OOPS, too soon, still beta

------------------------------
Beth Bowers
(269) 358-0989
------------------------------

But it was exciting while it lasted.......

OOPS, too soon, still beta

------------------------------
Beth Bowers
(269) 358-0989

Released.

Community Hub

But it was exciting while it lasted.......

OOPS, too soon, still beta

------------------------------
Beth Bowers
(269) 358-0989

Nice - Thanks for posting that @Jeff Schwenk !

Released.

Community Hub

But it was exciting while it lasted.......

OOPS, too soon, still beta

------------------------------
Beth Bowers
(269) 358-0989

ALSO - this fixes the following without having to change that check box.  AND - everyone needs to be out in order to install the fix.

Nice - Thanks for posting that @Jeff Schwenk !

Released.

Community Hub

But it was exciting while it lasted.......

OOPS, too soon, still beta

------------------------------
Beth Bowers
(269) 358-0989

HOLD THE PHONE.  My 3rd install was on a TS system.  The install on the server went fine.  Installing on the TS LOOKED fine, but trying to print gave me the error below.  I installed again (making sure I ran as Admin), ran SAGE as Admin - no love.  I had to reinstall their workstation.  The server is now at one ODBC driver and the TS at another, but it's not causing issues.  Have let Sage know about this issue and am waiting on a reply.  This was my 3rd install, first failure. It worked on a Win 11 single user (me), SWK cloud install (although I did have to run it twice).

ALSO - this fixes the following without having to change that check box.  AND - everyone needs to be out in order to install the fix.

Nice - Thanks for posting that @Jeff Schwenk !

Released.

Community Hub

But it was exciting while it lasted.......

OOPS, too soon, still beta

------------------------------
Beth Bowers
(269) 358-0989

Do NOT, I repeat NOT blindly install a patch provided by a 3rd party MD support person and read the accompanying PDF FIRST.  The patch does not work on a 32 bit install.  CSODBC and printing/odbc queries at the server are offline until they figure out how to undo the damage.  I will try switching to 64 bit tonight.  Maybe go back to 32 after that.  I think that would reset the DLL's

HOLD THE PHONE.  My 3rd install was on a TS system.  The install on the server went fine.  Installing on the TS LOOKED fine, but trying to print gave me the error below.  I installed again (making sure I ran as Admin), ran SAGE as Admin - no love.  I had to reinstall their workstation.  The server is now at one ODBC driver and the TS at another, but it's not causing issues.  Have let Sage know about this issue and am waiting on a reply.  This was my 3rd install, first failure. It worked on a Win 11 single user (me), SWK cloud install (although I did have to run it twice).

ALSO - this fixes the following without having to change that check box.  AND - everyone needs to be out in order to install the fix.

Nice - Thanks for posting that @Jeff Schwenk !

Released.

Community Hub

But it was exciting while it lasted.......

OOPS, too soon, still beta

------------------------------
Beth Bowers
(269) 358-0989

My client was 64 bit, so not sure what's up with that. 

Do NOT, I repeat NOT blindly install a patch provided by a 3rd party MD support person and read the accompanying PDF FIRST.  The patch does not work on a 32 bit install.  CSODBC and printing/odbc queries at the server are offline until they figure out how to undo the damage.  I will try switching to 64 bit tonight.  Maybe go back to 32 after that.  I think that would reset the DLL's

HOLD THE PHONE.  My 3rd install was on a TS system.  The install on the server went fine.  Installing on the TS LOOKED fine, but trying to print gave me the error below.  I installed again (making sure I ran as Admin), ran SAGE as Admin - no love.  I had to reinstall their workstation.  The server is now at one ODBC driver and the TS at another, but it's not causing issues.  Have let Sage know about this issue and am waiting on a reply.  This was my 3rd install, first failure. It worked on a Win 11 single user (me), SWK cloud install (although I did have to run it twice).

ALSO - this fixes the following without having to change that check box.  AND - everyone needs to be out in order to install the fix.

Nice - Thanks for posting that @Jeff Schwenk !

Released.

Community Hub

But it was exciting while it lasted.......

