SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems (http://www.crwatersolutions.com) - Contact me direct: david_sterling@sterling-consulting.com or call 704-873-8846 x704.

Search This Blog

Friday, March 19, 2010

WCF Service cannot be tested under SharePoint

Using WCF with SharePoint? Finding that the service can't be checked though it is working? Check the IIS 7.0 Application Pool setttings for the "Managed Pipeline Mode" - if it is set to "Classic" (as SharePoint demands), you'll get:

Server Error in '/' Application.


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

The resource cannot be found.

Description: HTTP 404. The resource you are looking for (or one of its dependencies) could have been removed, had its name changed, or is temporarily unavailable. Please review the following URL and make sure that it is spelled correctly.

Requested URL: //.svc

To check it, change the Mode to be "Integrated" and the service (if installed correctly) will render as it is supposed to. When done, change it back.

Note: As I mentioned in my previous post, this setting will prevent you from getting to the SharePoint site; after you have tested and made sure it is working, be sure that t

You receive a Server Application Unavailable in MOSS/WSS using IIS 7.0

Recently came across a clients problem - on attempting to render the SharePoint Site, they received:

Server Application Unavailable


The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
Administrator Note: An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

After some checking, it turns out that it was due to the Application Pool - while properly setup (the site had been operating just fine), the "Managed Pipeline Mode" was set to Integrated - changing this back to Classic (SharePoint 2007 requires this) fixes the problem.

Monday, March 15, 2010

Installing SharePoint 2010 using a SQL Named Instance

When doing the setup for SharePoint and connecting to the database for the first time and you are using a named instance, for example: SQLx64\SP2010SQL, you must specify the full path. Note however, you have to be sure the text case is exact as it is in SQL Server.

Doing a new install the other day, the error message displayed was quite alarming - protocol errors or some such. I had inadvertantly entered the name in uppercase as in: SQLX64\SP2010SQL.

Thursday, March 11, 2010

Windows Data Execution Prevention detected an add-on - Windows 2008, IE8, SharePoint, Office

In a development VM system running Windows Server 2008 R2, I had inadvertantly left the Automatic Updates to On. Naturally, they downloaded and rebooted overnight so the next morning, I logged on in had the unpleasant surprise of ALL of my SharePoint sites crashing (including Central Admin). On attempt to open the page, it would partially display then immediately redirect to a new URL:

res://ieframe.dll/acr_depnx_error.htm#http://

This page displays the default message:
Windows Data Execution Prevention detected an add-on trying to use system memory incorrectly. This can be caused by a malfunction or a malicious add-on

Checking the event log, I found this:

Faulting application name: iexplore.exe, version: 8.0.7600.16385, time stamp: 0x4a5bc69e

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x388
Faulting application start time: 0x01cac155f16f8d64
Faulting application path: C:\program files (x86)\internet explorer\iexplore.exe
Faulting module path: unknown
Report Id: 465927c2-2d49-11df-8e60-000c29c0b5a1
 
I also happened to try to open Word - bam - application fault as well. Event log showed:
 
Faulting application name: WINWORD.EXE, version: 12.0.6514.5000, time stamp: 0x4a89d533

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x00000000
Faulting process id: 0x10ac
Faulting application start time: 0x01cac156e171c287
Faulting application path: C:\Program Files (x86)\Microsoft Office\Office12\WINWORD.EXE
Faulting module path: unknown
Report Id: 21b31ab7-2d4a-11df-8e60-000c29c0b5a1
 
All solutions I looked at indicated either DEP, removing add-ons or somehow related to flash. Not the case - I followed all of them to no avail. I revereted to a backup and ran Windows Update manually and lo and behold, two Microsoft Office Security Updates, when removed, corrected the problem:

Security Update for the 2007 Microsoft Office System (KB969613)

Download size: 1.9 MB
Update type: Important
A security vulnerability exists in the 2007 Microsoft Office System and the Microsoft Office Compatibility Pack that could allow arbitrary code to run when a maliciously modified file is opened. This update resolves that vulnerability.

More information:

http://www.microsoft.com/downloads/details.aspx?FamilyId=63BD8F14-E736-46CE-AF66-D30F17461E5A&displaylang=en

Security Update for the 2007 Microsoft Office System (KB974234)
Download size: 525 KB
Update type: Important

This update resolves a problem that can cause programs that use the Outlook View Control with Forms 2.0, such as Microsoft Office Outlook with Business Contact Manager, to stop functioning as expected after Security Update for Microsoft Office Outlook 2007 (KB972363) is installed.

http://support.microsoft.com/kb/974234

Note that when I tested Word with the patches removed, I received an odd install message:



After this, Word started normally.

So to verify, I tried adding them back - while I suspected KB969613 was the problem, adding both back, one at a time corrected the problem completely.

NOTE: As an update, I repeated this on another system with the same problem; I ended up removing all of the Security Updates that occurred (approx release date 3/9/2010) - this included:

Office updates:

969559
978380
973704
972581

Security updates:
977724
969693
957789
973709
978382

Update for Junk Email Filter:
979895

As always...good luck!