ASU Load

I know this question has been asked before but after trawling through the list for the past hour I have not found a definitive answer so i will ask it again hoping one of you gurus has since solved the problem.

I have created a product package from PY and am trying to load it into PD here to test it. After having no end of problems trying to cab the correct data, which proved impossible due (see my post yesterday Product Packaging - Data) I eventually got round to loading the ASU from a CD. It created the correct records on the deployment server/planner/package directory. I then log on to JDEPLAN, as stated in the manual, and access P96470. Here is where the issue lies. Straight away I get prompted for a database password entry screen for db 'One World SU - '. No valid profiles and passwords (even JDE) seem to be accepted so I close out of this screen.

The ASU application does not show the ASU as available to install. What gives?

jde.log says that the "SQLDriverConnect failed".
jdeinst.log states "CJDESetupPackage :: ReadInfoFile: Key 'PackageName' is missing in section 'Attributes' of 'C:\TEMP\Deployment.inf'".

We have recently run similar tests on other packages and had no issues, but have never been prompted for database entry before - hence my assumption.

Regards and have a good weekend

Please can someone help me.
I still cannot see the Package from P96470 or in UTB but I can see it on the Deployment Server in Planner/Packages and on the Enterprise server in the SYS7333 library for the files:

F9603 (Planner ASU Header) - contains records for my ASU
F9622 (Planner ASU Detail) - contains records for my ASU

How can this be so? Does it have something to do with ODBC prompt. I don't understand ODBC other than the standard datasources? Why would the ASU application prompt me for a password? Has something gone missing? The JDE profile password has not changed.

Jill,

Whenever I've gotten that little userid/password prompt it was usually due to a bad or missing ODBC. Check your ODBC System Admin Data Sources and see if you have a ODBC driver set up for the environment you're logging on to.

OK Database Password Entry fixed. Took a couple of days, but eventually got there. Tried deleting ODBC database from Database Datasources APPL (P986115), jdeplan.mdb (F98611), Data Source Administrator and ODBC.txt in C\WINNIT, but every time I accessed P96470 I would still get prompted and the ODBC settings would be recreated!?!?!?!

In the end I had to do Start\Run: regedit. Then within the Registry Editor remove all records that related to the offending ODBC database driver. Finally no password prompt.

However still cannot see Product Package that I want to see because no entry in the F9670. Directory exists on planner pathcode, data.cab written to Planner\Data and records in following files:

F9603 (Software Package Header) - Package Deninition Status = Definition Complete
F96021 (Software Package Build Header) - Client 50/Server 70
F96215 (Software Package Build Header History) - Client 50*3/Server 70*3
F9622 (Software Package Build Detail) - All objects listed
F96225 (Software Package Build Detail History) - All objects have a spec build status of 03 = Successful
F9631 (Software Package Detail) - All objects listed"

The only two tables that do not contain records are the F9670 and F9671. How do these get populated and why does everything else apart from this get created? Please find attached jdeinst.log. This tells me why things went wrong, but all things that are causing errors are out of my control and are created by the Product Packaging software.

Sorted. Apparently when the SQL statement reads the available packages in the F9670 it tries to find all database datasource .mdbs and if it cannot find one it ignores the rest. An old packages had not been completely removed. This began with an R and my product package begins with a V so it never appeared. As soon as the R package had been removed from the deployment server using regedit my package appeared.

Hi Jill,

does your PP contain the F0005 table? This table has to be part of your ASU PP. If not generate this table after extracting the ASU. Do not open Application Software update, instead open OMW and generate F0005 (UDC) table in the 'ASU'.mdb (add db source first). Add one record for 98/RL with the name of your ASU.
After this try to install your ASU.

This is a workaround for the latest planner ESU, which has a bad BSFN which does not correctly create the PP info.

regards

Thomas

CNC specialist

Hi Jill,

I had faced the similar issue on my jdeinstall.log just yestreday..
The problem is with the user rights (windows security) not having Full control on the subdirectories..

Cheers