Cause:
This can be caused if the ACT7 instance of Microsoft® SQL Server® is not running.

Solution: 
There is more than one possible solution for this issue, but the following is normally the most effective fix.

Start the SQL Server (ACT7) Service
This issue may also be caused by the SQL Server service not being started. Follow the steps below to enable or start the SQL Server (ACT7) Service.


Services


    1. Click the Windows Start button, and then click Run. The Run dialog box appears.

 

    1. Type services.msc into the Open field, and then click OK. The Services panel appears.

 

    1. Locate the SQL Server (ACT7) service:

        • If the Status is Started, then right-click and select Restart. If the service is not started, then continue to the next step.

        • If the Status does NOT display Started for this service, right-click the service, and then click Start from the shortcut menu.


 

    1. When complete, the Status column will display Started, and the Startup Type will display Automatic.



If the SQL Server (ACT7) service cannot be started using the above steps, then the service may be damaged. If this is the case you may need to uninstall and reinstall the service. Please see the following Knowledgebase articles for instructions to remove the service and then recreate it:

Recreate Database Pointer File (.PAD)
This issue may also be caused by an invalid database pointer (.pad) file. Please see the following Knowledgebase article for instructions on how to recreate the database .pad file on the machine hosting the database:

How to Modify or Recreate a Sage ACT! Database *.PAD File
Answer ID: 28952


 .

2013-11-15 16:29:11
 
Comments List