Sage ACT Pro 2011 Database Files Unopenable

Brad McAfee
Brad McAfee used Ask the Experts™
on
We have a client that has ACT 2011 on Windows Server 2012 R2.  They have somehow managed to damaged all of their ADF files by messing with ACT 2011 and SQL server.  We have no idea what was done except that it is not working.

1. We are getting this error message with all the current database/files when we try to open them:

This database cannot be opened because the SQLServer version of this database cannot be identified.

2. When we restore backup files from before this issue occurred and try to open them we get a dialog box that say it will verify the database.  However, the next moment. we get an error message:

The log scan number (1201:656:1) passed the log scan in database 'Sales' is not valid,  The error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf).  ......


3. Finally, when we try to attach the file (that the client "messed with") to the database (via ACTDiag) I get this error message:

"The database was created with a version of SQL Server that is neither SQL Server 2005 or Server 2008.  Attaching a non-SQL 2005 or 2008 database is not supported."  However, I do not believe SQL version about 2008 R2 has been on this machine.

We are doing what seems to be endless research and multiple solutions for SQL and/or ACT and nothing seems to be working.  Any thoughts or advice?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Mike LazarusAct! Evangelist - CRM Consultant

Commented:
Ouch ... A number of possibilities.
What version of SQL is on the server?
Have you tried uninstalling SQL and Act!, then reinstalling so Act! can set up the SQL instance correctly?

You should also be aware that Act! 2011 will actually stop working sometime after December 31st, this year.
See: https://blog.glcomputing.com.au/2018/11/important-licensing-notice-for-all-act.html

Author

Commented:
Mike,

It is 2008 R2 Express.

SQL works fine as we can created a different database and open it and save it.  ACT also works fine.

We have tried it on two different systems with the same result so it is something to do with the file structure/SQL.
Raja Jegan RSQL Server DBA & Architect, EE Solution Guide
Awarded 2009
Distinguished Expert 2018

Commented:
>> This database cannot be opened because the SQLServer version of this database cannot be identified.

Seems like your Database is corrupted..

>> The log scan number (1201:656:1) passed the log scan in database 'Sales' is not valid,  The error may indicate data corruption or that the log file (.ldf) does not match the data file (.mdf)

When restoring the database backup, you shouldn't get this error as the mdf and ldf files would be from the backup file..
As the error mentions, ldf file is not matching up with your mdf file and hence possible corruptions again.

>> The database was created with a version of SQL Server that is neither SQL Server 2005 or Server 2008.  Attaching a non-SQL 2005 or 2008 database is not supported.

I think this error message also due to some corruption in your database files.
Since your database has some corruption, I would suggest you to run DBCC CHECKDB by following the steps mentioned here..
https://www.sqlservergeeks.com/repair-the-database-using-dbcc-checkdb/
Ensure you’re charging the right price for your IT

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!

Mike LazarusAct! Evangelist - CRM Consultant

Commented:
I can't recall if this was an option back with Act! 2011 ... But can you try attaching the ADF with ACTDIAG without the ADL?

Or try extracting the BAK file from the backup zip and using ACTDIAG to restore it?

If that and the checkdb recommended by Raja don't work, you'll need some expert help to see if either the original or the backup are recoverable. I can certainly assist with this.
Mike LazarusAct! Evangelist - CRM Consultant

Commented:
BTW: From the first point in your original post ... Does that mean the databases are still attached in ActDIAG?

If so, try a Repair from ACTDIAG - It does a checkdb.

To be safe, before you do ANYTHING, stop the SQL service and manually copy the ADF/ADL files.

Also, in ActDIAG, when you start it, what's the Server Edition and Version listed?
and, in the Database List, what's the Status showing?
This document at Act.com says that SQL Express 2008 R2 is not going to work with Act 2011 (expand the database section).  It says you need to have SQL Standard 2008 R2 for it to work and I suspect they unwittingly installed Express on the server!
http://kb.act.com/app/answers/detail/a_id/29767/~/act%21-compatibility-matrix
Mike LazarusAct! Evangelist - CRM Consultant

Commented:
No, Dennis ... Under Database, Standard for Premium only. Express for any.
Which line were you looking at?
It turns out that the client converted the databases to 2012 so that was the problem.  We ended up upgrading them to ACT 21 which fixed it.
Mike LazarusAct! Evangelist - CRM Consultant

Commented:
Ouch ... Yup, that'll do it.

They would have needed to go to v21 before the end of the year, anyway

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial