12-18-2012 06:04 AM
Is it okay to use the 28293 batch file on 2013 database?
Got a client who is suffering this issue after databases upgraded from 2012.
12-18-2012 08:00 AM
Greig Hollister
Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.
12-18-2012 02:23 PM
12-18-2012 02:50 PM
I called tech support who said it was okay, and was told I only needed to run it once.
They were on 2012 SP1 and we did run it, but maybe not enough times, as required then.
12-18-2012 03:31 PM
Greig Hollister
Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.
12-19-2012 05:13 AM
Thanks, Greig.
Attached is what I got when I ran it the second time.
Am I good to go?
If indeed we do need to run it more than once, can you make sure that tech support knows this, please?
12-19-2012 06:46 AM - edited 12-19-2012 06:50 AM
Those aren't the results I was expecting see. Here is an example of a successful run of the file:
The messages in your screen shots indicate the database was (or is) in a Recovery state. And I did not see the 0 rows affected message in there either. Is that database in Recovery state in ACTDiag?
Greig Hollister
Note: Effective 6/1/13, Sage no longers provides support for the Act! software. This is now provided by Swiftpage.