04-02-2009 12:13 PM
Solved! Go to Solution.
04-02-2009 09:03 PM
The version you are using might help, but there is one thing I've seen off and on - the SQL Server (ACT7 instance) doesn't start, so in turn, the database is "not accessible".
Go to services (or Start>Run>services.msc), scroll down to the SQL entries and verify it's running. If not, right click and choose Start.
Again, your version might help more...
04-03-2009 09:15 AM
10-14-2009 01:26 PM
01-23-2012 09:50 AM - edited 01-23-2012 12:22 PM
I'm having the same problem with my ACT2010, running on windows 7.
What may also be compounding this is that my original database was installed on XP, and got reinstalled to this new computer (running 7) as my XP computer got fried last week.
I also tried the services.msc trick and sql files are already running.. I've attempted other fixes as out lined in the troubleshooting like detaching and reinitiating the database, or adjusting the pad file.. I'm at the point where I need professional assistance...
01-24-2012 10:14 AM
Welcome to the Sage ACT! Online Community!
Have you tried deleting (or renaming) the PAD file associated with the database, then open the database using the ADF file? This will recreate the PAD file with the updated computer information.
If that doesn't resolve it:
- How was the database moved to the new computer? Restored from a backup, or manually copied from the original machine?
- If manually copied, were the ADF, ALF, and 'database files' folder copied to the new machine?
01-24-2012 09:30 PM
Thanks for responding to this. The database files were moved to the new computer by manually transferring them from the original machine/hd. The ADF, ALF, PAD and Database files were copied over.
I have not tried removing the PAD file yet and opening from ADF.
01-25-2012 05:59 AM