Reportnet Logon Failure on Validation - db = MSAccess via mapped drive

[emis]

Hi,

When validating a report we are getting the following error message:
------------------------------------------------------------------
QE-DEF-0285 Logon failure.

QE-DEF-0285 Logon failure.

QE-DEF-0325 The cause of the logon failure is:

QE-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in:
SCRBackhauling


UDA-SQL-0031 Unable to access the "SCRBackhauling" database.

UDA-SQL-0019 An internal system failure has occurred during the operation "attach".

[Microsoft][ODBC Microsoft Access Driver] '(unknown)' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

Trace back:

WPBIBusMethod.cpp(190): WPDataRetrievalException: CCL_CAUGHT: WPBIBusMethod::run

WPEngine.cpp(468): WPDataRetrievalException:

WPEngine.cpp(942): WPDataRetrievalException:

WPController.cpp(263): WPDataRetrievalException: CCL_RETHROW: WPController::executeRendering()

LWDataRetrievalEngine.cpp(305): WPDataRetrievalException: CCL_RETHROW: LWDataRetrievalEngine:repare

LWDataRetrievalEngine.cpp(1773): WPDataRetrievalException: CCL_THROW: LWDataRetrievalEngine::runQSQuery

Source/QE_QsApi.cpp(3822): QSException: CCL_RETHROW: QE

Source/QE_QsApi.cpp(3801): QSException: CCL_RETHROW: QE

Source/QESqlServer.cpp(3064): QSException: CCL_THROW: QE

------------------------------------------------------------------

Within Framework Manager we test the datasource and this returns as being successful. However on validation of the Report it produces this error.
The ODBC datasource is connected to an Access database which resides on a mapped network drive with FULL Administrative privileges for the user.

If we was to move the database to the servers hard drive (where Framework Manager and the Content store sits) then it's successful. However when it's on a mapped network drive we get the above error. We need to keep the database on this mapped drive for operation input purposes.
We only seem to be getting this error when we need to access databases on this mapped drive. We have used various other mapped drives and it's worked OK.
Can anyone please advise as to what we have possibly missed out here.

Many Thanks

 

[scrown]

We've run into a similar problem.

Were you able to resolve this?

What does your connection string look like?

Do you have you an saved ODBC connection saved on your Framework Manager server?

 

[dhulbert]

Do you reference the database via the mapped drive letter if so try using the full network path to the database instead.