x Want to participate? Join the group to interact
Options
  • State Not Answered
  • Replies 5 replies
  • Subscribers 105 subscribers
  • Views 1461 views
  • Users 0 members are here
Browse Forums
Announcements
293
topics
370
replies
Business Object Interface
1k
topics
7k
replies
Core Financial Modules
2k
topics
8k
replies
Customization and Productivity
3k
topics
12k
replies
Distribution, Manufacturing, and Applications
2k
topics
7k
replies
General Discussion
1k
topics
3k
replies
Partner Cloud
47
topics
95
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
965
topics
3k
replies
Sage CRM for Sage 100
164
topics
357
replies
Technical and Installation
2k
topics
9k
replies
Year-end Forum
89
topics
237
replies
sued2

Error 107 during Sage 2021 migration

Posted By

We have a client that is currently on Sage 2016.  They have Scanco and Mapadoc.  We have installed Sage 2021 on a new server with Product Update 2 and Scanco.  At the end of the Migration we receive an Error 107.  Once you click OK it closes out.  We are able to access the software but have not attempted data conversion because we're uncomfortable with the migration not finalizing.  Sage suggested we rebuild the system files in the Live environment, then try again.  We are willing to do that, but were curious if anyone else has run into this.

Thanks

Sue

Parents
  • 0

    We did rebuild all the System files as Sage requested.  There were a few errors in there which is a little scary, but what we did notice was that there was an error on the sy_odbcsecurity.m4t file.  It states "cannot lock Error #0: Record/file busy"  This is odd to me because we had all users out of the system, the Service was turned off and we checked to be sure that there were no pvxwin32.exe's running phantom.  Thoughts?

    Because of the file lock, we have not attempted the migration again yet.

Reply
  • 0

    We did rebuild all the System files as Sage requested.  There were a few errors in there which is a little scary, but what we did notice was that there was an error on the sy_odbcsecurity.m4t file.  It states "cannot lock Error #0: Record/file busy"  This is odd to me because we had all users out of the system, the Service was turned off and we checked to be sure that there were no pvxwin32.exe's running phantom.  Thoughts?

    Because of the file lock, we have not attempted the migration again yet.

Children

*Community Hub is the new name for Sage City