GP 18.3.1200 (2020)Excel 2013 and 2019Error:Initialization of the data source failed.Checked the database server or contact your database administrator. Mare sure the external database is available, and then try the operation again. If you see this message again, created a new data source to connect to the database.ThanksDedra#Technical#BIandReporting#GP2018and2018R2
This is likely an issue with the ODBC address. Did the server or instance name change?
It would be looking for a 32-bit ODBC (you'll find what it is looking for in the Data Definition in Excel). If that exactly-named ODBC does not exist on a machine then it can't connect and you'll have to create the ODBC source.
Are you seeing where two users using the SAME machine get different results or is the issue really a difference in the machine?
Please Remember to email firstname.lastname@example.org for any support issues or questions not related to a particular project
Business Applications Practice Manager
Phone: (770) 728-8083 Ext 1
Mobile: (770) 906-4504
FOR IMMEDIATE ASSISTANCE WITH SUPPORT ISSUES PLEASE EMAIL: SUPPORT.DESK@AISLINGDYNAMICS.COM OR CLICK THE LINK TO THE RIGHT
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. This message contains confidential information and is intended only for the individuals named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited.
Updated another refreshable excel report and have the same issue again. User with GP installed locally can open the file without errors, users who login to GP via RDS or do not have GP login get the Initialization of the data source failed.message. Below are the connection strings from the files based on GP versions that is the only thing that it showing as being different between excel reports .....GP2018 (only works with GP installed locally)
Provider=SQLNCLI11.1;Integrated Security=SSPI;Persist Security Info=True;Initial Catalog=XXC;Data Source=SVR-XXXXX;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=PC-XXXXX;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False;Application Intent=READWRITE
GP2016 (works with or without GP installed locally)
Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=True;Initial Catalog=SXX;Data Source=SVR-XXX;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=PC-XXXX;Use Encryption for Data=False;Tag with column collation when possible=False
If you've found this thread useful, dive deeper into User Group community content by role