﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Data Warehousing / Analysis Services  / Errors when writing querylog in sql server database / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Sun, 19 May 2013 07:45:44 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: Errors when writing querylog in sql server database</title><link>http://www.sqlservercentral.com/Forums/Topic106530-17-1.aspx</link><description>&lt;P&gt;Yaaa, that worked! &lt;/P&gt;&lt;P&gt;Thanks, Steve&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;Ramunas Balukonis&lt;/P&gt;</description><pubDate>Thu, 01 Apr 2004 23:16:00 GMT</pubDate><dc:creator>Ramunas Balukonis</dc:creator></item><item><title>RE: Errors when writing querylog in sql server database</title><link>http://www.sqlservercentral.com/Forums/Topic106530-17-1.aspx</link><description>&lt;P&gt;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. &lt;A href="http://www.boyce.us/windows/servertipcontent.asp?ID=7"&gt;http://www.boyce.us/windows/servertipcontent.asp?ID=7&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Seems to work...&lt;img src='images/emotions/unsure.gif' height='20' width='20' border='0' title='Unsure' align='absmiddle'&gt;&lt;/P&gt;</description><pubDate>Mon, 22 Mar 2004 23:11:00 GMT</pubDate><dc:creator>stevefromOZ</dc:creator></item><item><title>RE: Errors when writing querylog in sql server database</title><link>http://www.sqlservercentral.com/Forums/Topic106530-17-1.aspx</link><description>&lt;P&gt;This is valid connection string, and query logging works correctly before I stop sql sever service. &lt;/P&gt;</description><pubDate>Mon, 22 Mar 2004 23:04:00 GMT</pubDate><dc:creator>Ramunas Balukonis</dc:creator></item><item><title>RE: Errors when writing querylog in sql server database</title><link>http://www.sqlservercentral.com/Forums/Topic106530-17-1.aspx</link><description>&lt;P&gt;what did u change the connection string to?  are they valid (ie have u checked them from another applciation)?&lt;/P&gt;&lt;P&gt; &lt;/P&gt;</description><pubDate>Mon, 22 Mar 2004 17:36:00 GMT</pubDate><dc:creator>stevefromOZ</dc:creator></item><item><title>Errors when writing querylog in sql server database</title><link>http://www.sqlservercentral.com/Forums/Topic106530-17-1.aspx</link><description>No one has responded to this topic yet. Even if you don't have a complete answer, the original poster will appreciate any thoughts you have!</description><pubDate>Mon, 22 Mar 2004 08:00:00 GMT</pubDate><dc:creator>Site Owners</dc:creator></item><item><title>Errors when writing querylog in sql server database</title><link>http://www.sqlservercentral.com/Forums/Topic106530-17-1.aspx</link><description>&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;Hello, &lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;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. &lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;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: &lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;1. Relational data provider reported error: [No transaction is active.].&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;2. Relational data provider reported error: [Connection failure;08S01].&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;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.].&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;&lt;/FONT&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;When I stop and restart MSOLAP Service, it continue to write to table querylog. Pausing and then starting MSOLAps ervice does not work.&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;&lt;/FONT&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;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?&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;&lt;/FONT&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;Or can somebody propose another way to continue logging after sql server restarted?&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;&lt;/FONT&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;Thank you.&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;&lt;/FONT&gt; &lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;Ramunas&lt;/FONT&gt;&lt;/DIV&gt;&lt;DIV&gt;&lt;FONT face=Arial size=2&gt;&lt;/FONT&gt; &lt;/DIV&gt;</description><pubDate>Wed, 17 Mar 2004 01:34:00 GMT</pubDate><dc:creator>Ramunas Balukonis</dc:creator></item></channel></rss>