Knowledgebase: FDM
Posted by Priya Doyle on 08 February 2011 03:48 PM


 Modified 06-APR-2010     Type PROBLEM 

Applies to:

Hyperion Financial Data Quality Management - Version: to - Release: 9.3 to 11.1
Information in this document applies to any platform.


When attempting to import a simple pipe delimited file into a brand new SQL Server 2005 FDM application the import process fails.  The error message that is returned is written to the user error log and reads:

Could not bulk insert: Unable to read \\servername\share\appname\inbox\xxxx.tmp Error Code 5 Access is Denied


SQL Server Service Account does not have ability to read from FDM application inbox

   In order for the bulk insert process to complete within FDM, the windows account that is running the MSSQL database service must be granted read NTFS and Share permissions to the FDM application folder.  Currently the windows account that is set to run the MSSQL Service has not been granted access to the application folder share and is unable to read the necessary .tmp and .fmt files that are created to perform the bulk insert.


a) Logon to the Microsoft SQL Server 2005 machine and open the SQL Server Configuration Manager
b) Locate the MSSQL Service and view the user that is set to run the service.  This must be set to a domain account that is able to browse across the network to the FDM application folder directory.  If it is set to LOCALSYSTEM this needs to be changed to a domain user.
c) Grant the domain user running the MSSQL Service read permissions on the sharing and security tab of the FDM application folder.
d) Re-run the import process in FDM.  If the import is successful the issue is resolved.  If the bulk insert error continues to be returned, the network administrator can attempt the following process in Active Directory Users and Computers:

   On the Domain Controller machine :
1. Launch Active Directory Users and Computers within Administrative Tools
2. Find the Computer Account for the Microsoft SQL Server 2005 Machine.
3. Right click on the SQL Server 2005 Machine Account and choose Properties clicking on the Delegation tab
4. Click on the check box "Trust this computer for Delegation to any service (Kerberos only)"
5. Apply the change.

**Note: If the above process does not resolve the issue, Microsoft Support would need to be contacted to address the issue, as this is a SQL Server 2005 issue and outside of the scope of the FDM product.

(0 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name: