9.2.1.0 Full Package Error

[craig_welton]

Hi all,

After upgrading all the 9.2.0.5 components to 9.2.1.0, I'm getting an error when building a full package on the Dep server. Server log contains:

Mon Dec 05 19:41:31 - Header structure initialized successfully.
Mon Dec 05 19:41:31 -
Mon Dec 05 19:41:31 - Initializing internal structures for server ES1-920.
Mon Dec 05 19:41:31 - Message received from server.
Mon Dec 05 19:41:31 - spkgclntInit.c:410 PKGCLTINIT0017 ERROR: Failed to initialize server. Error ERROR: An unknown error 17..
Mon Dec 05 19:41:31 - spkginitsvrMain.c:586 PKGINTSVRM0012 ERROR: Failed to initialize detail structures and folders on the server.
Mon Dec 05 19:41:31 - spkginitsvrMain.c:267 PKGINTSVRM0003 ERROR: Failed to initialize detail structure on Primary Server: ES1-920.
Mon Dec 05 19:41:31 - spkginitsvrMain.c:306 PKGINTSVRM0006 ERROR: Failed to initialize Primary servers for server package build.
Mon Dec 05 19:41:31 - spkgeng.c:220 PKGENG0006 ERROR: Failed to initialize the servers in the package.
Mon Dec 05 19:41:31 - spkgeng.c:223 PKGENG0007 ERROR: Exiting Server Package Build.
Mon Dec 05 19:41:31 -

Change the ES (only) TR back to 9.2.0.5 and it works fine. This same error is on Dep Server and ES package logs. Anyone seen something like this?

thanks,
Craig

Lab environment is all Windows 2012 servers with SQL Server 2012. WebLogic 12.1.3

 

[jdelisths]

Hi Craig,

Got similar (not the same) errors when I built the first time (same configuration as yours). It went away when I tried the second time (did not reboot/reset anything, just restarted E1 on the deployment sever).

Unrelated: There is a known bug in 9.2.1 where kernels crash if the user id / password is incorrect. There is a documented bug for this .. it is supposed to be fixed in 9.2.1.1.

 

[JDEE1Tips]

Hi Craig,

Got similar (not the same) errors when I built the first time (same configuration as yours). It went away when I tried the second time (did not reboot/reset anything, just restarted E1 on the deployment sever).

Unrelated: There is a known bug in 9.2.1 where kernels crash if the user id / password is incorrect. There is a documented bug for this .. it is supposed to be fixed in 9.2.1.1.

Can you attach the Server Package Build log from your Enterprise Server to troubleshoot the issue?

 

[glen7x]

Hi all,

After upgrading all the 9.2.0.5 components to 9.2.1.0, I'm getting an error when building a full package on the Dep server. Server log contains:

Mon Dec 05 19:41:31 - Header structure initialized successfully.
Mon Dec 05 19:41:31 -
Mon Dec 05 19:41:31 - Initializing internal structures for server ES1-920.
Mon Dec 05 19:41:31 - Message received from server.
Mon Dec 05 19:41:31 - spkgclntInit.c:410 PKGCLTINIT0017 ERROR: Failed to initialize server. Error ERROR: An unknown error 17..
Mon Dec 05 19:41:31 - spkginitsvrMain.c:586 PKGINTSVRM0012 ERROR: Failed to initialize detail structures and folders on the server.
Mon Dec 05 19:41:31 - spkginitsvrMain.c:267 PKGINTSVRM0003 ERROR: Failed to initialize detail structure on Primary Server: ES1-920.
Mon Dec 05 19:41:31 - spkginitsvrMain.c:306 PKGINTSVRM0006 ERROR: Failed to initialize Primary servers for server package build.
Mon Dec 05 19:41:31 - spkgeng.c:220 PKGENG0006 ERROR: Failed to initialize the servers in the package.
Mon Dec 05 19:41:31 - spkgeng.c:223 PKGENG0007 ERROR: Exiting Server Package Build.
Mon Dec 05 19:41:31 -

Change the ES (only) TR back to 9.2.0.5 and it works fine. This same error is on Dep Server and ES package logs. Anyone seen something like this?

thanks,
Craig

Lab environment is all Windows 2012 servers with SQL Server 2012. WebLogic 12.1.3

