x Want to participate? Join the group to interact
Options
  • State Verified Answer
  • Replies 3 replies
  • Subscribers 118 subscribers
  • Views 1132 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
45
topics
92
replies
Payroll, Time Tracking, and Job Cost
777
topics
1k
replies
Reporting and Analytics
963
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
Kentaro

Starship 20.4 and Sage 100 2017 compatibility

SOLVED
Posted By

Hello, 

I'm exploring to see if anyone had an experience with issues between Starship ver. 20.4 and Sage 100 2017.  Specifically, Starship not being able to print invoice when processing an order/shipment.  

We've taken a few steps with the help of V-Technologies but the issue is persisting, so I'm trying to see if anyone else had the same or a similar issue that has been resolved. Below is the list of events.

  • Starship updated to 20.4
  • Starship client started showing error below when trying to print invoice 

  • Installed Crystal 32-bit runtime 
  • Installed V-Technologies MAS Interface Server Service
    • After this, the error on the client-side stopped showing. 

At this point, still no invoice is printed.  And in the Starship server log errors below are recorded. 

  • Printing the default form Code 'STANDARD’ throws error: “The Module Code is Required”
  • Printing a custom form code throws error "Report Setting Not on file"

Has anyone else had something like this??

-Ken

  • +1
    verified answer

    There is a Sage KB article pertaining to that "Unable to cast COM object..." error.  Try the pvxwin32.exe.config fix it recommends.

  • 0 in reply to Kevin M

    Thanks Kevin.  We tried the solution in the KB.  And it made no difference to our situation.  I think for some others in the identical situation with the same software environment, the KB probably would have taken to where we were at the time of posting this.    With that said, the KB contained a hint and we solved the issue.  If there is anyone else with this same situation, I'd recommend reading on.  The KB instructs us to replace the pvxwin32.exe.config on both the server and the clients in \Sage\2017\MAS90\Home folders.    But in our situation with Starship 20.4 an additional file needed to be replaced.   It's a file in C:\Program Files (x86)\Common Files\Sage\Common Components, very similarly named pvxcom.exe.config.  Once this file has been replaced with the KB supplied pvxwin32.exe.config, errors stopped and the invoice started printing.  This totally made sense after we solved it.  From the Sage or Crystal, printing was no problem.  But from trying to print from Starship/BOI scripts results in error.  Just rename, the old file, copy the new file, then rename the new file to match the old file.  Problem solved!  

  • 0 in reply to Kentaro

    That would have been my next suggestion.  I don't know how the StarShip program works, and I've seen others post about needing to use the config file fix for pvxcom too.  Glad you figured it out!

*Community Hub is the new name for Sage City