x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 13 replies
  • Subscribers 88 subscribers
  • Views 3184 views
  • Users 0 members are here
Browse Forums
Announcements
311
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
4k
replies
Partner Cloud
57
topics
117
replies
Payroll, Time Tracking, and Job Cost
794
topics
1k
replies
Reporting and Analytics
984
topics
3k
replies
Sage CRM for Sage 100
166
topics
361
replies
Technical and Installation
2k
topics
10k
replies
Year-end Forum
90
topics
237
replies
Kevin M

The Script Control object could not be created

SOLVED
Posted By

Posting this in case it helps someone else.  Client is on SPC (new), v2022.2, and we received this error when trying to add a UDS (clicking the green check-mark button to verify syntax).

The script host was properly installed (and Allow External Access enabled), with correct file association, but it turns out they were running the 64-bit version of Sage 100.

Changing to 32-bit (running the utility) fixed the error.

  • 0 in reply to Patrick K.

    You should find a file called "RegCom64.bat" in the folder "C:\ProgramData\Sage\Common Components". Close down Sage 100 if running and run this batch file. The batch file will self elevate and perform the COM registration(s). Note: you will need to be an administrator or a user that is part of the administrator group for this to register the components correctly.

    If this does not resolve the issue then please report back so we can research further.

    Regards,
    Russell

  • +1 in reply to Russell Libby
    verified answer

    So that didn't work initially, the batch file was stating it couldn't find tsc64.dll. I was able to locate this DLL on the server under ..MAS90\Migration\_Repository\_Repository_x64\wsc7.10\env\any\CommonProgramFiles\Sage\Common Components.

    Copied this to all clients' ProgramData, then ran the RegCom64.bat and am no longer receiving this error on any of the clients! Thank you so much!!!!

  • 0 in reply to Patrick K.

    Glad you were able to sort it, and sorry for the inconvenience. We will be working to resolve the workstation install issue.

    Regards,
    Russell

*Community Hub is the new name for Sage City