- For ease of deployment, copy the .cab file to the following location, where Office SharePoint Server 2007 is installed:
C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\binThis should be the same as the location of Stsadm.exe. Ensure that you update the path on your computer if it does not match the default location.
- Click Start, click Run, and then type cmd.
- Type cd "C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\bin"
- Run the following command to deploy your Web Part accross the entire farm:
stsadm.exe -o addwppack -filename yourcabfilename.cab -globalinstall -force
- Run the following command to deploy your Web Part to a specific website:
stsadm.exe -o addwppack -filename yourcabfilename.cab -url http://teleport -globalinstall -force
- After the command returns with "Operation completed successfully," run the following command:
- Check central administration / solution management to see where the solutions are registered as deployed by SharePoint.
Wednesday, May 16, 2007
Sunday, May 13, 2007
The symptom of the problem is that when trying to access the site usage reporting in MOSS the user (who does have access) is prompted to authenticate, upon failing to authenticate the worker process falls over.
The app event reports the following error: .NET Runtime version 2.0.50727.42 - Fatal Execution Engine Error
The SSP1 & Portal application pools both stopped running.
The resolution is the application of a non-public hotfix to ASP.net 2.0: http://support.microsoft.com/kb/913384
Recently while creating new web applications, I received the following error:
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchAdminSharedWebServiceInstance (ae1bb579-16f8-4ad3-9d60-decfb589e3ae).
Reason: The path specified cannot be used at this time. (Exception from HRESULT: 0x80070094)
Techinal Support Details:
System.Runtime.InteropServices.COMException (0x80070094): The path specified cannot be used at this time. (Exception from HRESULT: 0x80070094)
at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ApplyIisVirtualDirectorySettings(VirtualDirectory virtualDirectory, String path, AccessFlags accessFlags, String applicationName, String applicationPoolId, String scriptMaps)
at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisRootVirtualDirectory(WebSite webSite, String path, AccessFlags accessFlags, String applicationName, String applicationPoolId, String scriptMaps)
at Microsoft.SharePoint.Administration.SPProvisioningAssistant.ProvisionIisWebSite(String serverComment, String serverBindings, String secureBindings, AuthenticationMethods authenticationMethods, String authenticationProviders, String path, AccessFlags accessFlags, String applicationName, String applicationPoolId, String scriptMaps, String sslCertificateSubjectName)
at Microsoft.SharePoint.Administration.SPMetabaseManager.ProvisionIisWebSite(String serverComment, String serverBindings, String secureBindings, Int32 authenticationMethods, String authenticationProviders, String path, Int32 accessFlags, String applicationName, String applicationPoolId, String scriptMaps, String sslCertificateSubjectName)
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
Restart the WSS Timer service
the WSS Timer service leaks memory
The Content Deployment Settings are configured via Central Administration under Operations
- The site you deploy content to should use a separate content database from the source site.
- The site you deploy to must be initially created as a blank site.
- You can deploy content to sites with all relationships - ie: within a farm, between 2 web apps or between separate farms.
To set up content deployment between farms:
- Configure content deployment settings
- Enable content deployment jobs in Central Administration by setting CDS to Accept incoming content deployment jobs.
- Set the import & export servers
- Set the connection security to Do not require encryption
- Create a new blank site in the destination farm.
- Create a new Content Deployment Path
- Assign a name & description
- Select the source web application & site collection.
- Assign the URL for the destination Central Administration Server eg: http://dev01w2k3:11111
- Click on the Connect button.
- Select the desitination web application & site collection.
- Select whether you want to deploy user names & security information.
- Create a test one time deployment job
- Assign a name & description
- Select the content deployment path
- Specify whether the job should be site specific or accross an entire site collection.
- Leave the frequency & options as their default values.
- Click Ok.
- Run the one time test deployment job
- Open the One time deployment job drop down list and select Run Job.
- Refresh the page so that Running is displayed in the status column. Click on running to view the deployment process report page.
- If successful the status will change to Successful on completion.
- Schedule the Quick Deploy job
- Assign the frequency of the schedule.
- Check the quick deploy users.
- Set up notifiaction if required.
- Assign Quick Deploy content in the source website
- Go to your source website and edit a page.
- Publish your changes.
- From the Tools drop down list select Quick Deploy.
- The changes will be updated at the next scheduled job.
The webparts on MOSS bombed out yesterday morning with the following error message:
Web Part Error: One of the properties of the Web Part has an incorrect format. Windows Sharepoint Services cannot deserialize the Web Part. Check the format of the properties and try again.
The cause turned out to be the log files generated by MOSS which had increased in size to 5Gig and clogged up the c:drive
The log files are set up to be stored on the d:drive not the c:drive as are Indexes & Queries.
Each was originally configured as follows:
- Indexing: D:\MOSS\12.0\Data\Office Server\Applications
- Queries: D:\MOSS\12.0\Data\Office Server\Applications
Diagnostic Logging -
- Error Reports: Collect
- Event Throttling: Warnings / High
- Trace Log: 72 - 30
Usage Analysis Processing -
- Logging Settings: Enabled to create 1 log located at d:\MOSS\12.0\Logs\Usage
- Process Settings: Enabled between 10pm & 12am daily
This is still being investigated by reducing the amount & frequency of log files generated while monitoring the situation over the next 4 weeks