Community
Showing results for 
Search instead for 
Do you mean 
Reply

Conversion - schema update error

Nickel Super Contributor
Posts: 843
Country: United States

Conversion - schema update error

Attached report on conversion of 2008 Premium to 2013 Premium.

Database opens fine, but is there any damage lurking?

Thanks for any help.

Rita Kogstad
RKA Associates
Stamford, CT
Nickel Super Contributor
Posts: 843
Country: United States

Re: Conversion - schema update error

bump, bump!

Rita Kogstad
RKA Associates
Stamford, CT
Nickel Contributor
Posts: 695
Country: USA

Re: Conversion - schema update error

Hi Rita,

I had one of our database guys take a look at your log, and he says that it looks fine.

You can try running repair on it via actdiag to be sure. This article contains more information: http://answers.sagesoftwareonline.com/app/answers/detail/a_id/26854/kw/26854
Damien Park
Swiftpage
Nickel Super Contributor
Posts: 843
Country: United States

Re: Conversion - schema update error

Thanks for the reassurance, Daniel.

Tried the link and got this:

 

Fatal Error

 

Access Denied | Accès Interdit | Zugang Verbot

Reason: Please contact your Knowledge Center Administrator.

Rita Kogstad
RKA Associates
Stamford, CT
Nickel Contributor
Posts: 695
Country: USA

Re: Conversion - schema update error

Oh, that's embarrassing... I linked the wrong version. Try this one: http://kb.sagesoftwareonline.com/app/answers/detail/a_id/26854/kw/26854
Damien Park
Swiftpage
Copper Elite Contributor
Posts: 232
Country: Germany

Re: Conversion - schema update error

Hi Rita,

if the KB is not working, we have a tool that makes a 100% copy of the database and fixes any Database problems, let me know if i can help
ACC since 1995
Developer of Addons for ACT

CrmAddon Factory
+1 203 541 0040
Bronze Elite Contributor
Posts: 2,117
Country: United_Kingdom

Re: Conversion - schema update error

Hi Rita,

 

Lookign through the log file, the DBCC reports no orphaned record errors post conversion. I would say that this is more a warning to let you know that "in-process" checking was not able to complete since new schema tables had not been created at that point of running, which could be expected as there are dramatic changes to the schema between 2008 and 2013!

 

If you are able to successfully open the dB, I would carry out a Tools->dB Maintenance->Scan and Repair.

 

Let us know if you have any problems after that.

Vivek Gargav
Caldere Associates Ltd.
www.caldere.com
vgargav@caldere.com
My Blog