The sql database command timed out
Act 2012 has been installed on new Windows 7 computer acting as server.
Act 2009 (on XP computer old server) was backed up and restored on new server.
Database was converted on new server to 2012, shared and it opens fine locally.
Act 2012 was installed on a Windows 7 workstation computer, drive was mapped to database on new server.
Demo database opens fine but when I specify it for start up it wont startup automatically.
Instead I get an error: The sql database command timed out.
When I select the shared company database from list, it takes several seconds but eventually starts up fine.
I do recall initially leaving the old server and its database folder shared on the network but later removed it - I am not sure if this caused a problem?
I un-installed Act 8 on old server and installed Act 2012, connected to new servr database and this seems to works fine.
I need the company database to open automatically as fast as possible and get rid of SQL database command timed out error.
Please advise on corrective action.
Act 2009 (on XP computer old server) was backed up and restored on new server.
Database was converted on new server to 2012, shared and it opens fine locally.
Act 2012 was installed on a Windows 7 workstation computer, drive was mapped to database on new server.
Demo database opens fine but when I specify it for start up it wont startup automatically.
Instead I get an error: The sql database command timed out.
When I select the shared company database from list, it takes several seconds but eventually starts up fine.
I do recall initially leaving the old server and its database folder shared on the network but later removed it - I am not sure if this caused a problem?
I un-installed Act 8 on old server and installed Act 2012, connected to new servr database and this seems to works fine.
I need the company database to open automatically as fast as possible and get rid of SQL database command timed out error.
Please advise on corrective action.
ASKER
Hi,
It uses SQL 2008 Express.
I havn't done any database maintenance as yet.
It uses SQL 2008 Express.
I havn't done any database maintenance as yet.
1. There is no need to map the server drive
2. How are you specifying it for startup?
2. How are you specifying it for startup?
ASKER
I have copied the pad file from server to the workstation database folder.
On the workstation, I select the company (shared) database and it starts but next time I start Act it fails to rememeber the location and eventually displays the SQL error.
Its almost like it defaults to a location where there is no database?
On the workstation, I select the company (shared) database and it starts but next time I start Act it fails to rememeber the location and eventually displays the SQL error.
Its almost like it defaults to a location where there is no database?
Have you tried setting the Startup Database in Preferences to point to the PAD file?
ASKER
Yes I have tried but still same result.
I even compared with an XP workstation which is starting automatically and used same settings.
I even compared with an XP workstation which is starting automatically and used same settings.
Can you give the exact error message?
Also, does the same thing happen if you use the local PAD or the one on the server?
ASKER
The exact error is: The SQL database command timed out.
Yes same thing happens if I use local PAD or the one on server.
Another thing I have noticed on the workstations failing is that they have 2x ACT folders under Libraries\Documents\My Documents?
Is this normal?
I have copied the pad file in both but still no good.
Yes same thing happens if I use local PAD or the one on server.
Another thing I have noticed on the workstations failing is that they have 2x ACT folders under Libraries\Documents\My Documents?
Is this normal?
I have copied the pad file in both but still no good.
The Pad file is nothing more than a pointer to the ACT! database... you can open it in notepad to see.
I can only guess that either there is a firewall (either workstation or server) that's blocking some components or that you have a performance issue on the server
I can only guess that either there is a firewall (either workstation or server) that's blocking some components or that you have a performance issue on the server
ASKER
OK I will look into firewall variable to make sure its not causing the problem
What folder, on Windows 7 server is the database?
ASKER
Its in \Users\user\Documents\ACT\
Ok ... that WILL cause issues due to Windows 7 doing odd things with the security on User folders
Create a new folder off the C: drive - c:\ACTData
Move the database as per:
http://kb.sagesoftwareonline.com/app/answers/detail/a_id/19818
Detach the original database with ACTDIAG
Then use the new database and PAD file.
Create a new folder off the C: drive - c:\ACTData
Move the database as per:
http://kb.sagesoftwareonline.com/app/answers/detail/a_id/19818
Detach the original database with ACTDIAG
Then use the new database and PAD file.
ASKER
Great thanks, I will try this asap and let you know reslut.
How did you go?
ASKER
Thank you for following up.
I havn't tried as yet because the system is being used 6 days a week.
I hope to find a suitable time to sort this out and will be in touch.
I havn't tried as yet because the system is being used 6 days a week.
I hope to find a suitable time to sort this out and will be in touch.
ASKER
I hope to finalize in a few days
Look forward to hearing how it went
ASKER
I tried your suggestion but unfortunately same problem.
I even tried following Sage article 19420 - how to add ..... firewall ....exception list but no go.
(I hope I haven't missed something).
I have noticed that if the firewall on server is switched off then problem goes away.
It doesn't make much sense because database opens if I select manually and there is no problem on XP computers.
I even tried following Sage article 19420 - how to add ..... firewall ....exception list but no go.
(I hope I haven't missed something).
I have noticed that if the firewall on server is switched off then problem goes away.
It doesn't make much sense because database opens if I select manually and there is no problem on XP computers.
Ok ... to confirm:
The database is in the folder off the C:\ drive
The users are using the correct PAD - open it in notepad to see the location
Make sure no old pads pointing to the old location
Works from all machines with server FW off
Works from XP machines with FW on
Can you try with the startup database (in Prefs) set to a local demo on the workstation? Does that work?
Can you create a new db on the server in c:\ACTData and share it? Does that work?
You might also check that Winsock isn't damaged... see http://lnkd.in/tjC5rM - also note the 9th comment for two tips I forgot in original post
The database is in the folder off the C:\ drive
The users are using the correct PAD - open it in notepad to see the location
Make sure no old pads pointing to the old location
Works from all machines with server FW off
Works from XP machines with FW on
Can you try with the startup database (in Prefs) set to a local demo on the workstation? Does that work?
Can you create a new db on the server in c:\ACTData and share it? Does that work?
You might also check that Winsock isn't damaged... see http://lnkd.in/tjC5rM - also note the 9th comment for two tips I forgot in original post
ASKER
Just confirmin:
The database is in the folder off the C:\ drive - YES
The users are using the correct PAD - open it in notepad to see the location - Yes and pointing to correct location
Make sure no old pads pointing to the old location - Yes checked
Works from all machines with server FW off - Yes
Works from XP machines with FW on - Yes
Can you try with the startup database (in Prefs) set to a local demo on the workstation? Does that work?
Tried but fails
Can you create a new db on the server in c:\ACTData and share it? Does that work?
Tried but failed
You might also check that Winsock isn't damaged... see http://lnkd.in/tjC5rM - also note the 9th comment for two tips I forgot in original post
Tried on one client with issue but no go.
Not sure if this helps but I recently installed quickbooks database manager on the server computer (which also holds ACTData folder), shared the QB company file on network, and tried running the company file on a desktop (client).
What I noticed was that quickbooks was taking a long time to start (windows indicated porogram not responding).
Eventually it starts but just too slow!
In an earlier comment you mentiond possible performance issue but I can't see a problem with performance.
The fact that ACT and quickbooks struggle at start-up seems to suggest a newtorking issue?
(I am looking in to this further but starting to lose motivation).
I appreciate your efforts.
The database is in the folder off the C:\ drive - YES
The users are using the correct PAD - open it in notepad to see the location - Yes and pointing to correct location
Make sure no old pads pointing to the old location - Yes checked
Works from all machines with server FW off - Yes
Works from XP machines with FW on - Yes
Can you try with the startup database (in Prefs) set to a local demo on the workstation? Does that work?
Tried but fails
Can you create a new db on the server in c:\ACTData and share it? Does that work?
Tried but failed
You might also check that Winsock isn't damaged... see http://lnkd.in/tjC5rM - also note the 9th comment for two tips I forgot in original post
Tried on one client with issue but no go.
Not sure if this helps but I recently installed quickbooks database manager on the server computer (which also holds ACTData folder), shared the QB company file on network, and tried running the company file on a desktop (client).
What I noticed was that quickbooks was taking a long time to start (windows indicated porogram not responding).
Eventually it starts but just too slow!
In an earlier comment you mentiond possible performance issue but I can't see a problem with performance.
The fact that ACT and quickbooks struggle at start-up seems to suggest a newtorking issue?
(I am looking in to this further but starting to lose motivation).
I appreciate your efforts.
The winsock issue is likely to be a server issue ... can you try there?
ASKER
OK, I will also go through the firewall ports and program list in case I have missed something.
FYI
I was speaking with a colleague about the quickbooks app being unresponsive (similar behavior to ACT).
The solution here was to open a port in windows firewall.
So I have a feeling its also a firewall issue with ACT also.
FYI
I was speaking with a colleague about the quickbooks app being unresponsive (similar behavior to ACT).
The solution here was to open a port in windows firewall.
So I have a feeling its also a firewall issue with ACT also.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi,
After going through Sage article 19420 and adding the programs to exception list I have ACT starting automatically and no SQL time out error!
I must have missed an entry?
I just made sure to follow the article very closely.
ACT start up is a bit slow (about 8 sec after click) but I will assume this normal.
After going through Sage article 19420 and adding the programs to exception list I have ACT starting automatically and no SQL time out error!
I must have missed an entry?
I just made sure to follow the article very closely.
ACT start up is a bit slow (about 8 sec after click) but I will assume this normal.
The speed to start up can depend on a number of possible reason, but 8secs seems about normal, yes
ASKER
Thanks for sticking with me on this one.
I am a lot more confident in working with ACT in the future,
I am a lot more confident in working with ACT in the future,
Which version/edition of SQL does Act use? Some versions have autoclose on, and so on first connection the database is starting up.
Do you do any database maintenance on the database?
Regards
David