Skip to page contentSkip to chat
ServiceNow support
    • Community
      Ask questions, give advice, and connect with fellow ServiceNow professionals.
      Developer
      Build, test, and deploy applications
      Documentation
      Find detailed information about ServiceNow products, apps, features, and releases.
      Impact
      Accelerate ROI and amplify your expertise.
      Learning
      Build skills with instructor-led and online training.
      Partner
      Grow your business with promotions, news, and marketing tools
      ServiceNow
      Learn about ServiceNow products & solutions.
      Store
      Download certified apps and integrations that complement ServiceNow.
      Support
      Manage your instances, access self-help, and get technical support.
Resolving Microsoft SQL Linked Server Access Errors with ODBC Driver - Support and Troubleshooting
  • >
  • Knowledge Base
  • >
  • Support and Troubleshooting (Knowledge Base)
  • >
  • Resolving Microsoft SQL Linked Server Access Errors with ODBC Driver
KB0546265

Resolving Microsoft SQL Linked Server Access Errors with ODBC Driver


21417 Views Last updated : Aug 24, 2022 public Copy Permalink English (Original)
  • English (Original)
  • Japanese
KB Summary by Now Assist

Issue

When using the ODBC Driver with Microsoft SQL Linked Server, the ODBC Driver is unable to access the application logs or file cache.

Symptoms

When using the ODBC Driver with a Microsoft SQL Linked Server, one of these errors appears:

  • Cannot obtain the required interface ("IID_IDBSchemaRowset") from OLE DB provider "MSDASQL" for linked server "SERVICENOW". (Microsoft SQL Server, Error: 7301)

  • Cannot obtain the required interface (“IID_IDBCreateCommand") from OLE DB provider "MSDASQL" for linked server "SERVICENOW". (Microsoft SQL Server, Error: 7301)

  • Cannot create an instance of OLE DB provider "MSDASQL" for linked server "SERVICENOW". (Microsoft SQL Server, Error: 7302)

  • Cannot initialize the data source object of OLE DB provider "MSDASQL" for linked server "SERVICENOW".

  • OLE DB provider "MSDASQL" for linked server "SERVICENOW" returned message "[DataDirect][ODBC OpenAccess SDK driver][OpenAccess SDK Client]Failed to create the Core Service component.". (Microsoft SQL Server, Error: 7303)

  • The OLE DB provider "IBMDADB2.DB2COPY1" for linked server "<linked server name>" reported an error. Access denied. (Microsoft SQL Server, Error: 7399)

Cause

The ODBC Driver uses the %LOCALAPPDATA% environment variable to specify the location of log files and cache. When using the iSQL console, this variable is replaced with the user home directory, for example, C:\Users\<user>\AppData\Local. However, when running Microsoft SQL Server, this variable is replaced with C:\Windows\System32\config\systemprofile\AppData\Local. Unlike the user local directory, the System32 local directory requires elevated privileges to access.

Resolution

Modify the ServiceDebugLogPath and ServicesSQLDiskCachePath ODBC Driver configuration properties and replace %LOCALAPPDATA% with ${user.home}.


The world works with ServiceNow.

Sign in for more! There's more content available only to authenticated users Sign in for more!
Did this KB article help you?
Did this KB article help you?

How would you rate your Now Support digital experience?

*

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

Very unsatisfied

Unsatisfied

Neutral

Satisfied

Very satisfied

What can we improve? Please select all that apply.

What are we doing well? Please select all that apply.

Tell us more

*

Do you expect a response from this feedback?

  • Terms and conditions
  • Privacy statement
  • GDPR
  • Cookie policy
  • © 2025 ServiceNow. All rights reserved.