Errors when writing querylog in sql server database

• Ramunas Balukonis

  SSC-Addicted

  Points: 448

  More actions

  March 17, 2004 at 1:34 am

  #110654

  Hello,

  I migrated my Analysis Services querylog table from access database to sql server database. I just changed registry value QueryLogConnectionString and RemoteQueryLogConnectionString values in registry under HKEY_LOCAL_NASHINE/ SOFTWARE/MICROSOFT/OLAP SERVER/CURRENTVERSION.

  After that all works fine until I stoped ant restarted my SQL SERVER service. MSOLAP Service continued to work but failed to write to database querylog. In event log I found such error:

  1. Relational data provider reported error: [No transaction is active.].

  2. Relational data provider reported error: [Connection failure;08S01].

  3. Relational data provider reported error: [Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.].

   

  When I stop and restart MSOLAP Service, it continue to write to table querylog. Pausing and then starting MSOLAps ervice does not work.

   

  I think, one of the best method should be implement service dependency between olap service and sql server service, like between sqlserveragent and sql server. So, I want to stop olap service mandatory after sql server service stops. is it possible?

   

  Or can somebody propose another way to continue logging after sql server restarted?

   

  Thank you.

   

  Ramunas

   

• March 22, 2004 at 8:00 am

  This was removed by the editor as SPAM

• stevefromOZ

  SSC-Forever

  Points: 43646

  More actions

  March 22, 2004 at 5:36 pm

  #499912

  what did u change the connection string to?  are they valid (ie have u checked them from another applciation)?

   

  Steve.

• Ramunas Balukonis

  SSC-Addicted

  Points: 448

  More actions

  March 22, 2004 at 11:04 pm

  #499941

  This is valid connection string, and query logging works correctly before I stop sql sever service.

• stevefromOZ

  SSC-Forever

  Points: 43646

  More actions

  March 22, 2004 at 11:11 pm

  #499942

  obviously it can't log to sql server if it's not running, so alternatives are to log to another server or like you say, put a dependency on the msolap service to tie it to the mssql service.  Here's a link to a reg hack that shows how to add the dependency. http://www.boyce.us/windows/servertipcontent.asp?ID=7

  Seems to work...

  Steve.

• Ramunas Balukonis

  SSC-Addicted

  Points: 448

  More actions

  April 1, 2004 at 11:16 pm

  #501549

  Yaaa, that worked! 

  Thanks, Steve

   

  Ramunas Balukonis