SQLSrvAnalysisSrvcs Work Item Rss Feed

Created Issue: ssas.SSASCleanBatch looks to have bug. [10929]

opoudel — Thu, 12 Nov 2009 16:45:12 GMT

ssas.SSASCleanBatch procedure has where criteria as P_BatchID <= @BatchID in order to get rid of all the old batches. Should not that be P_BatchID < @BatchID?

Closed Issue: Unable to use ASTrace in 64 Bit machine

furmangg — Fri, 21 Aug 2009 16:13:28 GMT

I tried to build ASTrace targetting x86 cpu and deployed into 64bit server. I cant get to start the service. It always fails with following message.
8/19/2009 10:28:54 PM: Error: Microsoft.SqlServer.Management.Trace.SqlTraceException: Failed to initialize object as reader. ---> System.Runtime.InteropServices.COMException (0x8004021A)
at ?A0x8159d01c.ProcessError(Int32 hr, UInt16* lpszMessage)
at Microsoft.SqlServer.Management.Trace.CTraceControllerBase.InitSource(Boolean bReOpen)
at Microsoft.SqlServer.Management.Trace.CTraceObjectsRowsetController.InitSource(Boolean bReOpen)
at Microsoft.SqlServer.Management.Trace.TraceServer.InitializeAsReader(ConnectionInfoBase serverConnInfo, String profileFileName)
--- End of inner exception stack trace ---
at Microsoft.SqlServer.Management.Trace.TraceServer.InitializeAsReader(ConnectionInfoBase serverConnInfo, String profileFileName)
at ASTrace.Trace.OnStart(String[] args)

I have already applied the sugesstions given in the other thread related to this issue.

Please let me know what else needs to be done.
Comments:

resolved

Commented Issue: Unable to use ASTrace in 64 Bit machine

sambathraj — Fri, 21 Aug 2009 04:31:04 GMT

Thanks For your reply. I now reinstalled the service and added the registry key. It now worked.

Commented Issue: Unable to use ASTrace in 64 Bit machine

furmangg — Thu, 20 Aug 2009 19:58:04 GMT

you followed the instructions at http://timlaqua.com/2008/11/installing-astraceexe-in-a-64-bit-environment/ and it still didn't work? Works great for me.

Created Issue: Unable to use ASTrace in 64 Bit machine

sambathraj — Thu, 20 Aug 2009 05:36:47 GMT

Created Issue: ActivityViewer - LoadServerNode uses RegisteredServerName instead of ServerName

ScaleOvenStove — Fri, 02 Jan 2009 22:28:26 GMT

In SSMS, if you register a server and name it, then it doesn't work with activity viewer. You can type in a "Registered Server Name" different from your server name, so example:

Server Name = ABC123
Registered Server name = MyServer

ActivityViewer will try to use the Registered Server Name from the RegSrvr.xml in App Data folder. It needs to use the <ServerName> under <ConnectionInformation> instead. A kludegy workaround is this code change in the LoadServerNode

else if (node.Name.Equals("SERVER", StringComparison.InvariantCultureIgnoreCase))
{
string server = node.InnerXml;
server = server.Substring(server.IndexOf("<ServerName>"), server.IndexOf("</ServerName>") - server.IndexOf("<ServerName>"));
server = server.Replace("<ServerName>", "");
tn = new TreeNode(
server,
(int)ImageListItems.ServerConnected,
(int)ImageListItems.ServerConnected);
tn.Tag = AppNodeType.Server;
}

Commented Issue: ASTrace IA64, X64

tlaqua — Mon, 17 Nov 2008 11:39:25 GMT

Problem reported with AS trace on IA64 and x64 platforms
Environment:
======================
1.　Windows2003 ENT ENU
2.　DEV ENU 09.00.3033.00

Repro Steps:
======================
1. Build ASTrace.sln.
2. Create a folder named ASTrace under folder "C:\Program Files\Microsoft SQL Server\MSSQL.1"
3. Copy the files "ASTrace.exe.config" and "Standard.tdf" from the default sample installed folder "C:\Program Files\Microsoft SQL Server\90\Samples\Analysis Services\Administrator\ASTrace" to the folder ASTrace created in step1. The copy ASTrace.exe (The size of this file is 24KB.) from the debug folder to the folder ASTrace created in step1.
4.Open a Visual Studio 2005 Command Prompt, CD to "C:\Program Files\Microsoft SQL Server\MSSQL.1\ASTrace".
5.Execute the following command:
InstallUtil.exe ASTrace
6.Keey the properties of ASTrace.exe.config file as default.
7.Open Windows Service Control Manager and navigate to ASTrace, then start it.

Expectations:
======================
1.The ASTrace service should be started without error and after that the status ASTrace service displayed in Windows Service Control Manager shoulde be "Started".
2.Table "ASTraceTable" should be created in database "AdventureWorksDW".

Actual Results:
======================
1.Failed to start ASTrace service. Warning message provided by Windows Service Control Manager
Comments: ** Comment from web user: tlaqua **

