- A Crystal Report uses an ODBC connection to retrieve data
- The ODBC data source is configured to connect to a database located on a shared network drive
- The report runs successfully in the Crystal Reports Designer
- The report fails with one of the following errors when running in an ASP.NET web application:
- "Unable to connect - Invalid log on parameters"
- "Load report failed"
- These errors appear because the web application has insufficient permissions to access network resources.
- By default, the web application and the report run under the ASPNET account. The ASPNET account is a local account that does not have access to the network resources.
- Network drives that have been mapped on the local machine are not available to processes running under the ASPNET account.
To work around this issue, use the following steps:
1. Change the ODBC data source to use a System DSN and update the Server name to the Server name where SQL Expression exsits.
2. Change the account that the ASPNET process uses to run applications by following these steps:
i. Open Windows Explorer and navigate to
<%WINNT or Windows%>\Microsoft.Net\Framwork\v1.0.3705\CONFIG
b. Open the Machine.Config file and search for the line containing this text:
<processModel enable="true" timeout="Infinite"
c. Search this line for the property 'userName' (by default this property is set to "machine").
d. Change the user name to a user account that has permission to access network resources.
For example: 'userName="DOMAIN\username" password="users password" '
e. Save the Machine.config file.
f. On the 'Start' menu, click 'Run', and then type "IISReset" to reset IIS.
When you run your application, the report runs successfully.
DOTNET VS.NET NETWORK SHARE INCORRECT LOGON PARAMETER FAILED MAPPED DRIVE Crystal Reports for Visual Studio Network Share Access Permissions Cannot View Report , c2012606 , KBA , BI-DEV-NET , BI Software Development Kits (SDKs) - .NET or Other , Problem