Robert Robinson
Reputable Poster
This is perplexing -
We last ran package builds for all 3 of our 810 environments in January with no issues. I attempted to build and deploy an update package last week. The package built fine, but when I tried to deploy to our AS/400, I received the following error on the R98825D UBE:
106 - Path Code Not Defined for Development Server.
I then tried to run a full package - again, it built fine - but when I deployed, same error. I then repeated this for all of our environments with the same results.
I then reviewed the prior postings out here, and noted that I should check the P9654A. When I did, I found that the screen was blank in the deployment environment of the deployment server. I then reviewed the P9654A in the Planner Environment of the deployment server; all of the machines (including the deployment server) DO appear here (in fact, this is the only place where I can see the machines - in the past, I could view them from any client).
Has anyone encountered this? If so, how did you bring back the P9654A information? And, did this solve the package deployment error?
We last ran package builds for all 3 of our 810 environments in January with no issues. I attempted to build and deploy an update package last week. The package built fine, but when I tried to deploy to our AS/400, I received the following error on the R98825D UBE:
106 - Path Code Not Defined for Development Server.
I then tried to run a full package - again, it built fine - but when I deployed, same error. I then repeated this for all of our environments with the same results.
I then reviewed the prior postings out here, and noted that I should check the P9654A. When I did, I found that the screen was blank in the deployment environment of the deployment server. I then reviewed the P9654A in the Planner Environment of the deployment server; all of the machines (including the deployment server) DO appear here (in fact, this is the only place where I can see the machines - in the past, I could view them from any client).
Has anyone encountered this? If so, how did you bring back the P9654A information? And, did this solve the package deployment error?