You are currently offline, waiting for your internet to reconnect

Error "Data source name not found or no default driver specified" When Viewing the Input Screen or the Segment Trees in FRx Forecaster

This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft Business Solutions-Axapta 3.0 is now part of Microsoft Dynamics AX 3.0. All references to Microsoft Business Solutions-Axapta and Microsoft Axapta pertain to Microsoft Dynamics AX.
TechKnowledge Content
Note This article applies only to Forecaster 6.5.


Error - "Data source name not found or no default driver specified" occurs when viewing the Input Screen or the Segment Trees in FRx Forecaster.


There are three things you will want to check for the Data Source Name not found message:

1. Verify the Data Source Name (ODBC) is correctly identified in FRx Forecaster: There are two files that store the Data Source Name the FRx Forecaster uses. These files are stored on the Web Server. They are the msdfmap.ini and the global.asa file.

Msdfmap.ini: This file is stored in the Windows/WinNT folder on the IIS server. The installation of FRx Forecaster adds a section to this file. You can verify the ODBC by locating the following entry. DSN is the ODBC or Data Source Name that FRx Forecaster uses.

[connect FRxForecasterDB]

Global.asa: This file is stored in the root of the FRx Forecaster Code folder on the IIS server. Open this file with Notepad and look for the following entry:

Application("HelmRecs_ConnectionStringDb") = "DSN=FRxForecaster;DATABASE=FRxForecasterDB"

2. Reinstall MDAC (Microsoft Data Access Components): It could be an issue with the Microsoft Data Access Components on the IIS server. You can verify the version of MDAC by doing the following:

A. Locate the msado15.dll file located at C:\Program Files\Common Files\System\ado.
B. Right-click the msado15.dll file and select properties.
C. Click on the version tab. This will tell you what version of MDAC is installed on this machine

You will want to make sure that the database server had the same or a higher version of MDAC than the Web (IIS) server.

3. MSDFMAP.INI could be damaged: The MSDFMAP.INI may include the Connect FRx Forecaster section (see Step 1 above), but FRx Forecaster is not able to properly read the file. It could be an issue that the file is damaged. If you apply or reapply a Service Pack for the Operating System, this file will be recreated.

After recreating the MSDFMAP.INI, you will need to enter the Connect FRx Forecaster section again or you can reinstall the IIS components for FRx Forecaster and it will add that section to the file.

For steps about how to remove FRx Forecaster, see Knowledge Base Article

This article was TechKnowledge Document ID: 29168

Article ID: 858612 - Last Review: 01/11/2015 06:12:08 - Revision: 4.0

Microsoft Business Solutions–Great Plains 7.5, Microsoft Dynamics AX 3.0

  • kbnosurvey kbarchive kbsolomonfrx kbgreatplainsfrx kbaxaptafrx kbmbsmigrate KB858612