Office 2007, 2010 on Windows Vista / Windows 7 prompts for user credentials when opening documents in SharePoint 2007 / 2010

This should work for you You are prompted to enter your credentials when you access an FQDN site from a computer that is running Windows Vista or Windows 7 and has no proxy configured

A customer of mine installed Windows 7 and Office 2007. They migrated there Office from 2003 to 2007. When they try to open an Office document the client asked to authenticate against to the server. With Windows XP and Office 2003 everything works fine. The solution was very simple. They have to run Office 2007 Windows XP compatiblity mode by default.

To accomplish you should put following registry keys to your system:

[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers]
„C:\Program Files\Microsoft Office\Office12\WINWORD.EXE“=“WINXPSP2“
„C:\Program Files\Microsoft Office\Office12\EXCEL.EXE“=“WINXPSP2“
„C:\Program Files\Microsoft Office\Office12\POWERPNT.EXE“=“WINXPSP2“

Be care with the slashes. If you use a reg file you need to use double slashed \\ instead of one slash \.

If you have no access to the HKLM hive you can use the HKCU hive instead.

This is a known issued. If above solution do not work and for more details about this issued check following blog entry at msdn Office 2007 prompt for user credentials.

Timo

Veröffentlicht unter Infrastructur, MOSS, MOSS 2007, WSS 3.0 | Kommentare deaktiviert für Office 2007, 2010 on Windows Vista / Windows 7 prompts for user credentials when opening documents in SharePoint 2007 / 2010

Access Denied Error, Search Problems when installing .NET Framework 3.5

Today when I tried to install the .NET Framework 3.5 I got following error within your event log:

 

Event Type: Warning
Event Source: Office Server Search
Event Category: Gatherer
Event ID: 2436
Date: 26.03.2009
Time: 11:59:50
User: N/A
Computer: <YourServer>
Description:
The start address <YourSiteCollection> cannot be crawled.

Context: Application ‚SharedServices‘, Catalog ‚Portal_Content‘
Details:
Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (0x80041205)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

When you start to analyses the error you will find a Knowledge base article on the Microsoft homepage KB887993. Within this article they describe authentication issues to access web pages.

Use the second method to apply following registry key

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa]
„DisableLoopbackCheck“=dword:00000001

When you applied above registry value you get a second error within your event log:

 

Event Type: Error
Event Source: Windows Search Service
Event Category: Gatherer
Event ID: 3083
Date: 26.03.2009
Time: 15:26:27
User: N/A
Computer: <YourServer>
Description:
The protocol handler Search.Mapi2Handler.1 cannot be loaded. Error description: Class not registered.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

What for a strange error. It seems that the search class is not registered yet. If you take a closer look within the „Component services“ you find a discrepancy. If you search for osearch and check the permission entries you will see that you don’t have permission entries for your Index / Service account from your MOSS farm. You may miss the „WSS_Admin_WPG“ and „WSS_WPG group“ too.

If you take a look within your central administration now you will see that the search is running. But if you open your service manager you see that the service is stopped.

The simple resolution is to start the service from your search. You can do that on command line.

stsadm -o osearch -action start

That’s all. It seems if you start the service that all security information on the object will be set correctly.

It disappointing me that if you upgrade the .NET Framework to a higher version, what is good for your workflow functionality, that you run in problems like that. Hopefully this help someone.

For more information about the osearch commands check the technet article Osearch: Stsadm operation (Office SharePoint Server).

Timo

Veröffentlicht unter .NET, Errors, Infrastructur | Kommentare deaktiviert für Access Denied Error, Search Problems when installing .NET Framework 3.5

MSSDMN EventID 26

Sometimes you get an application popup from MSSDMN (Microsoft Search Service Daemon) with following error message:

mssdmn.exe – Application Error

The instruction at „0x77ef6114“ referenced memory at „0x0000000087“. The memory could not be „written“.
Click on OK to terminate the program

or

mssdmn.exe – Application Error

The instruction at „0xffffffff“ referenced memory at „0x00000000f5“. The memory could not be „read“.
Click on OK to terminate the program

The messages are different even on the same system!

If you look a bit closer you will find following information message within your system log:

 

Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 20.09.2008
Time: 02:03:51
User: N/A
Computer: <yourServerName>
Description:
Application popup: mssdmn.exe – Application Error : The instruction at „0x26439134“ referenced memory at „0x000000c0“. The memory could not be „read“.

Click on OK to terminate the program

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

Be care that message in your system log can deffered from your application popup. This is because the message popup comes when you make a crawl of your content.

For analysing check the time stamps on all EventID’s 26. You will see that they are a kind of „periodically“.

Why this happens? Do you have FoxIT PDF IFilter (mostly on x64 systems) installed? You will. This do not happen if you use the Adobe PDF IFilter. The problem is that you don’t have any choice right now within x64 systems.

This comming up from FoxIT directly:

We are pretty certain that these errors arise when a searchable PDF has been created from a „dirty“ scan where there is a lot of background „mush“ behind the text in the PDF.
As soon as the Foxit iFilter x64 tries to index one of these „dirty“ PDFs, the server throws this app error.

For a fix you have to wait for a next version of FoxIT (v1.0.0.1729 wont fix this problem).

Right now I see no issue within a production environment. So you can still use it.

Timo

Veröffentlicht unter Errors, Events, IFilter | Kommentare deaktiviert für MSSDMN EventID 26

Multiple timer job error on MOSS 2007. Event ID 6398, 6482, 7076

If you start to research with MOSS and above Event ID’s you won’t have luck to find any information about. The problem with above errors are that the event refer to an IIS problem. The errors occure because two threads access IIS 6.0 (Windows Server 2003) or IIS 7.0 (Windows Server 2008).

 

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 7076
Date: 28.07.2008
Time: 22:48:20
User: N/A
Computer: <yourServerName>
Description:
An exception occurred while executing the Application Server Administration job.

