Sanjeeva Samaraweera

Blog

May 09

Sql Server Browser Service

If server has only one Sql server 2005 instance and it is not is not a named instance then Sql Server Browser Service is in disable mode.

To get a in deep knowledge on this service visit http://msdn.microsoft.com/en-us/library/ms181087.aspx

12:00 PM | Add a comment | Send a message | Permalink | View trackbacks (0)

April 24

View SQL Server 2005 Installation Log Files

The main log you should look at is located in

%ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt

The following table contains sample log file names and log file descriptions for installation of each SQL Server component.

Log file	Description
SQLSetup0001_MachineName_Core.log	The primary SQL Server Setup log file that contains information about the success or failure of all .msi installations.
SQLSetup0001_MachineName_SCC.log	Detailed information from the SQL Server 2005 System Configuration Checker that runs system checks during SQL Server Setup.
SQLSetup0001_MachineName_SQL.log	The Database Engine Setup log file.
SQLSetup0001_MachineName_AS.log	The Analysis Services Setup log file.
SQLSetup0001_MachineName_RS.log	The Reporting Services Setup log file.
SQLSetup0001_MachineName_NS.log	The SQL Server 2005 Notification Services Setup log file.
SQLSetup0001_MachineName_DTS.log	The Integration Services Setup log file.
SQLSetup0001_MachineName_Tools.log	The client components, SQL Server Management Studio, and Books Online Setup log file.
SQLSetup0001_MachineName_WI.log	The Setup user interface (UI) Setup log file.
SQLSetup0001_MachineName_SNAC.log	The SQL Server Native Client Setup log file.
SQLSetup0001_MachineName_.NET Framework 2.0.log	The .NET Framework 2.0 Setup log file.
SQLSetup0001_MachineName_MSXML.log	MSXML Setup log file.
SQLSetup0001_MachineName_SQLXML.log	SQLXML Setup log file.
SQLSetup0001_MachineName_Logs.cab	For failover cluster installations, this file will contain logs from all cluster nodes.
SQLSetup0001_MachineName_Datastore.xml	A dump of all properties that are cached during Setup. This information may be requested by Product Support Services to troubleshoot and debug failures.

4:32 PM | Add a comment | Send a message | Permalink | View trackbacks (0)

April 01

Read default Trace

SELECT *

FROM fn_trace_getinfo(default);

This will give the default trace file. You can visit the directory and find old *.trc files as well.

If you cannot open these files directly as trace files folllowing command in query analyser will do that.

SELECT *

FROM fn_trace_gettable('D:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\log_38.trc',default)

ORDER BY starttime

2:47 PM | Add a comment | Send a message | Permalink | View trackbacks (0)

March 31

Unable to process cube from within SSIS package - Coordinating with Microsoft

Following is the complete mail I publish regarding coordination with Microsoft on this bug

-----------------------------------------------------------------------------------------------------

Great Sanjeeva. I’ll go ahead and archive off this case, below is a summary of the case for your reference:

As agreed your existing support case will now be archived. If I can be of any further assistance on this case or if you have any suggestions for improving our service please do not hesitate to contact myself or my manager on <mailto: s@microsoft.com> so we can ensure you receive our immediate attention.

[ARCR]

ACTION:

Unable to process cube from within SSIS package nor browse it from SSMS.

RESULT:

Error when processing cube from SSIS package:

0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap).

Error when browsing cube from SSMS:

class not registered ( Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG

CAUSE:

OWC corrupt which prevented the cube from being brows able in SSMS

Second issue is caused by a bug, http://support.microsoft.com/kb/919224

RESOLUTION:

Re-install OWC and apply workaround mentioned in KB 919224.

As the second issue is caused by a bug, I shall close the case as non-decrement.

Kind Regards,

----------------------------------------------------------------------------------

Hi I

Dll has been registered and now the cube can be processed through a SSIS job.

Thanks for your assistance.

regards

Sanjeeva

Hi Sanjeeva,

That’s great!

Wrt to the DTS runtime error, could you take a look this KB, http://support.microsoft.com/kb/919224

More specifically, see if re-registering the DTS.DLL resolves it or not.

“Method 1

If the versions of the instances of SQL Server 2005 are not earlier than SQL Server 2005 SP2, run the following command at a command prompt to register the 32-bit Dts.dll file:

%windir%\syswow64\regsvr32 "%ProgramFiles(x86)%\Microsoft SQL Server\90\dts\binn\dts.dll”

Kind Regards,

------------------------------------------------------------------------------------------------------------------------------

Hi I

I installed the Office Web Components from your link and now the first part of the problem is solved. We can browse the cube now.

Thanks for this, now we can move forward to solve the second part, still the same error is thrown when trying to create the new connection Manager for the Analysis Services Processing Task.

Regards

Sanjeeva

Hi S,

1. zip up the installation log files and email them . They can be found at: Program Files/Microsoft SQL Server/90/Setupbootstrap/log/

2. Setup the Adventure Sample database (can be downloaded from the Microsoft web-site) on the machine and test whether a cube can be built for it using SSIS

For the first part of the problem (point two below), could you try repair the Office Web Components, alternatively re-install them from http://www.microsoft.com/downloads/details.aspx?FamilyID=7287252c-402e-4f72-97a5-e0fd290d4b76&DisplayLang=en and see if you able to browse cube from BIDS/SSMS.

Regards,

Good Morning Mr. I

My name is Sanjeeva Samaraweera and I am the Database Designer sending you further details on Case Ref#

1. We use Sql Server 2005 Standard Edition (9.00.3175.00 SP2) in a 64 bit machine (Windows 2003 Standard edition for x64 SP2).

Is it ok if we publish the Installation log files in one of our ftp sites?. Also if possible please send us your IP address to enable that for you.

2. A cube is created for AdventureWorks database in BIDS and built and processed using BIDS/SSMS successfully.

Anyway the cube cannot be browsed in BIDS/SSMS throwing an error. – class not registered ( Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).

Cube can be accessed and used from Reporting Services.

3. Tried to create an SSIS package to do the processing. Following error thrown when trying to create the new connection Manager for the Analysis Services Processing Task.

The new connection manager could not be created.

Exception from HRESULT: 0xC0010014 (Microsoft.SqlServer.DTSRuntimeWrap).

I tried to run database/analysis services traces and capture this error but it was not possible as traces are not logging SSIS activities.

Thanks

Sanjeeva

5:49 PM | Add a comment | Send a message | Permalink | View trackbacks (0)

Set Trace Flags in 2005

Go from SQL Server Configuration Manager, right click your SQL Server Service and choose Properties. Then go to the Advanced Tab and add -Txxx to the list of startup parameters. Make sure you separate it from other startup parameters with semicolon (;) and don't leave a space.

4:52 PM | Add a comment | Send a message | Permalink | View trackbacks (0)

View more entries