Package Build Failure

Hi,

We are in XE Update 2, SP22. HP-UX, Oracle, CITRIX

When we try to build an Update Package, it fails. JDE log says it is not able to create the package folder. We have enough space in both C and D drives, rights is not an issue. We can manually create a folder and file, not a problem, but the package build process fails with unable to create directory message.

Any one has seen this before? Any help you can provide is greatly appreciated. Thanks!

Krish

ANy

The same user that you are logged into the machine with to build the package can create a folder/file?

Is it failing on the client portion or server portion of the package build? If it's the server portion, it would be disk space or rights on the enterprise server as the issue.

Krish,
What are you trying to name your package?
There are naming rules that if violated can cause this issue.

I am logging in as JDE, which is the most powerful user Id we got with all the rights possible. JDE can create the folders through the windows explorer fine, but package build process fails. Both client and server build fails, error message seems to be pretty clear, stating that it was NOT able to create the directory JDEDEP\B7333\PD7333\PACKAGE\TEST1 .... But we can create the directory manually with out any issues.

Package name , we tried with few different names, For Example,
CAON1
CAON2
PDU14FB
TEST1

Thanks for your time and help on this regard.

Which side of the build is failing, client or server? Is the B7333 folder on the deployment server shared?

Also try this...Run GH9083, then machine identification. Open the tree and find the deployment server. Make sure the share path says \B7333. Find the enterprise server and make sure that the installation path is correct. Take the Environments form exit and make sure all the environment for that server are there. Your jde.log file would be helpful in trouble shooting this issue.

Patty

Do you mind posting your log.....

If the parent package that you have defined in the udate package does not exist, then you can see this issue. Be sure your parent package exists on your deployment and enterprise servers.

Hello,
I feel the problem is purely with the Server Share path. Go to the path code master application. Select the pathcode of your concern and find the entry for share path. Is is B7334 or something else. change it to B7334 by logging in both your planner environment and the pathcode of your concern.
You can even change it from backend in table F00942. Let me know your output.

Regards,
Karthik Iyer

Please get us some logs and we will do our best to help!