Act Error: The database could not be accessed

Sage Act! 2009 (full product)
October 20, 2009 at 07:23:46
Specs: Windows XP
Receiving the error message, "The database could not be accessed. In order to access this database, check your network connection and verify that your database server is available. It may be necessary to disable any firewall software..."


The 2 most likely causes on a standalone are a damaged or invalid .pad file or SQL is not running, or is damaged.

.PAD file

- Close ACT!

- Click your Windows Start button, choose Run and type in actdiag

- When ACT! Diagnostics comes up, click Databases, the Database List

- Locate your database in the list, right-click on it and select Detach. Make sure you know the filepath to your database before detaching it.

- When the database has been detached, open My Computer (or Windows Explorer) and browse to the location of your database.

- Locate the .PAD file for your database [database name].pad and delete it

- Reopen ACT!...you will get a message that the last database opened cannot found, then will be taken to the Open Database dialog box

- At the bottom of this box, change the Files of Type to .adf, browse to the location of your database and double-click on the .adf file for your database

- You will get a message that ACT! will verify your database, click OK and ACT! will reattach your database to SQL and create a new .pad file

SQL Server

- Close ACT!

- Click on your Windows Start button, select run, and type in services.msc

- When the list of Local Services comes up, scroll down and locate the service called SQL Server (ACT7)

- Look in the Status column and make sure it says Started...if not, then right-click on the service and select Start

If either of these suggestions does not resolve the issue, then please see the following Knowledgebase article for additional troubleshooting:

Error: "The database could not be accessed. In order to access this database, check your network connection and verify that your database server is available. It may be necessary to disable any firewall software...


See More: Act Error: The database could not be accessed

Report •


#1
March 29, 2010 at 03:10:08
I had this same error after i had migrated the an organistion to sbs2008 from 03.

it turned out to be a problem with the windows firewall blocking the ports for sql. i followed the microsoft fix it which worked me http://support.microsoft.com/defaul...

To create the script, follow these steps:
Start Notepad.
Copy and paste the following code into Notepad:


@echo ========= SQL Server Ports ===================
@echo Enabling SQLServer default instance port 1433
netsh firewall set portopening TCP 1433 "SQLServer"
@echo Enabling Dedicated Admin Connection port 1434
netsh firewall set portopening TCP 1434 "SQL Admin Connection"
@echo Enabling conventional SQL Server Service Broker port 4022
netsh firewall set portopening TCP 4022 "SQL Service Broker"
@echo Enabling Transact-SQL Debugger/RPC port 135
netsh firewall set portopening TCP 135 "SQL Debugger/RPC"
@echo ========= Analysis Services Ports ==============
@echo Enabling SSAS Default Instance port 2383
netsh firewall set portopening TCP 2383 "Analysis Services"
@echo Enabling SQL Server Browser Service port 2382
netsh firewall set portopening TCP 2382 "SQL Browser"
@echo ========= Misc Applications ==============
@echo Enabling HTTP port 80
netsh firewall set portopening TCP 80 "HTTP"
@echo Enabling SSL port 443
netsh firewall set portopening TCP 443 "SSL"
@echo Enabling port for SQL Server Browser Service's 'Browse' Button
netsh firewall set portopening UDP 1434 "SQL Browser"
@echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK)
netsh firewall set multicastbroadcastresponse ENABLE


Save the file as a .txt file by using the following name: OpenSqlServerPort.txt
Rename the OpenSqlServerPort.txt file to the following: OpenSqlServerPort.bat


Before you run the OpenSqlServerPort.bat script, you must copy the script to the computer which has the firewall and then run the script on that computer. To run the script, follow these steps:
Click Start, click Run, type cmd, and then click OK.
At the command prompt, use the cd command to navigate to the folder in which you saved the OpenSqlServerPort.bat file.
To run the OpenSqlServerPort.bat script, type OpenSqlServerPort.bat at the command prompt, and then press ENTER.


