Can any one please help me understand what this publisher error log mean. We get this error when trying to run multiple (3-6 depending on the source file size) reduction jobs together. We are running QV 9 SR3 on windows 2003 server with 64 gig ram and 16 cpu.
(2010-04-08 12:37:18) Error: The sourcedocument failed to open.. Exception=System.Runtime.InteropServices.COMException (0x800706BE): The remote procedure call failed. (Exception from HRESULT: 0x800706BE)
(2010-04-08 12:37:18) Error: at QVBWrapper.Document.Load(ILogBucket i_LogBucket)
(2010-04-08 12:37:18) Error: The document failed to open.
(2010-04-08 12:37:18) Error: Could not request the QlikView Engine process to quit.. Exception=System.Runtime.InteropServices.COMException (0x800706BA): The RPC server is unavailable. (Exception from HRESULT: 0x800706BA)
(2010-04-08 12:37:18) Error: at QlikView.ApplicationClass.Quit(Int32 _ExitCode)
(2010-04-08 12:37:18) Error: at QVBWrapper.Document.NiceCloseThread(ILogBucket i_LogBucket)
(2010-04-08 12:37:18) Information: Closed the QlikView Engine successfully. ProcessID=12212
I would recommend contacting Support (firstname.lastname@example.org). I'm not positive, but I think this might have to do with the number of Engines that QDS can allocate at once. In theory, this should be equal to the number of cores on the machine, but I think I heard somewhere that there might be an internal QV limit that is less than this.
I do not have an explanation as to why this is happening but I do have a solution. At least one that removed the error count =5 from the log file.
I created a new ODBC data source connector within QV and made it apply to the 'this machine only'. UAC needed to be turned off in order for me to apply the to the machine. I then used the SQL driver rather than the SQL Native Client 10.0 client.
We connect to two SQL DB one is at SQL 2000 then other at 2005. I looked up an error code I was getting in my log on M$ site and found the below support message. The below states this issue was addressed with SQL 2000 SP3. The error code I was getting was a call made to our 05 DB, one would this would be fixed in SQL 2005... maybe not.
I am currently receiving 'errorcounte=3' now, I am still checking my settings but this may be my new issue...
As I mentioned before I am unsure why using the ODBC connector makes a difference. I will post again if I actually get the publisher task to reload automatically.