SIM 5.0/MSDE install error "unknown exception"

[Mark Butler_3]

During a "typical" install of 5.0 and msde on a virgin (just-built) 2003 sp1 server I received the popup dialog "unknown exception" at the "Typical Install - Database Configuration" screen.

This error seems to be different than the typical credential ones others are seeing. The enhanced logging (using the reg file from another thread) doesn't show anything.

Based on comments in other threads, I thought it might be the password complexity I had on the domain id I was using (which is an admin of the box). So I created a local ID with a simple password and it passed the screen!

Then to double-check I changed the password to match my domain id... it still worked!

My conclusion is that there is some issue with installing/connecting msde using a domain id, even when the id has admin rights on the box.

By using the local ID, I was able to finish the install.

[sandu_1]

Go to \80\Tools\Binn
Execute SVRNETCN.exe and select 'Named Pipes' and 'TCP/IP' and Enable it.

Restart MSDE service.(Service owner of MSDE should be domain account)

Rerun the HPSIM setup.

[Kevin_130]

Thanks for the info Mark.

I am having the same issue with the difference being the db is on a remote SQL box.

If I use a local account, the error changes from "unknown exception" to "credentials are invalid". Unfortunately, I can't very well use a local account to connect to a remote SQL box.

Does anyone have a workaround for this with a remote SQL box?

Thanks,
Kevin

[Annette Jones_2]

If you find an answer to the remote sql database setup, going through the HPSIM 5 upgrade from 4.X, could you please post it.

I have completed a test run on a local MSDE upgrade an run into th eproblems you listed, the resolution was as explained in the "NAMED PIPES & TCP/IP). My 'live' installation is a different setup though, it points to a remote sql 2000 database!!! No doubt there will be a problem with this upgrade.

Regards

A

[Mark Butler_3]

I checked SVRNETCN.exe and it already had 'Named Pipes' and 'TCP/IP' enabled so that does not appear to be the issue when installing/connecting to local MSDE.

I installed on a 2nd newly build machine with the same problem. Worked just fine when I was logged in to the local admin account...obviously this won't work for remote sql installs though.