Archive for error

MOSS 2007: LoadBalancer.RegisterLauncher failed

August 18, 2008 at 4:10 pm · Filed under Event Viewer, MOSS, error ·Tagged , , ,

Description:

Event Viewer of MOSS 2007 server machine filled with “LoadBalancer.RegisterLauncher failed” error after almost every 30 to 40 seconds. Description is as under:

Event Type: Error
Event Source: Office SharePoint Server
Event Category: Launcher Service
Event ID: 6102
Date:  8/18/2008
Time:  8:45:52 AM
User:  N/A
Computer: ABC
Description:
LoadBalancer.RegisterLauncher failed:  Unable to connect to the remote server

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

Workaround:

One workaround is to restart the service and this will work fine until the next restart of the machine. Other is to move from Central Administration -> Operation -> Service Account. Select the service “Load Balancer Service” and select the account “Network Service”.

Comments

After upgrade, Internet Users Cannot Access SharePoint 2003 sites

August 16, 2008 at 10:56 pm · Filed under MOSS, error, upgrade ·Tagged , , , , ,

Scenario:

Our SharePoint 2003 URL is exposed to internet. Let it be http://share.companyname.com .

 Our SharePoint 2003 was running on port 80. When we upgraded using gradual approach, SharePoint 2003 was moved to another port, say, 42154 and new MOSS 2007 started running on port 80.

Now, the functionality is that when we try to access a SharePoint 2003, we are redirected. Like if when we tried to access http://share.compantname/sites/abc , we were redirected to SharePoint 2003 and URL turns out to be http://share:42154/sites/abc. This works find for intranet users but for internet users http://share:42154/sites/abc is not Fully Qualified Domain Name (FQDN), so they get stuck with page not found error.

 

Workaround:                                  

What we did was used SSL for port 42154. One can do this by going to IIS Manager, select Web Site running SharePoint 2003. Right click and click on properties. In front of TCP PORT: 42154, you have SSL Port: test box. Write 443. You will be able to access SharePoint 2003 sites using httpS://share.companyname.com/sites/abc

 

What went wrong?

When started Upgrade by clicking on “Begin Upgrade”, we didn’t put host header name and did not exposed that host header to internet

 

 

For more explanation, kindly visit the heading “Determine and create new domain names (gradual upgrade only)” at the following link:

http://office.microsoft.com/download/afile.aspx?AssetID=AM101638521033

Comments

MOSS 2007: Server error: http://go.microsoft.com/fwlink?LinkID=96177

July 1, 2008 at 6:00 pm · Filed under MOSS, STSADM, error ·Tagged , , , , , ,

While trying to install WSS 3.0 SP1 (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx) the installation get stuck at task 9 of 10 of SharePoint Products and Technology Configuration Wizard. When tried to access the server, encountered the following error:

 

Server error: http://go.microsoft.com/fwlink?LinkID=96177

 

When look into the “Event Viewer”, found the following error description:

 

The schema version (3.0.149.0) of the database DATA
DATABASE_NAME on DATABA_SESERVER_NAME is not consistent with the expected database schema version (3.X.X.X) on DATABASE_NAME.  Connections to this database from this server have been blocked to avoid data loss.  Upgrade the web front end or the content database to ensure that these versions match.

 

Resolution:

 

The first thing we did was either remove content database from the web application which are having the error or Detach the database. This doesn’t seem to work. So we run the command

 

stsadm –o upgrade –inplace –url Central_Administration_URL –forceupgrade

 

and we were back in the business J.

Comments (2)

MOSS 2007: Event Viewer Error Code 6482 and 6398

June 30, 2008 at 5:04 pm · Filed under MOSS, error ·Tagged , , , , , , ,

Recently we encountered a problem in the Event Viewer of MOSS server machine. The event viewer is getting populated after approximately every 40 second with the Error Code 6482 and 6398. Details of the error are as under:-

 

Event ID:   6482

 

Event Type:        Error

Event Source:     Office SharePoint Server

Event Category:  Office Server Shared Services

Event ID:   6482

Date:        6/24/2008

Time:                10:12:41 AM

User:         N/A

Computer:  ABC

 

Description:

Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (f0fc6cd7-fd20-49e3-8965-218a64ed4fbc).

 

Reason: An error occurred loading a configuration file: Access to the path ‘C:\Program Files\Microsoft Office Servers\12.0\WebServices\Root\ibgueyl_.tmp’ is denied. (C:\Program Files\Microsoft Office Servers\12.0\WebServices\Root\web.config)

 

Techinal Support Details:

System.Configuration.ConfigurationErrorsException: An error occurred loading a configuration file: Access to the path ‘C:\Program Files\Microsoft Office Servers\12.0\WebServices\Root\ibgueyl_.tmp’ is denied. (C:\Program Files\Microsoft Office Servers\12.0\WebServices\Root\web.config) —> System.UnauthorizedAccessException: Access to the path ‘C:\Program Files\Microsoft Office Servers\12.0\WebServices\Root\ibgueyl_.tmp’ is denied.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)

   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)

   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)

   at System.CodeDom.Compiler.TempFileCollection.EnsureTempNameCreated()

   at System.CodeDom.Compiler.TempFileCollection.AddExtension(String fileExtension, Boolean keepFile)

   at System.CodeDom.Compiler.TempFileCollection.AddExtension(String fileExtension)

   at System.Configuration.Internal.WriteFileContext..ctor(String filename, String templateFilename)

   at System.Configuration.Internal.InternalConfigHost.StaticOpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext, Boolean assertPermissions)

   at System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext, Boolean assertPermissions)

   at System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)

   at System.Configuration.Internal.DelegatingConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)

   at System.Configuration.UpdateConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)

   at System.Configuration.MgmtConfigurationRecord.SaveAs(String filename, ConfigurationSaveMode saveMode, Boolean forceUpdateAll)

   — End of inner exception stack trace —

   at System.Configuration.MgmtConfigurationRecord.SaveAs(String filename, ConfigurationSaveMode saveMode, Boolean forceUpdateAll)

   at System.Configuration.Configuration.SaveAsImpl(String filename, ConfigurationSaveMode saveMode, Boolean forceSaveAll)

   at System.Configuration.Configuration.Save()

   at Microsoft.Office.Server.Administration.SharedWebServiceInstance.ProvisionSharedResourceProviderWebConfigSettings(SharedResourceProvider srp)

   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 ID:   6398

 

