05-23-2011 09:46 PM
05-24-2011 04:53 AM
if the error message says it's locked. You can fix this in ACT diag. (Start, run, actdiag, click on databases then look through the list. If a database is locked it will show there. Then right click on the database and click unlock.
If this isn't it, then mike is correct, we need more specifics. Error messages, what happened, etc. DONT UNINSTALL YET. this probably wont fix it.
05-24-2011 08:23 PM
Now I receive a could not connect to server instance after trying to run actdiag. I am on Windows 7. It was working fine Friday. Nothing has been done differently except the wifi I am on. Ideas
05-25-2011 05:57 AM
When opening Actdiag, you may be receiving 'could not connect' messages for databases that no longer exist but are still listed in SQL. Click the 'Continue' button on the messages until the Actdiag screen is presented. If this is the issue, you will still be able to access the Database List and perform the Unlock.
If you have gotten to the main Actdiag screen and it says it could not connect at the very bottom of the screen, it may be that the 'SQL Server (Act7)' service is not running. Close Actdiag > go to Windows Start > select 'Run' if XP, use the Search field for other > enter the command 'Services.msc' > hit Enter key. Scroll down to locate 'SQL Server (ACT7)' and check the Status column. Right click on the service and select 'Start' or 'Restart'. Once restarted, launch Actdiag again.