2

Closed

SharePointLogViewer has stopped working in SharePoint RTM demo VM

description

file attachments

Closed Jun 1, 2010 at 11:58 AM by
fixed.

comments

hasankhan wrote May 27, 2010 at 8:39 AM

Thank you chrisfie for reporting this bug.
Can you please provide the exception details that the dialog shows?

Is your executable accompanied with the SharePointLogViewr.exe.config file?

Xavid wrote May 31, 2010 at 7:01 AM

Crashes for me to. OS = Windows Server 2008 R2

Here is what Is in my logs

Log Name: Application
Source: Application Error
Date: 2010-05-31 08:58:45
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ********************************
Description:
Faulting application name: SharePointLogViewer.exe, version: 2.6.0.0, time stamp: 0x4be8a250
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0
Exception code: 0xc000041d
Fault offset: 0x000000000000aa7d
Faulting process id: 0xb60
Faulting application start time: 0x01cb008eb4581bbd
Faulting application path: ***********************************************
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: f42f694d-6c81-11df-9d5b-00155d016506
Event Xml:
1000
2
100
0x80000000000000

16499
Application




SharePointLogViewer.exe
2.6.0.0
4be8a250
KERNELBASE.dll
6.1.7600.16385
4a5bdfe0
c000041d
000000000000aa7d
b60
01cb008eb4581bbd
SharePointLogViewer.exe
C:\Windows\system32\KERNELBASE.dll
f42f694d-6c81-11df-9d5b-00155d016506

Xavid wrote May 31, 2010 at 7:01 AM

Crashes for me to. OS = Windows Server 2008 R2

Here is what Is in my logs

Log Name: Application
Source: Application Error
Date: 2010-05-31 08:58:45
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ********************************
Description:
Faulting application name: SharePointLogViewer.exe, version: 2.6.0.0, time stamp: 0x4be8a250
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0
Exception code: 0xc000041d
Fault offset: 0x000000000000aa7d
Faulting process id: 0xb60
Faulting application start time: 0x01cb008eb4581bbd
Faulting application path: ***********************************************
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: f42f694d-6c81-11df-9d5b-00155d016506
Event Xml:
1000
2
100
0x80000000000000

16499
Application




SharePointLogViewer.exe
2.6.0.0
4be8a250
KERNELBASE.dll
6.1.7600.16385
4a5bdfe0
c000041d
000000000000aa7d
b60
01cb008eb4581bbd
SharePointLogViewer.exe
C:\Windows\system32\KERNELBASE.dll
f42f694d-6c81-11df-9d5b-00155d016506

Xavid wrote May 31, 2010 at 7:02 AM

Crashes for me to. OS = Windows Server 2008 R2

Here is what Is in my logs

Log Name: Application
Source: Application Error
Date: 2010-05-31 08:58:45
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: ********************************
Description:
Faulting application name: SharePointLogViewer.exe, version: 2.6.0.0, time stamp: 0x4be8a250
Faulting module name: KERNELBASE.dll, version: 6.1.7600.16385, time stamp: 0x4a5bdfe0
Exception code: 0xc000041d
Fault offset: 0x000000000000aa7d
Faulting process id: 0xb60
Faulting application start time: 0x01cb008eb4581bbd
Faulting application path: ***********************************************
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: f42f694d-6c81-11df-9d5b-00155d016506
Event Xml:
1000
2
100
0x80000000000000

16499
Application




SharePointLogViewer.exe
2.6.0.0
4be8a250
KERNELBASE.dll
6.1.7600.16385
4a5bdfe0
c000041d
000000000000aa7d
b60
01cb008eb4581bbd
SharePointLogViewer.exe
C:\Windows\system32\KERNELBASE.dll
f42f694d-6c81-11df-9d5b-00155d016506

hasankhan wrote May 31, 2010 at 8:28 AM

Xavid do you have .NET Framework 3.5 installed in your machine?

Xavid wrote May 31, 2010 at 9:25 AM

Sorry about the repeat posts. Page did not reload when I pressed the submit button. Anyway, I do have .NET 3.5 installed. I have SharePoint 2010 also installed on that computer. Also Logviewer 1.5 works fine.

Xavid wrote May 31, 2010 at 9:47 AM

I ran the code in my environment. It crashes on or just after line 150 in MainWindow.xaml.cs. When i set watches on the the items in that line it seems like everything should work.

Anyway here is a picture of the message I get. Seems like it is some CLR problem. Perhaps it is a problem on my development environment. Any Suggestions?

hasankhan wrote May 31, 2010 at 10:32 AM

Xavid I am unable to reproduce this at my end.
The crash dialog in screenshot does not show the actual exception thrown on that line so I am not sure whats causing this problem.

Can you please try the following:

1) Run SPLV with administrator privileges.
2) Put a try/catch around that line and see if it still crashes.

Thank you for your help in resolving the issue.

Xavid wrote May 31, 2010 at 12:19 PM

            try
            {
                Environment.CurrentDirectory = String.IsNullOrEmpty(Properties.Settings.Default.LastDirectory) ? SPUtility.GetLogsLocation() : Properties.Settings.Default.LastDirectory;

            }
            catch (Exception ex)
            {

                throw ex;
            }
here is the ex.message

Could not find a part of the path 'C:\temp\sharepointlogviewer-46341df\SharePointLogViewer\bin\Debug\%CommonProgramFiles%\Microsoft Shared\Web Server Extensions\14\LOGS\'.

maybe it has problems with the %CommonProgramFiles% tag. It gets its information from line 226 on the SPutility.

...
logLocation = (string)property.GetValue(localDiagSvc, null);
logLocation = "%CommonProgramFiles%\Microsoft Shared\Web Server Extensions\14\LOGS\";

hasankhan wrote May 31, 2010 at 4:38 PM

Xavid Thank you for your help in finding the problem.
Your help is much appreciated.
I've updated the current build with the fix by expanding the environment variables in it.
You can download the latest build now.
Thanks

Hasan

hasankhan wrote Jun 1, 2010 at 4:52 AM

Xavid please confirm that bug is resolved so I can close this work item.

Thanks

Xavid wrote Jun 1, 2010 at 9:09 AM

Yep it works great. You can close the work item

jamilhaddadin wrote Jan 30, 2012 at 9:26 AM

I had the same problem, I run as different user who has access to SQL Server ( i.e. farm admin )

checking the eventview was very useful