Workaround: http://timlaqua.com/2008/11/installing-astraceexe-in-a-64-bit-environment/

Commented Issue: ASTrace IA64, X64

stoicform — Tue, 12 Aug 2008 03:40:36 GMT

Service started! Now to test if it is working. That last step was to shore up the domain authentication by setting the service account to a domain account with rights on the target SSAS and MSSQL servers.

Commented Issue: ASTrace IA64, X64

stoicform — Tue, 12 Aug 2008 03:39:25 GMT

Just noting that I had to manually create a reg key (after reading the code to see what it wanted).
regedit export:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ASTrace]
"path"="C:\\Users\\timshea\\work\\ASTrace\\ASTrace\\CS\\ASTrace\\bin\\Debug"

Commented Issue: ASTrace IA64, X64

stoicform — Tue, 12 Aug 2008 03:19:55 GMT

Forcing the build target to x86 moved past this error (was set to CPU agnostic in the downloaded sample code). pfclt.dll can be found under Program Files (x86) if tools are installed with SQL. Now onto the next issue..

Commented Issue: ASTrace IA64, X64

stoicform — Tue, 12 Aug 2008 03:07:05 GMT

Found this in MSDN: The log provider for SQL Server Profiler was unable to load pfclnt.dll because it is only supported on 32-bit systems.

Commented Issue: ASTrace IA64, X64

stoicform — Tue, 12 Aug 2008 02:55:49 GMT

I have a perfect repro. pfclnt.dll does not exist.
Note that I only got this far by manually creating the "path" registry key, which is failing to be created at service install.

8/11/2008 7:46:55 PM: Service Started in 'C:\Users\timshea\work\ASTrace\ASTrace\CS\ASTrace\bin\Debug'
8/11/2008 7:46:55 PM: Cannot start Analysis Server trace:
8/11/2008 7:46:55 PM: Analysis Server name: 'bi-server-24-lh\ssas2k8'
8/11/2008 7:46:55 PM: Trace defintion : 'C:\Users\timshea\work\ASTrace\ASTrace\CS\ASTrace\bin\Debug\Standard.tdf'
8/11/2008 7:46:55 PM: Error: Microsoft.SqlServer.Management.Trace.SqlTraceException: Failed to initialize object as reader. ---> System.IO.FileNotFoundException: Could not load file or assembly 'file:///C:\Program Files\Microsoft SQL Server\100\Tools\Binn\pfclnt.dll' or one of its dependencies. The system cannot find the file specified.
File name: 'file:///C:\Program Files\Microsoft SQL Server\100\Tools\Binn\pfclnt.dll'
at System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection)
at System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection)
at System.Reflection.Assembly.LoadFrom(String assemblyFile)
at Microsoft.SqlServer.Management.Trace.TraceUtils.CreateInstance(String assemblyRelativePath, String objectClass)
at Microsoft.SqlServer.Management.Trace.TraceServer.InitializeAsReader(ConnectionInfoBase serverConnInfo, String profileFileName)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

--- End of inner exception stack trace ---
at Microsoft.SqlServer.Management.Trace.TraceServer.InitializeAsReader(ConnectionInfoBase serverConnInfo, String profileFileName)
at ASTrace.Trace.OnStart(String[] args) in C:\Users\timshea\work\ASTrace\ASTrace\CS\ASTrace\Service1.cs:line 73

CREATED ISSUE: ASTrace IA64, X64

edwardm — Fri, 04 Apr 2008 17:49:14 GMT

CREATED ISSUE: Where filter, comma separator where colon expected

Sendami — Tue, 08 May 2007 14:35:40 GMT

Hello, I think I have found one issue, if you try to generate WHERE sentences with the same dimension hierarchy , it would build the query in an erroneus way: The issue is in the generated MDX query. An example of generated query is the following: SELECT {[Product].[Category].Children} ON COLUMNS, {[Geography].[Country].Children} ON ROWS FROM [Adventure Works] WHERE (([Date]. [Calendar Year].&[2004]),([Date].[Calendar Year].&[2002]) ) If you run this on the SQL Server Management Studio, you will get the following error: The 'Calendar Year' hierarchy appears more than once in the tuple. This query has one error: In the WHERE part, between the members, the delimiter character should be “:” instead of “,”. So the correct MDX query would be: SELECT {[Product].[Category].Children} ON COLUMNS, {[Geography].[Country].Children} ON ROWS FROM [Adventure Works] WHERE ( ([Date].[Calendar Year].&[2004]):([Date].[Calendar Year].&[2002]) ) I have found where the token is selected: The class Tokens.cs in the line 223 has been replaced the following code: value += values[id] + ","; } // Trim "," that occurs in the end. value = value.TrimEnd(','); Just change the token, would fix this problem, but not if we selected different dimensions to filter: value += values[id] + ":"; } // Trim “:” that occurs in the end value = value.TrimEnd(':'); Could you confirm me if this is a bug? Could you shed some light about how to solve it ?