Deployment troubleshooting

 

1.    Installing

a)     Install SQL Server by source file, run setup.exe under tools folder firstly, then run servers setup.exe.

b)     Before install the sharepoint.exe on window server 2008, install wss 3.0 sp1 firstly.

2.    Configuration

Delete SSP Error

To delete a ssp,be sure its subsites are deleted. STSADM.EXE -o deletessp -title sharedservices2 -deletedatabases

Delete Search Content Source

Can not renew a same content source as deleted one. To fix this, recommend to create a new ssp. Import user profiles and reconfigure search content source agin.

Can’t finished configuration by configuration wizard

Try to run: PSCONFIG.EXE -cmd configdb

Failed to register SharePoint services.

An exception of type System.Data.SqlClient.SqlException was thrown. Additional exception information: Cannot open database "SharedServices1_DB_5cb359e7-2d3b-46c7-9bbd-9bed1697ae62" requested by the login. The login failed. Login failed for user 'BOSSINI\Administrator'.

Check your database is ok, the you can reconfigure again.

Rename server

1.    Rename all alternate url to new server name under Operations in Sharepoint Central Administrations 2.    stsadm -o renameserver -newservername <newname> -oldservername <oldname> 3.    rename computer name and restart 4.    Restart Office SharePoint Server Search 5.    change search content source and scopes to new servername 6.    personal site settings need to be updated

Event ID: 6800

The database <databasename> on server\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures. A solution is available to administrators of SharePoint Products and Technologies deployments experiencing the following application event after introducing WSS October public update KB934525.   Event Type: Error Event Source: Windows SharePoint Services 3 Event Category: Topology Event ID: 6800 Date: 10/17/2007 Time: 8:09:40 PM User: NA Computer: HOME Description: The database WSS_Content on HOME\Microsoft##SSEE is not accessible to missing Windows Internal Database signatures.

1. Run the following STSADM operations to stop and start the SPWebService: stsadm -o provisionservice -action stop -servicetype spwebservice -servicename "" stsadm -o provisionservice -action start -servicetype spwebservice -servicename "" 2. Instantiate the upgrade by executing psconfig.exe or psconfigui.exe.

The cause of this issue is the SPWebService instance failed to finish provisioning. The status of that service is marked as provisioning. However, it has done enough provisioning work so that the user sites are working and/or during upgrade, the upgrade code skipped any web service instances that are not online, upgrading the administration sites; however, skipping the user sites.

Event ID : 6102

The Application event log has one entry: Source: Office SharePoint Server Category: Launcher Service Event ID: 6102 Description:LoadBalancer.RegisterLauncher failed: Unable to connect to the remote server

Login into SharePoint Server Web based,  Click Central Administration Click Operations Click Service Account Change the service account to "Document Conversions Load Balancer Service" And Select a "Network Services" Click Save Then restart the service on the server in operations.(to Select current indexer) This should fix this problem.

Event ID: 55555

Log Name:      Application Source:        Office SharePoint Server Date:          4/7/2009 4:00:15 PM Event ID:      5555 Task Category: User Profiles Level:         Error Keywords:      Classic User:          N/A Computer:      intranet.bossini.local Description: Failure trying to synch web application b4b2db98-758d-4a59-bca3-5b43f6e5c6ff, ContentDB 7a94fe64-67bb-4f85-a38b-0b8a686bc538 Exception message was Object reference not set to an instance of an object.

Run the follow command to delete old database: STSADM.EXE -o sync -deleteolddatabases 0

Event ID 6062

Open the Launcher and Load Balancer .config files in the office server bin folder (usually C:\Program Files\Microsoft Office Servers\12.0\Bin) In the launcher file (Microsoft.Office.Server.Conversions.Launcher.exe.config) comment in the key "keyIPExclude" and set the value to the IP address(s) that you want to exclude. For example, <add key="keyIPExclude" value="192\.168\.115\.14" /> In the load balancer file (Microsoft.Office.Server.Conversions.LoadBalancer.exe.config) add the ip exclude key to the <LoadBalancerSettings> section. For example, <add key="keyIPExclude" value="192\.168\.115\.14" /> If you have multiple IP’s that you want to exclude use the following syntax for the key value <add key="keyIPExclude" value=" (192\.168\.115\.14)|( 192\.168\.115\.15)” /> Refer to Here

Auto login On Xp

In IE tools -> Security ->IE local intranet-> custom Level->user Authentication, Selec 'Automatic login with current user and password'

 

转载于:https://www.cnblogs.com/qq273000969/archive/2010/04/07/1706751.html