Errors were written to the SQL Translation Log while converting the MAS_XXX data to SQL

Question

Good morning. During the refresh of an upgrade from 2017 Standard to 2018 Premium, the system activity log shows the following messages for each company that was converted.

XXX Company data conversion to version 06.00.00.00 started

XXX Company data conversion to version 6.00 completed

Also the SQL transaction log shows the following error for each company that was converted

01/04/2019 22:29:51,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 38.

01/04/2019 22:29:51,Logon,Unknown,Login failed for user 'MAS_User'. Reason: Failed to open the explicitly specified database 'MAS_XXX'. [CLIENT: <local machine>]

Note, MAS_User is properly showing as owner for all the MAS databases.

Has anyone experienced similar errors in a migration?

Where can these Translation logs be located and accessed or queried?

Thanks in advance.

Mike

mhainesalt · Answer

There were a couple of things that were critical here. I think that SQL permissions were an issue, and then there were some issues with some database settings in SQLL that were also necessary. 
 One thing is that MAS_USER needs to be the Owner of the databases if that did not happen automatically. See knowlegebase article 99062 https://support.na.sage.com/selfservice/viewdocument.do?noCount=true&externalId=99062&sliceId=1&isLoadPublishedVer=&docType=kc&docTypeID=DT_Article&stateId=8072&cmd=displayKC&dialogID=313506&ViewedDocsListHelper=com.kanisa.apps.common.BaseViewedDocsListHelperImpl&openedFromSearchResults=true 
 Also article 95107 about initial sizes on model.mdf and modellog.ldf sometimes those settings will give you an error message that has nothing to do with database size. 
 
 Please let me know if these resolutions don't solve your issue.

Sage 100

Errors were written to the SQL Translation Log while converting the MAS_XXX data to SQL

Top Replies

COMMUNITY

COMPANY

PARTNERS

SUPPORT & TRAINING