spsreport Work Item Rss Feed

Commented Issue: Unhandled exception at 0x77d9eaeb in dumpel.exe: 0xC0000005: Access violation reading location 0xea789724.

Kosher — Fri, 07 Aug 2009 04:16:02 GMT

I ran the dump utility right after installation with option 4 and received the error above. I believe it could be due to the fact that SharePoint 2010 is not installed.
Comments: ** Comment from web user: Kosher **

It turns out the application did finish gathering logs, so it might not be server related.

Created Issue: Unhandled exception at 0x77d9eaeb in dumpel.exe: 0xC0000005: Access violation reading location 0xea789724.

Kosher — Fri, 07 Aug 2009 04:14:11 GMT

I ran the dump utility right after installation with option 4 and received the error above. I believe it could be due to the fact that SharePoint 2010 is not installed.

Commented Issue: SPSReport doesn't gather either ULS or PSCDiagnostic logs

Karuana — Tue, 03 Feb 2009 02:50:48 GMT

When running SPSReport on my SharePoint server I get the following error messages:

"The system cannot find the file specified.
TAIL: can't open c:\WINDOWS\SPSReports\Portal\rpt\servername_ULSLogs.txt"

"The system cannot find the file specified.
TAIL: can't open c:\WINDOWS\SPSReports\Portal\rpt\servername_PSCDiagLogs.txt"

Analysis:
======
- I don't get errors on my vanilla SharePoint box, and this due to the fact that SharePoint logs use the default log location (C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS)
- After changing the location to my E:\ drive I got both errors and SPSReport didn't gather both logs.

[ Note: I am talking about Trace Log: Central Adminsitration > Operations > Diagnostic Logging: Trace Log]

Is there a way to make SPSReport gather ULS and PSCDiagnostic logs where the Trace Logs resides on different location?

Thanks,

Yassar
Comments: ** Comment from web user: Karuana **

I also have this issue with the lastest version and logs that are in a different location. Any fix or cmd line switch would be grand.

Thanx
Karuana

Created Issue: 'HTTPErr' is not recognized as an internal or external command

getdriver — Thu, 29 Jan 2009 19:39:45 GMT

I receive the below error message when running the WSS/SPS2003(V2) branch on Windows 2003 , using (3) Full-Noisy-Open:

Thu 01/29/2009 20:23:05.12: Gathering IIS
'HTTPErr' is not recognized as an internal or external command,
operable program or batch file.

I think it is caused by using "&" sign at the following lines in 2003.cmd, below the Bug 966 entry:
%SPS_ECHO% %date% %time%: Gathering IIS & HTTPErr logs
%SPS_LOG% %date% %time%: Gathering IIS & HTTPErr logs >> %SPS_TOOL_RPT_DIR%\%COMPUTERNAME%_PROGRESS.TXT

If delete the "&" ,or write "and" instead, then I do not get the error.

Created Issue: SPSReport doesn't gather either ULS or PSCDiagnostic logs

Yassar — Fri, 16 Jan 2009 22:49:01 GMT

Created Issue: SPSReport V3.0.0.8 is expired

dschneider — Thu, 18 Dec 2008 10:28:11 GMT

The current version of SPSReport expired on December 17th. There is a alert box coming up during installation, which says, that I should get a new version of SPSReport.

Can anyone fix this issue or publish a newer version?

Thank you,
David

COMMENTED ISSUE: SPSReport doesn't like to be installed to a directory with spaces.

ChristopherGLewis — Tue, 29 Jan 2008 19:18:45 GMT

SPSReport doesn't work if it's installed to a directory with spaces.

Reproduction:
1) Install SPSReport to C:\Program Files\SPSReport. The Setup prompts to execute the application, and asks you for your MOSS version. It immediately reports that it's finished successfully.

2) open a CMD prompt, change directory to C:\Program Files\SPSRpeort\Portal\Bin.
Execute 2007.CMD or SPSReport.CMD.
Both will fail with many "Path not found" issues.

Diagnosis:
It appears that in the RunOpts section, setting the SPS_TOOL_ROOT_DIR doesn't add spaces. Whenever the CMD files execute an EXE or call a CMD, the path to the EXE or CMD doesn't include necessary quotes.

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:RunOpts - set run options
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: Determine the type of report that is being generated. This will form the cab file name
::
if not defined SPS_TOOL_ROOT_DIR set SPS_TOOL_ROOT_DIR=%CD:~0,-11%

