Sometimes when you try to connect the .net to Sybase server then you might have received driver error “[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified.” When you try to connect .net the there is an ODBC connection setup which is pointed from the report Server to the data server but the ODBC does not have the same name which is used in designing. Suppose when you start FRx and open the Company | Information | System Specific tab then in their you will see that your data source name is reporter. On the report Server the ODBC which you have setup is called Report Server. And this is the main reason for occurring this error. This error prevent from connecting .net to the Sybase server.
Fix using Advanced System Repair Tool
Why this driver error occurs?
While connecting .net to the Sybase server there is ODBC connection setup which is pointed from the report Server to the data server but the ODBC used doesn’t have the same name which is used in designing.
This problem may also occur due to the virus program which is running in your system.
What are the symptoms?
40002 – IM002: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Database connection error number 1. RDO Error #0 IM002: [Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified Accounting system registration not found for system type: 0′ occurs in Report Server when sending a report to the queue.
How to fix this driver error message?
When you receive this error then stop connecting .net to Sybase server and start Registry Editor.
- To start Registry Editor, click on start button and type regedit in the search box and press enter.
- Select the following key HKEY_LOCAL_MACHINE\SOFTWARE\ODBC.
- Go to the security menu and from this menu select and click on the permissions option.
- Click to the account which is used for making connections.
- Then close registry Editor and restart your system.
- When system gets restarted then again try to connect .net to the Sybase server.
If you again receive this following driver error and unable to connect .net to the Sybase server then download third party repair tool because third party repair tool can only solve this driver error permanently. To fix driver error is quite complicated but if you have installed third party repair tool in your system then you can easily fix driver error without any tension.