The connector uses 13531 that has not changed

The data uses 13540 to 13545 .... this range has not changed either

Check HELP and ABOUT to find out which port the data is using

You can always TEST the connection in the ODBC admin

The port

When I open Sage 50 and look into Help Support Info it says the port is 13450.

ODBC Admin what is that?  MySQL Connector?

Something has changed with the update.  I have another machine that does not have the update and everything is working fine.

The connector port prior to the update was 13540.  It has now changed to 13541.

The Connector starts at 13540 and then moves to 41 if 40 is busy.

Diagnosis tools like netstat will identify why 40 is busy  and Sage uses 41

The ODBC admin is found in the control panel and is used to TEST and administer database connections

There are several KB on the subject

Thanks for the response GwG.

May I assume the ODBC Connection error I am experiencing is an isolated incident and may not even be attributable to the latest update?  You have not heard of other ODBC connections that stopped working after the latest update?  Thank you

Any reply on this ? I have the same problem and cannot make it work. Access keep crashing and the connection does not happen.

I've been talking with Sage Tech Support about this issue since Monday (I installed on Sunday).  At that time I was told it was not an known issue.  However, I found 6 or 7 related issues that were changed between 2013.3 and 2014.1.  I spoke with them yesterday and they are continuing to setup a computer scenario similar to mine so they can test fully.  I have not heard from them today.

From the testing on my machine a several others, it is related to the update to 2014.1.  The ports are not updated properly but the driver is updated to the new one.

Ions did mention an error message but unfortunately did not mention what it was or what was done specifically to create it.  I have found several error messages that are related to the MySQL ODBC driver installations on several machines (I believe all Win7 computers - 32 and 64 bit).  They are below.

I clicked on the Configure button in the ODBC Data Sources admin utility on the Sage 50: Last Opened driver.

Then on one computer, after I clicked ok, I received

And I have confirmed the drivers on this computer were not installed correctly but cannot get it to install.

When I try to support my clients using Crystal Reports on Sage 50 2013 and Simply Accounting, on my own computer, I get this one when I try to create a new report or edit an old one I worked on last week

On some computers, they cannot hit configure at all because something is not installed correctly.  I've talked with a couple of IT people who cannot figure out why it would not install properly.  I've reinstalled the drivers myself on one computer and it still doesn't work.  On others, they can hit configure and change the port to the correct number and the custom forms that were having problems will work, so if Sage corrects their programming this will fix it but for those who have corrupted drivers, it may not (not all custom Crystal forms have problems only some).

All I can say for sure, is that Sage needs to know what the configurations are on the computers that are affected so they can do some testing.  Then maybe they can publish something that will help us get the drivers installed correctly, then hopefully they will fix the port issue with the next release.  I have not yet seen one computer where it is working properly but I had intentionally not done many installs once I heard others had some problems.  But now some of my clients are stuck on the new program and cannot do some reporting/printing so I had to start testing.

If anyone knows how to properly install the MySQL ODBC drivers so that both the 3.51 and 5.2a drivers will work on the same machine together, I and all my clients who want work done over the next couple of months would be most grateful.  Otherwise, I am going to have to do a system restore and eliminate 2014.1 from my system very soon.

I have the very same problem. In my case the setup is like this.

Database on a Windows XP PC used as server

Sage50 running on a Windows 7 client. Sage 50 itself connects fine.

Run Access on the Windows7 client, fires ODBC, fails

My failure is the same. I observed the same issues with missing or incompatible ODBC drivers. All the issues you mention I have. I also talked to Sage support and after an hower did not get anything useful from them. For now the only solution I see is rolling back all the machines to 2013.

For IONS i went and deleted the 2013 ODBC connection in the ODBC ADMIN... then closed and reopened the file. Returned to the ODBC admin and resetup the connection. In the advanced section  ENABLED RECONNECT.... tested.... so far so good.. For some othe crystal forms have had to LOG ON/OFF server to make sure the form know there is a new connector in town. I don't recall what message he orginally had.... i think it just crashed with no message.

Gregg,

Which driver was ions using?  Last Opened or filename.sai?

Are you guys have the third-party rights problems?

GwG fixed the problem as indicated above.  Thank you again GwG.

@Richard.  I was using the Old MySQL 3.51 driver.  It's now using the latest MySQL 5.2 Driver.

After reading through this entire thread a question came to mind. Does this problem affect any of the Custom Crystal Forms that may have been customized for use within Sage 50 for printing invoices, sales orders, purchase orders etc? Or is this problem just occuring if there needs to be interaction with the custom forms for further parameters to be input before printing?

Another one does this then affect such 3rd Party Programs such as MiSys, XLGL.... which all use OBDC connections. I gather the answer is yes.