OOPS, too soon, still beta

------------------------------
Beth Bowers
(269) 358-0989

Please see: Error: 6830968 Windows could not start CS ODBC Driver Service

OK, I had to revisit my TS client because SI stopped working after this fix, too, and even though I had their printing working again, not SI.  So after uninstalling and manually renaming and rebooting, then starting all over, I had SI working.  Then I had to ask myself two things - 1) do I want to get any sleep tonight? and 2) did I fell lucky?  Well, did I?

So I went ahead and rolled the dice and installed the fix again and tested printing and SI afterwords and all is well.  During my uninstalling I had a file locked, so MAYBE that was the issue in the first place.  I guess instead of thinking I can just whip this fix in, I'll make sure I reboot before installing it next time.

Please see: Error: 6830968 Windows could not start CS ODBC Driver Service

Does anyone have a workaround for this?  Downgrade to 32-bit?  One of my FEW 64-bit clients just encountered this.  Ran fine on Friday, not today.  Tried several workstations.  Any word on when the download patch link will be activated?  This does not bode well for the upcoming 64-bit ONLY v2025 release.

OK, I had to revisit my TS client because SI stopped working after this fix, too, and even though I had their printing working again, not SI.  So after uninstalling and manually renaming and rebooting, then starting all over, I had SI working.  Then I had to ask myself two things - 1) do I want to get any sleep tonight? and 2) did I fell lucky?  Well, did I?

So I went ahead and rolled the dice and installed the fix again and tested printing and SI afterwords and all is well.  During my uninstalling I had a file locked, so MAYBE that was the issue in the first place.  I guess instead of thinking I can just whip this fix in, I'll make sure I reboot before installing it next time.

Please see: Error: 6830968 Windows could not start CS ODBC Driver Service

@Jeff Schwenk - what exact issue is it? (There's too many now!)

Does anyone have a workaround for this?  Downgrade to 32-bit?  One of my FEW 64-bit clients just encountered this.  Ran fine on Friday, not today.  Tried several workstations.  Any word on when the download patch link will be activated?  This does not bode well for the upcoming 64-bit ONLY v2025 release.

OK, I had to revisit my TS client because SI stopped working after this fix, too, and even though I had their printing working again, not SI.  So after uninstalling and manually renaming and rebooting, then starting all over, I had SI working.  Then I had to ask myself two things - 1) do I want to get any sleep tonight? and 2) did I fell lucky?  Well, did I?

So I went ahead and rolled the dice and installed the fix again and tested printing and SI afterwords and all is well.  During my uninstalling I had a file locked, so MAYBE that was the issue in the first place.  I guess instead of thinking I can just whip this fix in, I'll make sure I reboot before installing it next time.

Please see: Error: 6830968 Windows could not start CS ODBC Driver Service

Oops, sorry.  Trying to print and the window simply closes.  They are unable to print invoices today.  Reboot workstation, reboot server, try different workstation.  Only thing I can think of doing is to reinstall 32 bit.

@Jeff Schwenk - what exact issue is it? (There's too many now!)

Does anyone have a workaround for this?  Downgrade to 32-bit?  One of my FEW 64-bit clients just encountered this.  Ran fine on Friday, not today.  Tried several workstations.  Any word on when the download patch link will be activated?  This does not bode well for the upcoming 64-bit ONLY v2025 release.

OK, I had to revisit my TS client because SI stopped working after this fix, too, and even though I had their printing working again, not SI.  So after uninstalling and manually renaming and rebooting, then starting all over, I had SI working.  Then I had to ask myself two things - 1) do I want to get any sleep tonight? and 2) did I fell lucky?  Well, did I?

So I went ahead and rolled the dice and installed the fix again and tested printing and SI afterwords and all is well.  During my uninstalling I had a file locked, so MAYBE that was the issue in the first place.  I guess instead of thinking I can just whip this fix in, I'll make sure I reboot before installing it next time.

Please see: Error: 6830968 Windows could not start CS ODBC Driver Service

Oops, sorry.  Trying to print and the window simply closes.  They are unable to print invoices today.  Reboot workstation, reboot server, try different workstation.  Only thing I can think of doing is to reinstall 32 bit.