Message: Exception from HRESULT: 0x80005006

Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80005006): Exception from HRESULT: 0x80005006

Server stack trace:
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.PutEx(Int32 lnControlCode, String bstrName, Object vProp)
at System.DirectoryServices.PropertyValueCollection.OnClearComplete()
at System.DirectoryServices.PropertyValueCollection.set_Value(Object value)
at Microsoft.SharePoint.AdministrationOperation.Metabase.ApplicationPool.set_UserName(String value)
at Microsoft.SharePoint.AdministrationOperation.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionIisApplicationPool(String name, Int32 identityType, String userName, String password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionIisApplicationPool(String name, Int32 identityType, String userName, String password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.Office.Server.Administration.SharedWebServiceInstance.CreateSharedWebService
ApplicationPool(SharedResourceProvider srp)
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

 

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server Shared Services
Event ID: 6482
Date: 28.07.2008
Time: 22:48:20
User: N/A
Computer: <yourServerName>
Description:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (e9f5b621-092d-4abe-b718-9bf6ae92659d).

Reason: Exception from HRESULT: 0x80005006

Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80005006): Exception from HRESULT: 0x80005006

Server stack trace:
at System.DirectoryServices.Interop.UnsafeNativeMethods.IAds.PutEx(Int32 lnControlCode, String bstrName, Object vProp)
at System.DirectoryServices.PropertyValueCollection.OnClearComplete()
at System.DirectoryServices.PropertyValueCollection.set_Value(Object value)
at Microsoft.SharePoint.AdministrationOperation.Metabase.ApplicationPool.set_IdentityType(ApplicationPoolIdentityType value)
at Microsoft.SharePoint.AdministrationOperation.SPProvisioningAssistant.ProvisionIisApplicationPool(String name, ApplicationPoolIdentityType identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionIisApplicationPool(String name, Int32 identityType, String userName, String password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.SharePoint.AdministrationOperation.SPAdministrationOperation.DoProvisionIisApplicationPool(String name, Int32 identityType, String userName, String password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisApplicationPool(String name, Int32 identityType, String userName, SecureString password, TimeSpan idleTimeout, TimeSpan periodicRestartTime)
at Microsoft.Office.Server.Administration.SharedWebServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

 

Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: Timer
Event ID: 6398
Date: 28.07.2008
Time: 22:47:20
User: N/A
Computer: <yourServerName>
Description:
The Execute method of job definition Microsoft.Office.Server.Administration.ApplicationServerAdministrationServiceJob (ID f44c72ae-dceb-4934-8884-65c04a0077b8) threw an exception. More information is included below.

Exception from HRESULT: 0x80005006

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

 

You can download a fix for KB946517 here. When you request the hotfix download for IIS 6.0 Fix220121 and for IIS 7.0 Fix222292.

Don’t be confused that the article write only about IIS 6.0 because when you request the hotfix you can download the fix as well for Vista (IIS 7.0) which has the same code base like Windows Server 2008.

Be aware: A lot of people write about following hotfix (KB923028). This hotfix handles a .NET 2.0 bug which is already fixes with SP2 of the .NET Framework. This will not resolve above event entries!

One hint about the fix. If you apply you need to restart your MOSS 2007 server. I applied this fix on an WFE in a MOSS farm. My Application server started to shutdown all IIS Web Applications. I was really confused about. You just need to restart all Web Applications manually and all errors are gone.

Timo

Veröffentlicht unter Errors, Infrastructur, MOSS 2007 | Kommentare deaktiviert für Multiple timer job error on MOSS 2007. Event ID 6398, 6482, 7076

Restore SSP and Slipstream do not work

Getting a strange situation last view weeks. I needed to restore the SSP within a new farm.

The old farm was installed in following situation:

a) MOSS2007
b) SP1
c) Build 12.0.0.6305.5000
d) Build 12.0.0.6317.5000

All patches was applied without slipstreaming.

When I started to create my slipstream CD I applied all patches at once. During the test (nothing was installed slipstreamed) eveything works great. Restore of the SSP was really easy. No problem.

Because of above experience It was possible to go relaxed in mainanance time. When I started to restore the SSP a strange error occured. Ok. Uninstall everything Slipstream new. Restore again. I tried that in different situations. Nothing worked. At 2:00 AM the mirror was going back into the server. Believe me. A really frustrating situation.

Two weeks figuring out which error occured camed a strange result! Slipstreaming does not work. If everything is installed manually (see above) the restore works great. If you use a slipstreaming MOSS 2007 CD the restore will fail. A colleague of mine made 8 different tests. Last friday it was possible to restore everything successfully. But not slipstreamed.

Today I give that error to Microsoft. Understand. If slipstreaming is not working what bring us the future? Not all customers make good documentation. As well. What for a f… work.

Resume: Right now if you get following error

 

Shared Services Provider restore failed.

Reason: The specified SearchSharedDatabase Name=SharePoint_SSP_Search_DB=SPDatabaseServiceInstance has been upgraded to a newer version of SharePoint. Please upgrade this SharePoint application server before attempting to access this object.

Check the event log for details.

Note: SSP provisioning will be retried periodically. If you correct the error that caused this failure, provisining will subsequently succeed. To stop provisioning from being retired, delete the SSP.

 

…and you used slipstreaming install everything manually. That should work!

Hint: You get above error as well if you patch your target machine one patch level higher! I tried this with the latest patch Build 12.0.0.6318.5000. So this will not help you. The problem is that above message is just confusing and not the reallity.

Timo

Veröffentlicht unter Infrastructur, MOSS 2007 | Kommentare deaktiviert für Restore SSP and Slipstream do not work