PSSDiag Utility Questions

Would anyone can told me following about PSSDiag ?

1. The Performance Monitor output is default set to output as .BLG file, would it be other format like CSV or TXT ?

2. For SQL Trace log gathering location, even those we set to drive other than C:\ , it still need some spaces for temporary storage in C:\ under setting of TEMP and TMP path, so is PSSDIAG still need temporary spaces in dirve C:\

3. Does this utility also support monitor on SQL 2005 server ? Pls

Many Thanks First.

1. You cannot change the default output for PERFMON.

2. Yes it access the TEMP directory to perform few computations.

3. http://www.microsoft.com/downloads/details.aspx?familyid=5564386A-28C2-4483-8293-76FFF67B9EB3&displaylang=en refers :

System Requirements

Supported Operating Systems: Windows 2000; Windows NT; Windows Server 2003; Windows XP|||

how about if my server cannot install MSXML 4.0 SP2 ? Can I use alternative method that use ini instead of xml configuration file ?

Also, can I find some example of the ini file format somewhere as I can't find any in the web especially those with some calling custom utility function as I want to start the Performance Monitor myself which can stored as csv format?

Many Thanks.

|||

Have you tested the installation of MSXML SP in thsi case?|||

Satya SKJ wrote:

Have you tested the installation of MSXML SP in thsi case?

yes. if using MSXML4.0SP2, I can start the PSSDIAG but my production server not allow me to apply them. If so, need to go through a complex QC cycle. So, only test on testing server but cannot apply them into Production Server.

|||

Then I believe we are out of option, either you can open a case with Microsoft Support to have desired facility or follow whatever is available.

PSSDiag Utility Questions

Would anyone can told me following about PSSDiag ?

1. The Performance Monitor output is default set to output as .BLG file, would it be other format like CSV or TXT ?

2. For SQL Trace log gathering location, even those we set to drive other than C:\ , it still need some spaces for temporary storage in C:\ under setting of TEMP and TMP path, so is PSSDIAG still need temporary spaces in dirve C:\

3. Does this utility also support monitor on SQL 2005 server ? Pls

Many Thanks First.

1. You cannot change the default output for PERFMON.

2. Yes it access the TEMP directory to perform few computations.

3. http://www.microsoft.com/downloads/details.aspx?familyid=5564386A-28C2-4483-8293-76FFF67B9EB3&displaylang=en refers :

System Requirements

Supported Operating Systems: Windows 2000; Windows NT; Windows Server 2003; Windows XP|||

how about if my server cannot install MSXML 4.0 SP2 ? Can I use alternative method that use ini instead of xml configuration file ?

Also, can I find some example of the ini file format somewhere as I can't find any in the web especially those with some calling custom utility function as I want to start the Performance Monitor myself which can stored as csv format?

Many Thanks.

|||

Have you tested the installation of MSXML SP in thsi case?|||

Satya SKJ wrote:

Have you tested the installation of MSXML SP in thsi case?

yes. if using MSXML4.0SP2, I can start the PSSDIAG but my production server not allow me to apply them. If so, need to go through a complex QC cycle. So, only test on testing server but cannot apply them into Production Server.

|||

Then I believe we are out of option, either you can open a case with Microsoft Support to have desired facility or follow whatever is available.

PSSDiag Failed to instantiate an XML DOM

Can anyone explain to me what I need to do to correct this?

I have ran the SAME PSSDiag install from the this particular server MANY times before.

All of a sudden, it now fails to start and I find this error, that is posted in teh subject line of the thread, in teh Windows Application Event Log.

If I need to install another app in order to correct this, please let me know if the installed app will need a reboot of the server to take affect. I have to schedule down time for that.

Thanks ALL!

Check with this
http://www.microsoft.com/downloads/details.aspx?familyid=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en

PSSDiag Failed to instantiate an XML DOM

Can anyone explain to me what I need to do to correct this?

I have ran the SAME PSSDiag install from the this particular server MANY times before.

All of a sudden, it now fails to start and I find this error, that is posted in teh subject line of the thread, in teh Windows Application Event Log.

If I need to install another app in order to correct this, please let me know if the installed app will need a reboot of the server to take affect. I have to schedule down time for that.

Thanks ALL!

Check with this
http://www.microsoft.com/downloads/details.aspx?familyid=3144b72b-b4f2-46da-b4b6-c5d7485f2b42&displaylang=en

PSSDIAG

Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.
I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:

> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.

PSSDIAG

I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?
1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:

> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message that
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?

PSSDIAG

I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:

> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4
.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message th
at
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?

PSSDIAG

Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:

> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.

PSSDIAG

I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
The collectif of the trace seems to go well.
When I stop the trace the programm seems to hang after the last message that
says that it's exiting.
I dont't have the problem on a Windows XP SP1.
Is there an issue for windows 2003 sp1 ?
Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
diagnostic ?1- Do not install PSSDiag in c:\program files or any other directory that
have blank in its name
2- There are two requirements for the PSSDIAG service startup account: 1) it
must be a member of the local administrators group (though not necessarily
the local Administrator), and 2) it must be a member of the SQL Server
sysadmin server role. The default PSSDIAG service startup account is
LocalSystem, and by default it satisfies both of these requirements.
However, if you have removed the local Administrators group from the SQL
sysadmin role, you will need to choose a new PSSDIAG service startup account
that is both an NT administrator and a SQL sysadmin.
3- The .trc file is actually written by the SQL Server process. For this
reason, the SQL Server service startup account must be able to write to the
output directory.
"Sylvain Nadeau" wrote:
> I try to run PSSDIAG on a Windows 2003 sp1 box running SQL Server 2000 SP4.
> The collectif of the trace seems to go well.
> When I stop the trace the programm seems to hang after the last message that
> says that it's exiting.
> I dont't have the problem on a Windows XP SP1.
> Is there an issue for windows 2003 sp1 ?
> Also SQLDiag doesn't run with SQL 2000 SP4, is there another tool for a
> diagnostic ?

PSSDIAG

Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
Server 2000 SP4 ? It seems to hang.
The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.I wouldn't use that tool during business hours. I did and it crashed my
server, desipte MS assuring that it would be fine.
"Sylvain Nadeau" wrote:
> Is there a problem with PSSDiag on a Windows 2003 SP1 server running SQL
> Server 2000 SP4 ? It seems to hang.
> The tool works perfectly on a Windows XP SP1 with SQL Server 2000 SP4.