Got the update message as well this morning.

No clue about the error 65, but I would probably get the update installed as soon as possible.

Why does Sage not announce that this update is imminent? We've received a number of calls from clients asking what they should do.

Agreed!
Barbara's comment speaks exactly to my thread in the Partner section of Sage City. Marketing controls all notifications, and technical information has no Sage plan for release (as a warning to customers / partners). We're constantly being reactive, and it is not (to put it mildly) the most efficient way to work.
Sage support is overloaded when something like this happens, and our customers ask us for help urgently. Terminal Servers, pre-requisites requiring admin credentials and a server reboot... These things should have a planned roll-out (with advance warnings).

I had a similar issue although not with the same error message.

In my case a customer was unable to click though and install the mandatory update. There are several problems, IMO, with the installer which does not display any useful error information and also covers any other windows on the desktop and also prevents you from moving the installer window.

When I downloaded Sage Exchange Desktop 2.0 installer from sageexchange.com and ran it I was suddenly able to see the problem.

The Sage Exchange Desktop 2.0 would not install on a version of Windows earlier than 7.  This is understandable since Sage no longer supports those versions with Sage 100. However, there are likely quite a few end users still making use of old XP or Server 2008 machines. This mandatory update did not test for the compatibility of the underlying OS or give any type of warning message upon failure.

It appears that this update to Sage Exchange Desktop 2.0 is required before June 2018. So if you are running into a version issue you have some time to update.

I suggest upgrading the Windows versions first then the Sage versions.

Hi all.

I hope the following information will be of help to anyone encountering this issue:

To address the notifications that users with Sage Exchange Desktop 1.x are receiving about a new version of Sage Exchange, and if users have installed Sage Exchange Desktop (SED) 2.0, but the version of Sage 100 may not be compatible with 2.0...

Please take a look at the following Sage Knowledgebase KB articles at http://support.na.sage.com (login is required if you plan on accessing a download article):
84659 [Is my version compatible with Sage Exchange update to 2.0?]
84681 [Error: "You must wait while the Sage Exchange Desktop service attempts to install or restart on your system" with Sage Exchange Desktop 2.0 installed on a workstation]

Also note that Sage 100 2017 is already compatible with Sage Exchange Desktop (SED) 2.0, and in fact requires it.

I hope this helps.

Sincerely,

Paul Chen
Customer Support, Advisory
North America Services

Hi all.

I hope the following information will be of help to anyone encountering this issue:

To address the notifications that users with Sage Exchange Desktop 1.x are receiving about a new version of Sage Exchange, and if users have installed Sage Exchange Desktop (SED) 2.0, but the version of Sage 100 may not be compatible with 2.0...

Please take a look at the following Sage Knowledgebase KB articles at http://support.na.sage.com (login is required if you plan on accessing a download article):
84659 [Is my version compatible with Sage Exchange update to 2.0?]
84681 [Error: "You must wait while the Sage Exchange Desktop service attempts to install or restart on your system" with Sage Exchange Desktop 2.0 installed on a workstation]

Also note that Sage 100 2017 is already compatible with Sage Exchange Desktop (SED) 2.0, and in fact requires it.

I hope this helps.

Sincerely,

Paul Chen
Customer Support, Advisory
North America Services

Here was the information I really needed, which is in one of the KBs that Paul mentioned (thank you, Mr. Chen)
For those of you who may not be logged into the Sage Portal I copy it here for your benefit:
..per KB 84659, the following should be noted:
Description
Is my version compatible with Sage Exchange update to 2.0.
Getting a prompt to update Sage Exchange to version 2.0

Cause
Sage Exchange pushed out an update. Only compatible versions should update.
Resolution
Sage Exchange 2.0 is NOT compatible with the following versions:
Version 2013 all product updates (5.00.0-5.00.9)
Version 2014 all product updates (5.10.0 - 5.10.7)
Version 2015 with no product update (5.20.0)
Version 2016 with no product update (5.30.0)
Windows XP
If Sage Exchange 2.0 has been installed, uninstall and install version 1.0.

Wayne Schulz - to your point, we tried to install SE 2.0 on a Terminal Server and it just flashed on and off the screen. There was nothing we could do except log out of our session to kill it. Then of course I found out our version doesn't support SE 2.0, doh! Onward through the fog..

Thanks, Cullen! I have updated article 84659 with better wording.

Paul Chen
Customer Support, Advisory
North America Services

Thanks Paul, you are a gentleman and a scholar.

In case anyone is wondering, the Error 65 has not returned and I've decided it was a sheer coincidence that it occurred at the same time as this SE 2.0 upgrade message.

I would like to just take a second to echo the sentiments of barbgold and Kevin M that a little advance warning would have been really nice. It does seem like we spend a great deal of time trying to get that barn door closed after the horse has gotten out!

There are going to be a couple "gotcha" issues that arise as June 2018 approaches.

1. End users actively using a version of Sage 100 2013 or 2014 - both unsupported with SED 2.0 but reliant on it for functionality.
2. End users running a supported version of Sage 100 but an unsupported OS (essentially anything lower than Windows 7)

I have a couple large-ish customers on Sage 100 2014 who have been staying as-is due to cost/complexity of upgrading. These users are going to be required to upgrade if they wish to continue using SED 2.0 type functionality - basically charging CC within Sage 100 or storing cards.

Thanks Wayne,

Another interesting nuance to this issue is that in KB 84659 [Is my version compatible with Sage Exchange update to 2.0?] there is a link for "those on Citrix environments, see the following Sage Payments KB article:"
Here is the link (fair warning, it just takes you to the Sage Payments login screen):
support.sagepayments.com/.../A-Citrix-environment-and-the-Sage-Exchange-application-reinstalls-every-time-I-log-in
I have never logged into that site, does anyone know how I can do so?

Cullen:

Try visiting that link (support.sagepayments.com/.../A-Citrix-environment-and-the-Sage-Exchange-application-reinstalls-every-time-I-log-in) and then scroll down...

Sincerely,

Paul Chen
Support Analyst, Advisory
North America Services

Thanks again, Paul;

Yes, I found it by searching for that article title. Interesting article, says mostly they don't recommend using it in Citrix - which seems very odd of them to say. There is a link to a lengthy Citrix article which talks a lot about "ClickOnce applications".

Here is the text, with the link to the Citrix article:

A Citrix environment and the Sage Exchange application reinstalls every time I log in.

Description

I'm on a Citrix environment and the Sage Exchange application reinstalls every time I log in.  Why is this?

Resolution

Sage Exchange Desktop is a ClickOnce Application, which is stored in the Local Settings of the user’s profile.  When a user ends a Citrix session, the user’s Local Settings are not saved. The result is that any Citrix user running a ClickOnce Application will be required to reinstall the application whenever a new session is begun.

Sage does not recommend or support operating the Sage Exchange Desktop application in a Citrix environment.  Citrix, however, has published several tips for using ClickOnce Applications in their environment, which are available here at Citrix’s online Knowledge Center: