search

bramdejager / spcb

The SharePoint Client Browser (SPCB) uses the CSOM to connect to a remote SharePoint site collection and shows the site structure with related properties and values.
GNU General Public License v2.0
174 stars 48 forks source link

Problem on Windows 7 SP1 #17

Closed bramdejager closed 6 years ago

bramdejager commented 6 years ago

Good day,

The application does not want to open on Windows 7. It gives this error message: "SharePoint 2013 Client Browser has stopped working"... Please help.

Problem signature: Problem Event Name: APPCRASH Application Name: SPCB2013.exe Application Version: 1.5.1.0 Application Timestamp: 54b37560 Fault Module Name: clr.dll Fault Module Version: 4.0.30319.17929 Fault Module Timestamp: 4ffa59b1 Exception Code: c00000fd Exception Offset: 00000000000063f7 OS Version: 6.1.7601.2.1.0.256.48 Locale ID: 7177 Additional Information 1: 911e Additional Information 2: 911e48f5c618ab9757fee9b961077af6 Additional Information 3: 5b2d Additional Information 4: 5b2d1e5ae444b81d2669d1b0d2a251d3

This work item was migrated from CodePlex

CodePlex work item ID: '25907' Assigned to: 'BdeJager' Vote count: '2'

bramdejager commented 6 years ago

[BdeJager@12-1-2015] Could it be the case it has to do with "Faulting module name: clr.dll" error message when you run a Microsoft .NET Framework 4-based application? There is a KB article addressing a simular issue it looks like, check out KB2640103.

Regards, Bram

bramdejager commented 6 years ago

[UnknownUser@12-1-2015]

bramdejager commented 6 years ago

[alisalih@22-1-2015] Hi,

v1.5.1 is crashing on startup on my dev machine, with W2k8 R2 Enterprise. v1.4.0 was starting without issues.

Problem signature: Problem Event Name: APPCRASH Application Name: SPCB2013.exe Application Version: 1.5.1.0 Application Timestamp: 54b37560 Fault Module Name: clr.dll Fault Module Version: 4.0.30319.34209 Fault Module Timestamp: 5348a1ef Exception Code: c00000fd Exception Offset: 0000000000003090 OS Version: 6.1.7601.2.1.0.274.10 Locale ID: 1033 Additional Information 1: 136c Additional Information 2: 136c27c56db809f51a885916f18f0ca7 Additional Information 3: 13b6 Additional Information 4: 13b6347fb61420685a05993cee0be469

bramdejager commented 6 years ago

[UnknownUser@26-1-2015]

bramdejager commented 6 years ago

[Poidl@26-1-2015] Same here, Windows Server 2012

Seems to be the case which is referenced by the KB-article. However, MS does not provide a fix (without contacting the Support personally and i guess this has to be paid). So, as 1.4 worked like a charm, I Switch back to 1.4

bramdejager commented 6 years ago

[alisalih@28-1-2015] I found a workaround that works for me:

Change compatibility setting on the EXE file to Windows 7 (My computer is W8.1) and it works.

bramdejager commented 6 years ago

[Poidl@29-1-2015] Workaround not working on Windows Server 2012

bramdejager commented 6 years ago

[cveld@6-2-2015] Workaround is not working on Windows Server 2008 R2

bramdejager commented 6 years ago

[BdeJager@24-2-2015] Hi all,

I'm working on fixing the issue. I have found the root cause of the appcrash. I hope to get the fix and new features out within days.

Bram

bramdejager commented 6 years ago

[BdeJager@24-2-2015] New release is out and fixes this bug, please check SharePoint Client Browser v1.6

bramdejager commented 6 years ago

[UnknownUser@13-4-2015]

bramdejager commented 6 years ago

[UnknownUser@13-4-2015]

bramdejager commented 6 years ago

[UnknownUser@17-8-2015]