Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
1 ) Implementing a new app connecting oracle database. Failed in Production Qlikview server as a task reload but in desktop in server it is perfectly working on reload.
2 ) User in section access and user running the service and user installed oracle client all same.
3 ) OLEDB and OLEDB64 tested. Force 32 and not force 32 ticked also checked.
4) Did not restart the qlikview server after Oracle installation. ODAC
5) All other details given below
Script line:
OLEDB CONNECT64 TO [Provider=OraOLEDB.Oracle.1;Persist Security Info=True;User ID=****;Data Source=***;Extended Properties=""] (XPassword is *********);
This is really eating everyone'ss mind in my company. Definitely this is not repeated error. Could you please help me fix it?
LOg file :
10/19/2015 11:29:23 AM: Execution started.
10/19/2015 11:29:23 AM: QlikView Version:11.20.12235.0
10/19/2015 11:29:23 AM: CPU Target x64
10/19/2015 11:29:23 AM: Operating System Windows Server 2008 R2 Enterprise Service Pack 1 (64 bit edition)
10/19/2015 11:29:23 AM: Wow64 mode Not using Wow64
10/19/2015 11:29:23 AM: MDAC Version 6.1.7601.17514
10/19/2015 11:29:23 AM: MDAC Full Install Version 6.1.7601.17514
10/19/2015 11:29:23 AM: PreferredCompression 2
10/19/2015 11:29:23 AM: EnableParallelReload 1
10/19/2015 11:29:23 AM: ParallelizeQvdLoads 1
10/19/2015 11:29:23 AM: AutoSaveAfterReload 0
10/19/2015 11:29:23 AM: BackupBeforeReload 0
10/19/2015 11:29:23 AM: EnableFlushLog 0
10/19/2015 11:29:23 AM: SaveInfoWhenSavingFile 0
10/19/2015 11:29:23 AM: UserLogfileCharset 1200
10/19/2015 11:29:23 AM: OdbcLoginTimeout -1
10/19/2015 11:29:23 AM: OdbcConnectionTimeout -1
10/19/2015 11:29:23 AM: ScriptWantsDbWrite false
10/19/2015 11:29:23 AM: ScriptWantsExe false
10/19/2015 11:29:23 AM: LogFile CodePage Used: 1200
10/19/2015 11:29:23 AM: Reload Executed By *******************
10/19/2015 11:29:23 AM: Process Executing: QVB
10/19/2015 11:29:23 AM: Process ID: 10352
10/19/2015 11:29:23 AM: 0004 OLEDB CONNECT*Provider*XPassword*
10/19/2015 11:29:23 AM: Error: ErrorSource: Microsoft OLE DB Service Components, ErrorMsg: The specified module could not be found.
10/19/2015 11:29:23 AM: General Script Error
10/19/2015 11:29:23 AM: Execution Failed
10/19/2015 11:29:23 AM: Execution finished.
Hi,
I was facing the same problem - a reload via the desktop on the server worked fine but a scheduled reload produced thev same error.
I had assumed that our server guy had rebooted the server after the oracle client install but it turned out that they hadn't. One restart later and the error is fixed: if this is still a problem for you and you haven't already done so, I suggest trying a restart of the QV server.
cheers
4) Did not restart the qlikview server after Oracle installation. ODAC
So why didn't you do this? It resolves a lot of mysterious Oracle connection errors...
Peter
I suspect that the (XPassword is *********) option only is valid together with ODBC and not with OLEDB.
HIC
Okie, I will try restarting. Is there a way to test whether the Oracle client is installed correctly is there a way?
It is working in Qlikview desktop hic . Why not in server is the question? Can you also help me to raise a ticket with Qlik?
Check whether this will help you...
Problem with OLEDB connection string to connect to SQL Server database
Hi,
Did you install same drivers/configurations in Server as well as same as Qlikview desktop?
Hope this will help you.
Probably it is installed correctly. You told us that connecting to an Oracle DB using QV Desktop on the server does work, But Oracle software occasionally has these strange habits...
As I said: I don't think that the (XPassword is *********) option is valid for OLEDB.
In OLEDB, the authentication credentials are stored inside the connection string, whereas the XPassword option is a QlikView ODBC password obfuscation feature written after the connection string. For OLEDB I think this string is neglected.
The reason why it works in the Desktop but not in the Server hides inside the connection string. Probably in the ...;User ID=****;... attribute.
HIC
HIC,
Actually password and username was present there in log file, for security purpose I masked it with x...