03-19-2012 08:30 AM
We recently purchased a new server and I moved ACT over to it. It is faster and has more memory. While doing so I upgraded to ACT 2012. Then restored the ACT Backup on the new server. I kept ACT on the old server because I use it as a terminal server. I also upgraded it to 2012. Is there an issue having basically two servers in the same network? I'm having a few random errors and I thought this may be the issue.
03-19-2012 09:16 AM
Having the database on two systems, even servers by itself wouldn't be a problem. Licensing is by the named user so unless you're using the two databases for extra users that wouldn't be a problem.
03-19-2012 09:52 AM
I'd make sure each user is opening the database on the new server. Go to Help About, Database Information and confirm that the first entry - "Database Server Name" points to your new server. Just to avoid such issues, I never leave the old database attached on the old server.
03-19-2012 11:37 AM
Most of the answers I would have for you start with " it depends"
What type of errrors?
Any sync users?
How did you do the restore?
How do users access the ACT database?
03-19-2012 11:56 AM
My maing problem is with Topline Dash. Every time I open a report that I've built since the upgrade I get an error "There was a problem connecting to the OLEDB engine. Please rebuild the ACT! OLEDB engine and try again.". I rebuilt the OLEDB. Also, Topline works fine on local sample database. I also get "Object Reference not set to an Instance of an Object" sometimes.
No sync users.
Restore As different name on new server. No one goes to the old server. I unmapped the drives.
All users open the database through a mapped network drive.