Solution:
I believe that the RunOpts section in SPSRpt could be changed to include quotes:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:RunOpts - set run options
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
:: Determine the type of report that is being generated. This will form the cab file name
::
if not defined SPS_TOOL_ROOT_DIR set SPS_TOOL_ROOT_DIR=%CD:~0,-11%
set SPS_TOOL_DATA_DIR="%SPS_TOOL_ROOT_DIR%\%SPS_TOOL_SPECIALTY%"
set SPS_TOOL_BIN_DIR="%SPS_TOOL_DATA_DIR%\bin"
set SPS_TOOL_RPT_DIR="%SPS_TOOL_DATA_DIR%\rpt"
set SPS_TOOL_CAB_DIR="%SPS_TOOL_RPT_DIR%\cab"
set SPS_TOOL_DOC_DIR="%SPS_TOOL_DATA_DIR%\doc"
if not exist %SPS_TOOL_CAB_DIR% md %SPS_TOOL_CAB_DIR%
cd /d %SPS_TOOL_RPT_DIR%
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::

2007.cmd and 2003.cmd need their "Define global strings" section changed:

::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
: Define global strings
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
setlocal
set SPS_TOOL_NAME=Microsoft Platform Support Reporting Tool
rem Version string format = MajorVer.MinorVer.BuildMajorVer.BuildMinorVer
set SPS_TOOL_VERSION_NUM=V3.0.0.8
set SPS_TOOL_SPECIALTY=Portal
set SPS_TOOL_EVENTID_START=500
set SPS_TOOL_EVENTID_STOP=501

set SPSReports=%Systemroot%\SPSReports
if not defined SPS_TOOL_ROOT_DIR set SPS_TOOL_ROOT_DIR=%Systemroot%\SPSReports
if /i %PROCESSOR_ARCHITECTURE% == x86 set ProcArc=x86
if /i %PROCESSOR_ARCHITECTURE% == IA64 set ProcArc=IA64
if "%PROCESSOR_ARCHITEW6432%" == "" (
set ProcArc=%PROCESSOR_ARCHITECTURE%
) else (
set ProcArc=%PROCESSOR_ARCHITEW6432%
)

set SPS_TOOL_DATA_DIR="%SPS_TOOL_ROOT_DIR%\%SPS_TOOL_SPECIALTY%"
set SPS_TOOL_BIN_DIR="%SPS_TOOL_DATA_DIR%\bin"
set SPS_TOOL_RPT_DIR="%SPS_TOOL_DATA_DIR%\rpt"
set SPS_TOOL_CAB_DIR="%SPS_TOOL_RPT_DIR%\cab"
set SPS_TOOL_DOC_DIR="%SPS_TOOL_DATA_DIR%\doc"
if not exist %SPS_TOOL_CAB_DIR% md %SPS_TOOL_CAB_DIR%
DEL /F /Q %SPS_TOOL_RPT_DIR%\*.* > nul
cd /d %SPS_TOOL_RPT_DIR%
::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
Comments: ** Comment from web user: ChristopherGLewis **

It actually appears that *all* the CMD files have this code block:

set SPS_TOOL_DATA_DIR=%SPS_TOOL_ROOT_DIR%\%SPS_TOOL_SPECIALTY%
set SPS_TOOL_BIN_DIR=%SPS_TOOL_DATA_DIR%\bin
set SPS_TOOL_RPT_DIR=%SPS_TOOL_DATA_DIR%\rpt
set SPS_TOOL_CAB_DIR=%SPS_TOOL_RPT_DIR%\cab
set SPS_TOOL_DOC_DIR=%SPS_TOOL_DATA_DIR%\doc
if not exist %SPS_TOOL_CAB_DIR% md %SPS_TOOL_CAB_DIR%

and would have to be altered in all the Get-*.CMD files.

CREATED ISSUE: SPSReport doesn't like to be installed to a directory with spaces.

ChristopherGLewis — Tue, 29 Jan 2008 19:12:47 GMT

CREATED ISSUE: Desktop link points to previous location

mcintymp — Fri, 27 Apr 2007 15:44:19 GMT

When you run spsreport the first time, it creates a link on your desktop to allow you to download future version. The link directs you to the old location of SPSReport located on gotdotnet.com. It needs to reflect the new location