Sage 100

Sage 100 v2016 Standard to Sage 100 v2019 Standard - Installed v2019 Standard on the same Win 2016 server.  Now getting the dreaded Unable to Cast COM Object mesage when I try and print from version 2016.  I copied the pvxwin32.exe.config file from 2019 mas90\home to 2016 mas90\home.  It doesn't seem to make a difference.  #Urgent  #Onsite​​

------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------

Did you follow the new Crystal version required work-around?

------------------------------
Michelle Taylor
ERP Team Manager, CS3 Technology
918-388-9772
------------------------------

with the article!

------------------------------
Michelle Taylor
ERP Team Manager, CS3 Technology
918-388-9772
------------------------------

Original Message:
Sent: 04-09-2019 13:02
From: Michelle Taylor
Subject: Unable to Cast COM Object

Did you follow the new Crystal version required work-around?

------------------------------
Michelle Taylor
ERP Team Manager, CS3 Technology
918-388-9772
------------------------------

No.  Please enlighten me.

------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------

Original Message:
Sent: 04-09-2019 13:02
From: Michelle Taylor
Subject: Unable to Cast COM Object

Did you follow the new Crystal version required work-around?

------------------------------
Michelle Taylor
ERP Team Manager, CS3 Technology
918-388-9772
------------------------------

Update.  After an hour on the phone with Sage they determined the pvxwin32.ece.config file that gets installed on from cab1 is incorrect.  It is missing s lot of data.  Sage installed a v2018 pvxpin32.exe.config in the home folder of the 2016 installation and the printing worked fine.  So, there was an issue with the 2019 download that has been escalated.  If you downloaded 2019 before today then you need to download again.  When you install 2019 on the same server as 2017 and prior, copy over pvxwin32.exe.config to home, install the Crystal runtime update, and if that doesn't workk try replacing pvxwin32.exe.config in the earlier version with a known good copy. 


------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------

Thanks for the update and tips!

------------------------------
Michelle Taylor
ERP Team Manager, CS3 Technology
918-388-9772
------------------------------

Original Message:
Sent: 04-09-2019 17:16
From: Doug Higgs
Subject: Unable to Cast COM Object

Update.  After an hour on the phone with Sage they determined the pvxwin32.ece.config file that gets installed on from cab1 is incorrect.  It is missing s lot of data.  Sage installed a v2018 pvxpin32.exe.config in the home folder of the 2016 installation and the printing worked fine.  So, there was an issue with the 2019 download that has been escalated.  If you downloaded 2019 before today then you need to download again.  When you install 2019 on the same server as 2017 and prior, copy over pvxwin32.exe.config to home, install the Crystal runtime update, and if that doesn't workk try replacing pvxwin32.exe.config in the earlier version with a known good copy.


------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------

Update 5/8/2019: I spoke to Sage. Apparently, the file from 2019 won't work 

For the 2019 release, the Sage 100 reporting DLL's have been recompiled so that it will use the current Crystal functionality and the pvxwin32.exe.config reflects the current functionality. The 2018 and 2017 pvxwin32.exe.config pushed down the version compatibility of Crystal to an earlier release. The previous releases 2018/2017 require the older pvxwin32.exe.config to work.

TL;DR: This is WAD and for upgrades requiring this workaround use the pvxwin32.exe.config from 2018 as 2019 version won't work.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

Original Message:
Sent: 04-09-2019 17:16
From: Doug Higgs
Subject: Unable to Cast COM Object

Update.  After an hour on the phone with Sage they determined the pvxwin32.ece.config file that gets installed on from cab1 is incorrect.  It is missing s lot of data.  Sage installed a v2018 pvxpin32.exe.config in the home folder of the 2016 installation and the printing worked fine.  So, there was an issue with the 2019 download that has been escalated.  If you downloaded 2019 before today then you need to download again.  When you install 2019 on the same server as 2017 and prior, copy over pvxwin32.exe.config to home, install the Crystal runtime update, and if that doesn't workk try replacing pvxwin32.exe.config in the earlier version with a known good copy.


------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------

It would be nice if Sage communicated this to the channel.... you know, because of the small issue that nobody can print after installing v2019.

------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------

Original Message:
Sent: 05-08-2019 12:27
From: Wayne Schulz
Subject: Unable to Cast COM Object

Update 5/8/2019: I spoke to Sage. Apparently, the file from 2019 won't work

For the 2019 release, the Sage 100 reporting DLL's have been recompiled so that it will use the current Crystal functionality and the pvxwin32.exe.config reflects the current functionality. The 2018 and 2017 pvxwin32.exe.config pushed down the version compatibility of Crystal to an earlier release. The previous releases 2018/2017 require the older pvxwin32.exe.config to work.

TL;DR: This is WAD and for upgrades requiring this workaround use the pvxwin32.exe.config from 2018 as 2019 version won't work.

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------


Original Message:
Sent: 04-09-2019 17:16
From: Doug Higgs
Subject: Unable to Cast COM Object

Update.  After an hour on the phone with Sage they determined the pvxwin32.ece.config file that gets installed on from cab1 is incorrect.  It is missing s lot of data.  Sage installed a v2018 pvxpin32.exe.config in the home folder of the 2016 installation and the printing worked fine.  So, there was an issue with the 2019 download that has been escalated.  If you downloaded 2019 before today then you need to download again.  When you install 2019 on the same server as 2017 and prior, copy over pvxwin32.exe.config to home, install the Crystal runtime update, and if that doesn't workk try replacing pvxwin32.exe.config in the earlier version with a known good copy.