I could do a package fine on Linux box, 9.2.1. Did the ES service start alright? Do check if the package build kernel got initialized. Also, try doing an update package with a few objects to check if it builds alright.

 

[craig_welton]

Thanks for the response Glen,

There is no server package log on the ES. The package folder is never even created on the ES. The log entries posted earlier were from the svrpkgbuild.log on the Deployment Server within the package directory. the jde.log on the Deployment Server shows the same messages.

I turned on tracing and examined the package kernel log for a good (9.2.0.5) and bad (9.2.1.0) build. There are no evident "errors", the process seems to call JDB_FreeUser after trying to delete existing package tables in the "bad" log and then never continues. The "good" log performs the same actions (trying to delete package tables) but continues.

thanks
Craig

 

[JDEE1Tips]

Thanks for the response Glen,

There is no server package log on the ES. The package folder is never even created on the ES. The log entries posted earlier were from the svrpkgbuild.log on the Deployment Server within the package directory. the jde.log on the Deployment Server shows the same messages.

I turned on tracing and examined the package kernel log for a good (9.2.0.5) and bad (9.2.1.0) build. There are no evident "errors", the process seems to call JDB_FreeUser after trying to delete existing package tables in the "bad" log and then never continues. The "good" log performs the same actions (trying to delete package tables) but continues.

thanks
Craig

If package directory is not getting created on your Enterprise Server then there might be an issue with communication in between your Deployment Server & Enterprise Server.

May be below troubleshooting steps will help you !

1. Did you Verified the telnet for the port 6017

> telnet JDEENT 6017

2. Did you enabled the Security Server and tried login into DEP920 or DV920 ..etc ?

3. Did you checked the Package Build Kernel log ?

 

[craig_welton]

Communication with the ES from the DS is working. Security server is enabled. The package build kernel log does not show any errors.

If I try to rebuild the assembled package, the package kernel logs show the attempts to drop the package tables (as expected and confirming communication).

If I change the TR on the ES, everything works fine.

odd

 

[JDEE1Tips]

Communication with the ES from the DS is working. Security server is enabled. The package build kernel log does not show any errors.

If I try to rebuild the assembled package, the package kernel logs show the attempts to drop the package tables (as expected and confirming communication).

If I change the TR on the ES, everything works fine.

odd

Yes its odd

Our Server Package Build log

Fri Dec 09 05:54:08 - Header structure initialized successfully.
Fri Dec 09 05:54:08 -
Fri Dec 09 05:54:08 - Check where the file repository is located, Deployment Server or Database.
Fri Dec 09 05:54:08 - Source/Include/Res files will be retrieved from the F98780R repository.
Fri Dec 09 05:54:08 - Check is complete, package build will continue.
Fri Dec 09 05:54:08 - Files will be retrieved from Database Repository.
Fri Dec 09 05:54:08 - Initializing internal structures for server JDEENT
Fri Dec 09 05:54:13 - Message received from server.
Fri Dec 09 05:54:13 - Server initialized.
Fri Dec 09 05:54:13 - Detail server structure initialized.
Fri Dec 09 05:54:13 - Detail structure initialized on Primary Server: JDEENT
Fri Dec 09 05:54:13 - Primary Server initialized.
Fri Dec 09 05:54:13 - Servers initialized successfully.
Fri Dec 09 05:54:13 -
Fri Dec 09 05:54:13 - Send Command: Build Object List
Fri Dec 09 05:54:48 - Send Command: Send message to server to get all files from the repository for the build.

In our case 9.2.1.0 Package Build Process Checking where the file repository is located inDeployment Server or Database (this is 9.2.1.0 Change ) but in your log looks like this process is not happening & Directly trying to Initialize the internal structures for server ES1-920.

Not sure whether is there any issue around required component ESU, Planner ESU or ASI is causing issue in your setup.

 

[paul_ross]

Anything in the jde.log of the build machine?

 

[craig_welton]

I re-applied the TR to the DS and ES. Rebooted everything and now it appears to be working. Thanks for all the feedback, seems like some kind of timing glitch.

 

[JDEE1Tips]

I re-applied the TR to the DS and ES. Rebooted everything and now it appears to be working. Thanks for all the feedback, seems like some kind of timing glitch.

Glad to hear !