@Jeff Schwenk - what exact issue is it? (There's too many now!)

Does anyone have a workaround for this?  Downgrade to 32-bit?  One of my FEW 64-bit clients just encountered this.  Ran fine on Friday, not today.  Tried several workstations.  Any word on when the download patch link will be activated?  This does not bode well for the upcoming 64-bit ONLY v2025 release.

OK, I had to revisit my TS client because SI stopped working after this fix, too, and even though I had their printing working again, not SI.  So after uninstalling and manually renaming and rebooting, then starting all over, I had SI working.  Then I had to ask myself two things - 1) do I want to get any sleep tonight? and 2) did I fell lucky?  Well, did I?

So I went ahead and rolled the dice and installed the fix again and tested printing and SI afterwords and all is well.  During my uninstalling I had a file locked, so MAYBE that was the issue in the first place.  I guess instead of thinking I can just whip this fix in, I'll make sure I reboot before installing it next time.

Please see: Error: 6830968 Windows could not start CS ODBC Driver Service

Not sure if you covered this already but have you tried running Mas90 style? It's possible you'll get a better error that way. In case it works running that way and the normal way uses CS ODBC,  maybe it means the newer 64-bit ODBC component from the fix is different between workstation and server.

Oops, sorry.  Trying to print and the window simply closes.  They are unable to print invoices today.  Reboot workstation, reboot server, try different workstation.  Only thing I can think of doing is to reinstall 32 bit.

@Jeff Schwenk - what exact issue is it? (There's too many now!)

Does anyone have a workaround for this?  Downgrade to 32-bit?  One of my FEW 64-bit clients just encountered this.  Ran fine on Friday, not today.  Tried several workstations.  Any word on when the download patch link will be activated?  This does not bode well for the upcoming 64-bit ONLY v2025 release.

OK, I had to revisit my TS client because SI stopped working after this fix, too, and even though I had their printing working again, not SI.  So after uninstalling and manually renaming and rebooting, then starting all over, I had SI working.  Then I had to ask myself two things - 1) do I want to get any sleep tonight? and 2) did I fell lucky?  Well, did I?

So I went ahead and rolled the dice and installed the fix again and tested printing and SI afterwords and all is well.  During my uninstalling I had a file locked, so MAYBE that was the issue in the first place.  I guess instead of thinking I can just whip this fix in, I'll make sure I reboot before installing it next time.

Please see: Error: 6830968 Windows could not start CS ODBC Driver Service

What fix @Beth Bowers?  The link was taken down per the Community announcement.  Is it back?  Alnoor, client did run in 90mode, no dice.

Not sure if you covered this already but have you tried running Mas90 style? It's possible you'll get a better error that way. In case it works running that way and the normal way uses CS ODBC,  maybe it means the newer 64-bit ODBC component from the fix is different between workstation and server.

Oops, sorry.  Trying to print and the window simply closes.  They are unable to print invoices today.  Reboot workstation, reboot server, try different workstation.  Only thing I can think of doing is to reinstall 32 bit.

@Jeff Schwenk - what exact issue is it? (There's too many now!)

Does anyone have a workaround for this?  Downgrade to 32-bit?  One of my FEW 64-bit clients just encountered this.  Ran fine on Friday, not today.  Tried several workstations.  Any word on when the download patch link will be activated?  This does not bode well for the upcoming 64-bit ONLY v2025 release.

OK, I had to revisit my TS client because SI stopped working after this fix, too, and even though I had their printing working again, not SI.  So after uninstalling and manually renaming and rebooting, then starting all over, I had SI working.  Then I had to ask myself two things - 1) do I want to get any sleep tonight? and 2) did I fell lucky?  Well, did I?

So I went ahead and rolled the dice and installed the fix again and tested printing and SI afterwords and all is well.  During my uninstalling I had a file locked, so MAYBE that was the issue in the first place.  I guess instead of thinking I can just whip this fix in, I'll make sure I reboot before installing it next time.

Please see: Error: 6830968 Windows could not start CS ODBC Driver Service

