RDP 3.80 upgrade - aximport error - installation failure

[ThomasO]

Hi all

So I did an upgrade today of my RDP environment from v3.70 to v3.80 and the upgrade failed during ProLiant Integration Module 3.80 installation.
More specifically, it fails during the Import Job task (see attached screen shot).
I did some searching here in this forum and found some information referencing to a database table issue in previous versions (Altiris KB20621 and 28329).
I have verified that this particular table is correct.
I have tried installing both through mstsc /console and directly on the console, but with the same error every time.

The user used for the installation is member of local Administrators group on both my RDP server and the back-end SQL 2000 server.

Some help is greatly appreciated.

Thanks.

/Thomas

[ThomasO]

I forgot to mention that I have installed WAIK 2.1 before starting the upgrade process.

/Thomas

[Gordon Leonard]

Are you installing over a network mapped drive? Copy the files to the local drive then install.

[RaMpaNTe]

If you are copying files from a CD try copying all the files into a local temporary folder and then execute the installation from there. It should work.

[ThomasO]

I extracted the content of the ISO file to a local temp folder on my RDP server and ran the installation from there.

Since I ended up with these problems, I even burned the ISO image to a DVD and tried installing from that as well, but with the same problems.

Any other things that might cause these problems?

Thanks.

/Thomas

[ThomasO]

Hi All

Is there a log file being generated during the upgrade? Maybe that can tell me something more about what's failing.

Thanks.

/Thomas

[Gordon Leonard]

When you D/L your RDP did you check to see if the MD5sum matched?

[ThomasO]

Hi Gordon

Yes, I have verified that the check-sum is correct.

/Thomas

[Gordon Leonard · Accepted solution]

Try to manually import the job to see if additional information is presented.

Go to the JOBS panel and create a new folder.
Click on the new folder.
From the menu select FILE->Import/Export->Import Jobs
Select the BIN file that you show in your first message. [The BIN files are located in {DRIVE}\pim\jobs\Server Deployment]

[ThomasO]

Hi Gordon

Thanks a lot for your advice.

I did exactly as you suggested and the import job also failed with the attached error.

Maybe this can shed some more light on my problems?

/Thomas

[Gordon Leonard]

Feedback..

"
I'm not sure what to make of that error. It's not a straight out corruption error, as it is just stating that database table definition doesn't match - I'm not sure what or whether there were database schema changes between 3.7 and 3.8. If there were schema changes, then this would be a predictable error.

The only way it could be data corruption is if the meta data in the express db has somehow gotten out of whack and I've never seen that happen in this manner. A DBCC checkdb would detect and fix that type of corruption.
"

[ThomasO]

I ran the check on the eXpress database to check for corruption and got the following result:

CHECKDB found 0 allocation errors and 0 consistency errors in database 'eXpress'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.

Anything else I can check?

/Thomas

[ThomasO]

Well, not really a good solution, but I actually ended up scrapping my RDP installation completely and reinstall from scratch to get my deployment working again.

After specifying database to use during the installation, you get a question if you want to retain the data in the database or not. I selected no to overwrite the current database and start fresh.

Remember to export all the jobs you want to keep before doing the above.

/Thomas