Has this affected also any Excel workbooks created to pull the LIVE data and populate the workbook with data for further analysis. This again uses OBDC connection.

I ask the questions because no specific programs had been mentioned. If the answers are yes, then this presents lots of problems and a lot of unhappy Sage 50 users and many fixes to come.

Thanks for you input!!

Jo Anne

Coach

Any product that uses the ODBC connection including the Crystal Forms. The Crystal Invoice forms are less of a problem because they read from a CSV form but still in a round about way still use the ODBC connector. All the other 3rd party could have problems including the prepackage Excel reports. Im afraid there will not be one standard fix.... each client may have there own unique solution. Hopefully there will be a range of solutions.... if A does not work go to B and so forth.

Jo Anne and GWG

Can you run the only canned Crystal Report in the MS Office Documents program or does it tell you you do not have a valid account name or password?  Pick a 2014 file that has a password and test third-party rights at read-only and read/write.  It should work on read-only.

That will tell you if other products might have problems.  I haven't installed BI yet.

I can safely say not all Crystal Reports on 2014.1 will have problems, but the more highly programmed ones will especially for people who run more than one company file.  If all you have done is put a logo on an invoice and moved some columns around, it will probably not be a problem.  Even one of my clients who hits print once and gets two invoices with different layouts and a packing slip show up seemed to test fine but they went back to 2013 so I didn't get a chance to test fully.

To Richard S. Ridings : Use this ODBC Administrator instead of the one showed in Administrative Tools : C:\Windows\SysWOW64\odbcad32.exe.

The Shortcut in Administrative Tools points to C:\Windows\System32 and when I used it I had the same errors as you had.

I hope this helped.

To everyone : I still need help on that

I didn't find a clear instructions how to create the Sage ODBC connection for business connectivity. We need a Step by Step instructions, with all the details so we can troubleshoot more easily and go forward with other things less basic than this. There's a lot of people stuck here and I think that is fair to say that this should have been well documented somewhere in this forum. I'm sorry, GwG posted answer but it's not detailed and may be functionnal for him and if we don't have all the steps in details it may be dangerous to kill an existing configuration without being able to restore it back.

Thank you.

Thanks.  I've had that solution for a couple of weeks and have already updated my clients using 64 bit computers with shortcuts and showed them how to manually change the port properly so they can print and get the correct information on their reports.

I originally emailed Sage in Aug/13 about the custom forms in Sage 50 2014 and was assured

My analyst confirms no changes affecting custom forms of any kind for 2014.

I talked with Sage about the custom forms errors Oct 28, but on Nov 12 a consultant asked me for some help on the issue.  She told me she had called Sage and as of that day,

I see other people are having the same problem even though Sage assured me they had not heard from anyone else with this problem.  I have several clients who are very unhappy.

On Nov 7 Sage called me back and indicated that they had confirmed the problem is an issue on 64 bit computers but not 32 bit computers.  They will apparently have it fixed for the next release.  I think this is great but the only problem I see is that I originally found the problem on my 32 bit computer within a half hour of getting 2014.1 installed.  On Oct 28 and 29 I demoed several problems for R&D staff on my computer.

There is an article in the knowledgebase for 2014 about Cannot open SQL Server last edited Oct 14/13 but the resolutions do not deal with this issue.  I cannot tell you how disappointed I am in Sage about this whole issue and not just because of the two days I spent in Oct resolving it when Sage has not (to my knowledge even as of today) but because of the money end users have had to waste to get it resolved.  And also the fact that no one at Sage appears to care that if it does print, wrong information may be showing up on reports and forms and the end users may not realise it because they expect it to work as it did in the past.  There has been more than enough time to get some articles updated/written to help users.

GwG's solution will probably work properly for many users who are only running one company file but I have proven with testing on another Certified Consultant's computer, that I can print from one company file and get the information from another one using Sage's canned report.  So it will not work for everyone.  Normally the program will recreate all DSN's needed when opening the file, but it is not updating them properly.  I have not deleted mine to test.

GTGroup

I have just been trading emails with the consultant I mentioned in my last message and found part of her issue was that the security was not set correctly.  She had her file set to Read/Write for Third-Party rights but due to another non-change in the program between 2013 and 2014, you may need to set it back to read-only, save the changes and then go back in and then change it to read/write.  You cannot use Read-only.  I do not know if Sage will correct this but it has been reported to them.

Seems as if there is no standard solution. In some cases the solution may involve a registry clean-up.

HKEY_CURRENT_USER\Software\ODBC\ODBC.INI. Renaming this key and have the system set up a new key. In one case there was a conflict between HKEY_CURRENT_USER\Software\ODBC\ODBC.INI and

HKEY_CURRENT_USER\Software\ODBC\ODBC.INI\ODBC Data Sources. Can also check the users permissions to these KEYS.