Possible to Install 4.1 using SQL authentication ???

[Don Patchen]

Every time I try to do an install it wants to use the currently logged in user...without the option to change credentials.

The installation states that if you want to run as a different user to login as that user. We have service accounts for running applications like this, and they are locked down to non-interactive, so this isn't an option.

Insight Manager 7 sp2.3 has no issues with this, so was hoping 4.1 could be "forced" to allow custom credentials.

In addition, I tried the install with the currently logged in user having full privs in the database (local SQL 2000) and it would fail on the install. Decided to remove SQL 2000 and let the install put MSDE on.....tried this and it fails as well, even though the instance was setup by the same setup routine. (Makes no sense to me)

Any thoughts ?

Thanks

[James Kennedy_4]

Unfortunately, I don't beleive there is a way to change the login credentials during the install. I was in the same boat as you are.

You can, however, modify the service account and such after installation is all complete and the system is up and running properly.

Not sure why it was failing, but you can look at your SQL Logs and it will probably tell you why, probably some sort of authentication problem. Sounds like you have everything setup properly with the account being a full Database Admin for the SQL Server.

Strange that the MSDE would fail, though I've seen this happen with other products. MSDE will fail install because there are still some remenants of SQL Server on the box. Even just having the "C:\Program Files\Microsoft SQL Server" with no files in it, is a enough to through MSDE out of whack. There are tids from microsoft on how to get MSDE to install when it fails. Beleive it even creates an err.log on the root of C:\

Hope this helps some, sometimes rather than beating your head against the wall its just quicker to rebuild the OS from scratch and start again. Good luck.