I must admit to being a little confused by Sage's KB article -Print screen disappears intermittently without printing or previewing report in Sage 100 64-bit

Where it indicates: 

• This update must be reapplied if the Sage 100 Server or workstation are reinstalled

Is this saying that if I install this "fix" and then run workstation setup on a workstation where I've never install Sage 100 before that I must also manually apply this patch? 

The download PDF seems to imply that you have to manually apply this patch if the workstation is ever re-installed? 

Hmmm, once again, saved by the unwillingness to move people to the 64-bit version.....  But I agree that it is ambiguous as to future WS installations.  One would think (dangerous, I know) that once the patch is installed on the server, future WS installations (if done from the wksetup folder) would install the latest dll's.

Also, correct me if I am befuddled, but isn't 2025 going to be ONLY 64 bit?  That WILL be interesting.

Perhaps a question for Sage at MOTM - how responsive will they be when issues crop up for 2025??

I must admit to being a little confused by Sage's KB article -Print screen disappears intermittently without printing or previewing report in Sage 100 64-bit

Where it indicates: 

• This update must be reapplied if the Sage 100 Server or workstation are reinstalled

Is this saying that if I install this "fix" and then run workstation setup on a workstation where I've never install Sage 100 before that I must also manually apply this patch? 

The download PDF seems to imply that you have to manually apply this patch if the workstation is ever re-installed? 

The 32 to 64-bit is going to be confusing.

First, you won't be able to install 32-bit and 64-bit on the same server/workstation.

So that means you'll need to flip the 32 to 64 bit right after upgrading

Second, some ISVs are already indicating that they are 64-bit read but swapping to 64-bit requires a reinstallation of their solution (let that sink in and ask yourself how you are going to get 64-bit Sage 100 staged and ready to test prior to go-live without bringing down 32-bit Sage).


At the pace the Sage 100 ecosystem is being ignored/neglected I suspect people will fall back to something like a five+ year upgrade cycle to avoid this nonsense.

Hmmm, once again, saved by the unwillingness to move people to the 64-bit version.....  But I agree that it is ambiguous as to future WS installations.  One would think (dangerous, I know) that once the patch is installed on the server, future WS installations (if done from the wksetup folder) would install the latest dll's.

Also, correct me if I am befuddled, but isn't 2025 going to be ONLY 64 bit?  That WILL be interesting.

Perhaps a question for Sage at MOTM - how responsive will they be when issues crop up for 2025??

I must admit to being a little confused by Sage's KB article -Print screen disappears intermittently without printing or previewing report in Sage 100 64-bit

Where it indicates: 

• This update must be reapplied if the Sage 100 Server or workstation are reinstalled

Is this saying that if I install this "fix" and then run workstation setup on a workstation where I've never install Sage 100 before that I must also manually apply this patch? 

The download PDF seems to imply that you have to manually apply this patch if the workstation is ever re-installed? 

Good questions Wayne.  I just posted a thread on Sage City to get that ball rolling:

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/243984/when-sage-100-becomes-64-bit-only-how-to-handle-same-server-upgrades-where-the-old-version-is-running-32-bit

