Problem Deployign a full package

jaisejames

Well Known Member
Hello all
I just did a brand new install of ERP8.9 and build full package over the weekend.. Now when I am deploying the package to the enterprise server... I keep gettign internal error.. I have restarted the service..and even reboted the server.. but it will still not deploy the package... Package had no error for both server and client.. this is the log I am gettign on the enterprise server

3832/3836 Mon Apr 05 10:11:48.119 NETCFG.C251
Starting Kernel of Type:pACKAGE BUILD KERNEL

3832/3836 Mon Apr 05 10:11:49.121 JDEKDISP.C718
INITIALIZING PACKAGE BUILD KERNEL

3832/3836 Mon Apr 05 10:11:49.528 spkgclnt.c2613
_jdeUnlink (D:\peoplesoft\ddp\b9\DV9\bin32\CAEC.dll) failed (errno = 13)

3832/3836 Mon Apr 05 10:11:49.528 spkgclnt.c2613
_jdeUnlink (D:\peoplesoft\ddp\b9\DV9\bin32\CAEC.pdb) failed (errno = 13)

3832/3836 Mon Apr 05 10:11:49.528 spkgclnt.c2613
_jdeUnlink (D:\peoplesoft\ddp\b9\DV9\bin32\CALLBSFN.dll) failed (errno = 13)

3832/3836 Mon Apr 05 10:11:49.528 spkgclnt.c2613
_jdeUnlink (D:\peoplesoft\ddp\b9\DV9\bin32\CALLBSFN.pdb) failed (errno = 13)

3832/3836 Mon Apr 05 10:11:49.543 spkgclnt.c2613
_jdeUnlink (D:\peoplesoft\ddp\b9\DV9\bin32\CCONVERT.dll) failed (errno = 13)

Any idea whats going on.....
 
When I sometimes get a deployment issue on my applications servers ( for
some reason or the other ), this is what I do ...

- Print out the PDF of the objects that were successfully built. The
DLL's and spec listed on
the PDF are what you going to be copying from one folder to another.

- Shut down OneWorld Services

- Backup your CAEC.dll, CAEC.pdb, CALLBSFN.dll, CALLBSFN.pdb ..etc
listed in the
PDF you printed out, from your pathcode ( i.e. ddp\b7333\DV7333\bin32\
) to temp folder
( so that if this doesn't work, you could always copy the files back )

- Deleted the CAEC.dll, CAEC.pdb, CALLBSFN.dll, CALLBSFN.pdb ..etc from
your path
code folder

- Copy CAEC.dll, CAEC.pdb, CALLBSFN.dll, CALLBSFN.pdb ..etc from the
parent
package ( e.g ddp\b7333\packages\DV7333FA\bin32\ ) folder to the
pathcode
(e.g.ddp\b7333\DV7333\bin32\ )

As you can tell we still on OneWorld Xe but don't see how different it
can really be. When deploying a package the above is what it's
essentially doing. This process can also be used for deploying specs (
.ddb and .xdb ).

Hope this helps

JL
 
Re: RE: Problem Deployign a full package

JL

I am aware of this process.. But Since this is brand new installa nd would ultimately will hand over to local CNC, I want to keep it as clean as possible.. These are trick we could use if we have no other alternative....
I really would like to have jde process deploy it cleanly so that I can handover the systems to my client as clean as possible..
Apprecaited your help though...
 
Re: RE: Problem Deployign a full package

Jaise,

13 is an access error. Check if your DV9 pathcode is properly installed on your ES. See if the user who starts the services has proper access to the DLLs. Change the Default Pathcode from your server´s JDE.INI to something different from DV.

Good luck, Gerd
 
Please post your JDE.INI file .
Have observed a couple of similar issues related to JDE.INI settings (Kernel Definitions)
 
Re: RE: Problem Deployign a full package

Gerd,

Thanks... It helped.. But I am confused the user JDE is a domain admin and was able to build a package without a problem.. why would it have problem deploying a package nothign has changed... I added the JDE user id to local admin group and that have resolved the issue... But would like to know why do I need to do this..
any comment will be appreciated
 
Re: RE: Problem Deployign a full package

Jaise,
it´s a Windows-domain-permissions question. I gave up trying to understand windows security. I actually feared for my sanity. Maybe somebody else can help.

Cheers, Gerd
 
Re: RE: Problem Deployign a full package

Gerd,

That sucks... I was puzzled as I am MCSE AND MCSA and this did not fit into my knowledge base as I would have liked....

But yeah its weird.....
thanks for your Help though
 
Re: RE: Problem Deployign a full package

Not necessarily, it is more likely to be "The data is invalid" Windows error, or maybe an internal OW error number. It's not always easy to say.

Regards,
Alexander Pastuhov
http://www.pastuhov.com.au/index.htm
 
RE: RE: Problem Deployign a full package

Sounds like someone has a group policy going down to your enterprise server,
or has being playing with your local security policy. The domain admins group
is normally a member of the admin group on all member servers..
Regards,
Kieran Fitzgerald
 
Back
Top