Event Type:        Error

Event Source:     Windows SharePoint Services 3

Event Category:  Timer

Event ID:   6398

Date:        6/27/2008

Time:                3:07:38 PM

User:         N/A

Computer:  ABC

Description:

The Execute method of job definition Microsoft.SharePoint.Administration.SPUpgradeJobDefinition (ID 2d9efa9c-d2e8-4be4-9312-b8ff74b93247) threw an exception. More information is included below.

 

Requested registry access is not allowed.

 

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

 

Resolution:

 

After a lot of net search, the final solution was of installing Office SharePoint Server 2007 Service Pack 1 available at the URL (http://technet.microsoft.com/en-us/office/sharepointserver/bb735839.aspx).

 

But for this solution work, you should have a server with version older than 12.0.0.6219.

You can check the version number by running SharePoint Central Administration and moving to Operation to “Servers in Farm”.

 

Hope that this solution works for you as well. J

 

Comments

SharePoint Upgrade: Prescan.exe

May 15, 2008 at 8:52 pm · Filed under MOSS, SharePoint, error, upgrade ·Tagged , , , ,

You can download prescan.exe from this link or it can be found at “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN” along with preupgradescanconfig.xml

 

PreScan is a pre-upgrade scan tool used to scan all Web sites in your environment (by using the /all parameter) or to scan a specific URL (by using the /v <URL> parameter). If you do not supply a scoping parameter, all Web sites will be scanned. The pre-upgrade scan tool takes the following parameters:

 

Parameter

Description

/all

Scans all site collections in a server farm.

/v <URL>

Scans all site collections at a specific URL.

/c preupgradescanconfig.xml

Uses the preupgradescanconfig.xml file while scanning. This configuration file contains additional logic to identify the portal site templates as standard templates used by SharePoint Portal Server 2003 rather than as custom templates based on Windows SharePoint Services 2.0. You must use this parameter when scanning site collections based on SharePoint Portal Server 2003. This parameter has no effect when scanning site collections based on Windows SharePoint Services 2.0.

 

 

To run Prescan.exe, perform the following steps:

 

On the command line, change to the folder that contains the file, and then run the prescan.exe command with the appropriate parameters. For example,

 

prescan.exe /all or

prescan.exe /c preupgradescanconfig.xml /all or

prescan.exe /c preupgradescanconfig.xml /v http://sps

  

I will recomend to use the second option.

  

After successful run, it will generate reports with name PreupgradeReport_uniqueID_Log.txt (where uniqueID is a number string) located in the temp directory on the computer of the user who ran the tool (for example, C:\Documents and Settings\User\Local Settings\Temp or Temp\2).

 

An example output is:

 

=====================Totals===================

Number of sites skipped (already scanned):   0

Number of sites scanned:   12

Number of broken sites:   0

Number of webs scanned:   41

Number of broken webs:   0

Number of webs using custom template:   0

Number of pages scanned:   4145

Number of unghosted pages:   40 (0.97% of total).

 

 

For errors, check Bill Baer blog:

 

http://blogs.technet.com/wbaer/archive/2006/12/22/prescan-errors-what-they-mean.aspx

 

Comments

SharePoint 2003: Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists.

May 14, 2008 at 11:45 pm · Filed under SharePoint, error ·Tagged , , , ,

Error:

 

Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists.

 

Description:

 

We tried to upgrade SPS 2003 to MOSS 2003 using in place upgrade which was a disaster. Fortunately it was our development serverJ. We uninstall SPS 2003 and reinstall SPS 2003. When we try to open the portal main page “http://portal/default.aspx”, found the error “Web Part Error: This page has encountered a critical error. Contact your system administrator if this problem persists.” on every web part. Other links like “Sites” were also not working.

 

Resolution:

 

It turns out that our SharePoint Central Administration and Virtual Server was running under ASP.Net 2.0…… We changed it back to 1.1…… through IIS and everything was fine.     

Comments (1)

ERROR: SharePoint Portal Server 2003 on the server does not match the language you are currently trying to install

May 8, 2008 at 10:59 pm · Filed under SharePoint, error ·Tagged , , ,

Exception:

 

When you try to install SharePoint Portal Server 2003, you get the following error:

 

“SharePoint Portal Server 2003 on the server does not match the language you are currently trying to install.”

 

Reason:

 

On my side, this exception occur when I try to install SharePoint Portal Server 2003 and uninstall process get stuck. I restart the system and when try to install SharePoint Portal Server 2003, got the above the exception.

 

Resolution:

 

Go from Start -> Run and type “regedit”.

 

Move from HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> SharePoint Portal Server

 

Either delete the entry “SharePoint Portal Server” or rename it like “SharePoint Portal Server discard”.

Comments

« Previous entries