Feel free to add your own concerns (...ISV's / enhancements...).

The 32 to 64-bit is going to be confusing.

First, you won't be able to install 32-bit and 64-bit on the same server/workstation.

So that means you'll need to flip the 32 to 64 bit right after upgrading

Second, some ISVs are already indicating that they are 64-bit read but swapping to 64-bit requires a reinstallation of their solution (let that sink in and ask yourself how you are going to get 64-bit Sage 100 staged and ready to test prior to go-live without bringing down 32-bit Sage).


At the pace the Sage 100 ecosystem is being ignored/neglected I suspect people will fall back to something like a five+ year upgrade cycle to avoid this nonsense.

Hmmm, once again, saved by the unwillingness to move people to the 64-bit version.....  But I agree that it is ambiguous as to future WS installations.  One would think (dangerous, I know) that once the patch is installed on the server, future WS installations (if done from the wksetup folder) would install the latest dll's.

Also, correct me if I am befuddled, but isn't 2025 going to be ONLY 64 bit?  That WILL be interesting.

Perhaps a question for Sage at MOTM - how responsive will they be when issues crop up for 2025??

I must admit to being a little confused by Sage's KB article -Print screen disappears intermittently without printing or previewing report in Sage 100 64-bit

Where it indicates: 

• This update must be reapplied if the Sage 100 Server or workstation are reinstalled

Is this saying that if I install this "fix" and then run workstation setup on a workstation where I've never install Sage 100 before that I must also manually apply this patch? 

The download PDF seems to imply that you have to manually apply this patch if the workstation is ever re-installed? 

Isn't the 64-bit as the sole option for version 2026+? 

Good questions Wayne.  I just posted a thread on Sage City to get that ball rolling:

https://communityhub.sage.com/us/sage100/f/technical-and-installation-discussions/243984/when-sage-100-becomes-64-bit-only-how-to-handle-same-server-upgrades-where-the-old-version-is-running-32-bit

Feel free to add your own concerns (...ISV's / enhancements...).

The 32 to 64-bit is going to be confusing.

First, you won't be able to install 32-bit and 64-bit on the same server/workstation.

So that means you'll need to flip the 32 to 64 bit right after upgrading

Second, some ISVs are already indicating that they are 64-bit read but swapping to 64-bit requires a reinstallation of their solution (let that sink in and ask yourself how you are going to get 64-bit Sage 100 staged and ready to test prior to go-live without bringing down 32-bit Sage).


At the pace the Sage 100 ecosystem is being ignored/neglected I suspect people will fall back to something like a five+ year upgrade cycle to avoid this nonsense.

Hmmm, once again, saved by the unwillingness to move people to the 64-bit version.....  But I agree that it is ambiguous as to future WS installations.  One would think (dangerous, I know) that once the patch is installed on the server, future WS installations (if done from the wksetup folder) would install the latest dll's.

Also, correct me if I am befuddled, but isn't 2025 going to be ONLY 64 bit?  That WILL be interesting.

Perhaps a question for Sage at MOTM - how responsive will they be when issues crop up for 2025??

I must admit to being a little confused by Sage's KB article -Print screen disappears intermittently without printing or previewing report in Sage 100 64-bit

Where it indicates: 

• This update must be reapplied if the Sage 100 Server or workstation are reinstalled

Is this saying that if I install this "fix" and then run workstation setup on a workstation where I've never install Sage 100 before that I must also manually apply this patch? 

The download PDF seems to imply that you have to manually apply this patch if the workstation is ever re-installed? 

The 32 to 64-bit is going to be confusing.

First, you won't be able to install 32-bit and 64-bit on the same server/workstation.

So that means you'll need to flip the 32 to 64 bit right after upgrading

Second, some ISVs are already indicating that they are 64-bit read but swapping to 64-bit requires a reinstallation of their solution (let that sink in and ask yourself how you are going to get 64-bit Sage 100 staged and ready to test prior to go-live without bringing down 32-bit Sage).


At the pace the Sage 100 ecosystem is being ignored/neglected I suspect people will fall back to something like a five+ year upgrade cycle to avoid this nonsense.

Hmmm, once again, saved by the unwillingness to move people to the 64-bit version.....  But I agree that it is ambiguous as to future WS installations.  One would think (dangerous, I know) that once the patch is installed on the server, future WS installations (if done from the wksetup folder) would install the latest dll's.

Also, correct me if I am befuddled, but isn't 2025 going to be ONLY 64 bit?  That WILL be interesting.

Perhaps a question for Sage at MOTM - how responsive will they be when issues crop up for 2025??

I must admit to being a little confused by Sage's KB article -Print screen disappears intermittently without printing or previewing report in Sage 100 64-bit

Where it indicates: 

• This update must be reapplied if the Sage 100 Server or workstation are reinstalled

Is this saying that if I install this "fix" and then run workstation setup on a workstation where I've never install Sage 100 before that I must also manually apply this patch? 

The download PDF seems to imply that you have to manually apply this patch if the workstation is ever re-installed?