change sa password on SQL Server

Hi,

I changed the sa password on my SQL Server 2005 database and followed the instructions from tech support on what to do.  After changing the passwords in all the .config files and restarting my application server, I get the error below when I run 'prepare database' from the database repair utility.

Runtime Error!

Program: C:\Prog...

R6034
An application has made an attempt to load the C runtime library incorrectly.
Please contact the application's support team for more information.

 

Has anyone experienced a similar issue before?  I am currently running iMIS15.1.1.3508 on a windows 2008 server 64bits system.

 

Thanks,

odoro

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Doesn't sound like the password is the problem.

I wouldn't think changing the sa password could cause this, unless the new password contains some character DBRepair can't deal with.

Make sure you checked *all* the .config files, not just the ones Tech Support documented for you.  I've found that the iMIS installer pushes the login info into a few undocumented places.

It could also be that the error is caused by the reboot.  The C Runtime may have had a pending rename that only took effect when you restarted.  (I bet you loaded Windows Updates on the same reboot, right?)

--
Bruce Wilson
Director, Technical Services
RSM McGladrey, Inc.

Thanks

Thanks Bruce,

I will check the config files.  I have windows updates turned off on my server so I don't expect any updates to have been applied with the reboot.

I will check all the config files in the ASI folders for sa passwords.

 

thanks,

Odoro

DBRepair Runtime error on Windows 2008 64-bit - my solution

This error was happening to me on some servers and not others, all of which were virtual application servers sharing the same SQL server, but I couldn't see a pattern. I wasn't changing passwords, just restoring databases and needing to fix the sql logins.

It turns out that running Microsoft Update after installing the SQL Server Management Studio 64-bit Client Components fixed the problem. The update installed SQL 2005 SP3 and after a reboot it was fine.

I know it's been a while since you posted the question and may have solved it but hopefully if others find this page they can see what worked for me.

Barry D Wise
iMIS Consultant and Infrastructure Manager
Fisher Technology plc
.