Report •

#2
May 11, 2010 at 14:13:51
I had a similar error with ACT...after the 2010 upgrade. But also I kept getting the message that my dbase could not be accessed and that my dbase was not accessible by the administrator. After following the instructions above, to - Click your Windows Start button, choose Run and type in actdiag. I noticed my specific dbase was locked by the administrator. Was a simple step to just right click and unlock it. Weird that the dbase was locked and password protected (even though I didn't password protect it in the first place). Thanks for the tip!
Dana Labrie www.marketinglaunchinnovations.com

Report •

#3
May 20, 2010 at 10:28:05
The posting from lbates70 for Windows 2008 and above works great.

The script below addresses the issue

The script that is discussed in this section opens the firewall ports for SQL Server.

To create the script, follow these steps:
Start Notepad.
Copy and paste the following code into Notepad:


@echo ========= SQL Server Ports ===================
@echo Enabling SQLServer default instance port 1433
netsh firewall set portopening TCP 1433 "SQLServer"
@echo Enabling Dedicated Admin Connection port 1434
netsh firewall set portopening TCP 1434 "SQL Admin Connection"
@echo Enabling conventional SQL Server Service Broker port 4022
netsh firewall set portopening TCP 4022 "SQL Service Broker"
@echo Enabling Transact-SQL Debugger/RPC port 135
netsh firewall set portopening TCP 135 "SQL Debugger/RPC"
@echo ========= Analysis Services Ports ==============
@echo Enabling SSAS Default Instance port 2383
netsh firewall set portopening TCP 2383 "Analysis Services"
@echo Enabling SQL Server Browser Service port 2382
netsh firewall set portopening TCP 2382 "SQL Browser"
@echo ========= Misc Applications ==============
@echo Enabling HTTP port 80
netsh firewall set portopening TCP 80 "HTTP"
@echo Enabling SSL port 443
netsh firewall set portopening TCP 443 "SSL"
@echo Enabling port for SQL Server Browser Service's 'Browse' Button
netsh firewall set portopening UDP 1434 "SQL Browser"
@echo Allowing multicast broadcast response on UDP (Browser Service Enumerations OK)
netsh firewall set multicastbroadcastresponse ENABLE


Save the file as a .txt file by using the following name: OpenSqlServerPort.txt
Rename the OpenSqlServerPort.txt file to the following: OpenSqlServerPort.bat


Before you run the OpenSqlServerPort.bat script, you must copy the script to the computer which has the firewall and then run the script on that computer. To run the script, follow these steps:
Click Start, click Run, type cmd, and then click OK.
At the command prompt, use the cd command to navigate to the folder in which you saved the OpenSqlServerPort.bat file.
To run the OpenSqlServerPort.bat script, type OpenSqlServerPort.bat at the command prompt, and then press ENTER.
Back to the top

thanks bates


Report •

Related Solutions

#4
December 28, 2010 at 09:46:50
I had this recurring problem and was reinstalling Act 2010 each time to overcome it.

I followed tonyawells instructions: Click on your Windows Start button, select run, and type in services.msc. When the list of Local Services comes up, scroll down and locate the service called SQL Server (ACT7). If Status column doesn't say Started...then right-click on the service and select Start.

This fix worked beautifully.

Thank you tonyawells!


Report •

#5
January 23, 2011 at 11:36:46
hi tony,

been struggling all weekend to load my old act database, have overcome the pad file issue and removed and then pointed at the adf ( by reading numerous post) this worked all the way through to the point it says the database is version 660 and the version i am running is 612, i have also then went and bought act 2011 thinking this would sort it but no joy.
the version i was running is 2009, i am sure this is something minor i am missing but cannot work it out

any idea's??

rob


Report •

#6
January 25, 2011 at 13:36:25
As per above suggestions, I also ran services.msc and started the SQL Server (ACT7) and it works for me too! Yey!

Report •


Ask Question