How To Fix: Microsoft OLE DB Provider for SQL Server Error 80040e4d



RECOMMENDED: Click here to fix Windows errors and optimize system performance

When you try to use an ODBC data source name (DSN) to open a connection of ActiveX data objects (ADO) to a SQL Server database from an Active Server Pages (ASP) page, you can receive the following error message:

Microsoft OLE DB Provider for ODBC Drivers (0x80040E4D)
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user ‘(null)’. Reason: Not associated with a trusted SQL Server connection.

What are the causes of this error?

1. You have connected to an incorrect MSSQL server.

2 The database user name and password may be invalid.



Update:

We now recommend using this tool for your error. Additionally, this tool fixes common computer errors, protects you against file loss, malware, hardware failures and optimizes your PC for maximum performance. You can fix your PC problems quickly and prevent others from happening with this software:

  • Step 1 : Download PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista – Microsoft Gold Certified).
  • Step 2 : Click “Start Scan” to find Windows registry issues that could be causing PC problems.
  • Step 3 : Click “Repair All” to fix all issues.

download



Verification of ODBC data sources

It is necessary to check the ODBC data sources used by WhatsUp Gold to access the database, then transfer the changes to the WhatsUp Gold database configuration utility. To do this, you must perform the following steps:

ODBC connection

  1. Select from the Windows Start menu: For a 32-bit Windows operating system: Control Panel > Administrative Tools > Data Sources, then the System DSN tab – or – for a 64-bit Windows operating system: Select “Run” and type (without quotation marks) “c:\Windows\SysWOW64\odbcad32.exe”; then select the System DSN tab in the ODBC Data Source Administrator dialog box.
  2. Select the DSN “WhatsUp”, then click on the “Configure” button and the configuration wizard appears.
  3. Make sure that the name assigned is “WhatsUp” (or “NetFlow” if you are checking NetFlow DSN) and that the Server field is correctly assigned, i. e. \>.
  4. In the second dialog box, make sure that the option “With SQL Server authentication with login ID and password entered by the user” is selected. Enter the SQL user name in the Login field.
  5. In the Password field, enter the SQL user’s password (default for WUG would be’sa’ user and the password for’WhatsUp_Gold’), then click Next.
  6. In the third dialog box, make sure that the Modify default database option is selected and that the WhatsUp database (or NetFlow if configured for NetFlow) appears in the drop-down menu, then click Next.
  7. Continue clicking “Next” until you reach the last dialog box, then click Finish.
  8. The Microsoft SQL Server Setup ODBC dialog box opens. You can click on Test Data Source or OK to test the configuration.
  9. Repeat steps b to f for the DSN “NetFlow” and “iDroneService”.

Check if the UISR account has anonymous access.

  1. Log in to the Application Server knowledge base as a user with administrator rights.
  2. Right-click on the My Computer icon and choose Manage from the menu option.
  3. In the Computer Management window, expand Services and Applications > Internet Information Services Manager (IIS) > Websites.
  4. Right-click on ClientPortal and select Properties from the menu option.
  5. In the Directory Security tab, in the Authentication and Access Control section, select Edit.
  6. Make sure that the Enable anonymous access option is enabled for the UISR user name.
  7. Click OK to save all changes.
  8. Click OK to close the ClientPortal Properties.
  9. Repeat steps 4 to 8 for the customer portal.

Once all problems related to these three causes have been resolved, users should no longer see the error message when they connect to the knowledge base of the administrator control panel.

https://community.oracle.com/thread/89045


RECOMMENDED: Click here to troubleshoot Windows errors and optimize system performance