------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc

Thanks - can verify this was a problem on a 2017 to 2019 upgrade. 
Replacing the file with one from 2018 did the trick - thanks!

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

@Wayne Schulz - did you have to put it in v2019 ​ or just v2017?

------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5
------------------------------

Original Message:
Sent: 05-06-2019 21:54
From: Wayne Schulz
Subject: Unable to Cast COM Object

Thanks - can verify this was a problem on a 2017 to 2019 upgrade.
Replacing the file with one from 2018 did the trick - thanks!

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

@Phil McIntosh I took the file from 2018 and put it into 2017. I did not have to do anything with 2019.​

I really haven't run into this too often because 95% of the time I'm working on the server which is not also serving as a workstation or a Terminal Server. 

BUT, my current upgrade IS using their server as a Terminal Server and people were RDP'ing into the 2017 system so as soon as I installed 2019 everyone on 2017 broke for printing/paperless ( I think I had to also reinstall their paperless driver ). 

Then when I fixed 2017 people that worked fine for those that RDP into the system but I had a few that were coming in via regular network connection that had to be fixed individually..... 

Thankfully I spotted Doug's post and that saved me a lot of hair pulling.

The only real new thing I have to add is Sage saying that the 2019 file won't work so keep a copy of 2018 ( they say they will look into uploading that to the KB ) 



------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------

Original Message:
Sent: 05-08-2019 13:02
From: Phil McIntosh
Subject: Unable to Cast COM Object

@Wayne Schulz - did you have to put it in v2019 ​ or just v2017?

------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5
------------------------------


Original Message:
Sent: 05-06-2019 21:54
From: Wayne Schulz
Subject: Unable to Cast COM Object

Thanks - can verify this was a problem on a 2017 to 2019 upgrade.
Replacing the file with one from 2018 did the trick - thanks!

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

@Phil McIntosh and @Wayne Schulz  be aware that if you install v2019 on the same server as a live version of 2017 or prior then you need to copy the 2018 pvxwin32.exe.config file to the 2017 or prior home folder or no users will be able to print from the 2017 or prior version.  If you do the intuitive process of trying to copy the 2019 pvxwin32.exe.config to the v2017 or prior home folder then users in v2017 or prior will not be able to print.

------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------

Original Message:
Sent: 05-08-2019 13:15
From: Wayne Schulz
Subject: Unable to Cast COM Object

@Phil McIntosh I took the file from 2018 and put it into 2017. I did not have to do anything with 2019.​

I really haven't run into this too often because 95% of the time I'm working on the server which is not also serving as a workstation or a Terminal Server.

BUT, my current upgrade IS using their server as a Terminal Server and people were RDP'ing into the 2017 system so as soon as I installed 2019 everyone on 2017 broke for printing/paperless ( I think I had to also reinstall their paperless driver ).

Then when I fixed 2017 people that worked fine for those that RDP into the system but I had a few that were coming in via regular network connection that had to be fixed individually.....

Thankfully I spotted Doug's post and that saved me a lot of hair pulling.

The only real new thing I have to add is Sage saying that the 2019 file won't work so keep a copy of 2018 ( they say they will look into uploading that to the KB )



------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------


Original Message:
Sent: 05-08-2019 13:02
From: Phil McIntosh
Subject: Unable to Cast COM Object

@Wayne Schulz - did you have to put it in v2019 ​ or just v2017?

------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5


Original Message:
Sent: 05-06-2019 21:54
From: Wayne Schulz
Subject: Unable to Cast COM Object

Thanks - can verify this was a problem on a 2017 to 2019 upgrade.
Replacing the file with one from 2018 did the trick - thanks!

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990

Sage is beyond horrible about communicating technical fixes out to partners / customers.

------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------

Original Message:
Sent: 05-08-2019 13:15
From: Wayne Schulz
Subject: Unable to Cast COM Object

@Phil McIntosh I took the file from 2018 and put it into 2017. I did not have to do anything with 2019.​

I really haven't run into this too often because 95% of the time I'm working on the server which is not also serving as a workstation or a Terminal Server.

BUT, my current upgrade IS using their server as a Terminal Server and people were RDP'ing into the 2017 system so as soon as I installed 2019 everyone on 2017 broke for printing/paperless ( I think I had to also reinstall their paperless driver ).

Then when I fixed 2017 people that worked fine for those that RDP into the system but I had a few that were coming in via regular network connection that had to be fixed individually.....

Thankfully I spotted Doug's post and that saved me a lot of hair pulling.

The only real new thing I have to add is Sage saying that the 2019 file won't work so keep a copy of 2018 ( they say they will look into uploading that to the KB )



------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990
------------------------------


Original Message:
Sent: 05-08-2019 13:02
From: Phil McIntosh
Subject: Unable to Cast COM Object

@Wayne Schulz - did you have to put it in v2019 ​ or just v2017?

------------------------------
Phil McIntosh
President
Friendly Systems, Inc.
Asheville NC
678.273.4010 ext 5


Original Message:
Sent: 05-06-2019 21:54
From: Wayne Schulz
Subject: Unable to Cast COM Object

Thanks - can verify this was a problem on a 2017 to 2019 upgrade.
Replacing the file with one from 2018 did the trick - thanks!

------------------------------
Wayne Schulz - Schulz Consulting - 860-516-8990