When installing the .NET 3.5 framework on a Windows 2003 SP2 x64 VPS I got these errors, using the web or full installer:
[09/19/10,11:07:29] XPSEPSC x64 Installer: [2] Error code 1603 for this component means "Fatal error during installation.
"
[09/19/10,11:07:29] XPSEPSC x64 Installer: [2] Setup Failed on component XPSEPSC x64 Installer
[09/19/10,11:07:30] WapUI: [2] DepCheck indicates XPSEPSC x64 Installer is not installed.
[09/19/10,11:14:54] XPSEPSC x64 Installer: [2] Error code 1603 for this component means "Fatal error during installation.
I also found the info: The installation of the XPSEPSC component requires that the Print Spooler Service be running in the "Started" state. If the Print Spooler Service is not running, the XPSEPSC installer will fail.
To install .NET 3.5 framework on a windows virtuozzo container, perform these steps for a successfull installation:
1 delete the C:\windows\system32\catroot\ folder
2 Start the print spooler service
3 Run the .NET 3.5 SP1 installer
Sonntag, 19. September 2010
Freitag, 13. August 2010
How to change the default search scope from "all sites" to "this site:xx"
By default SharePoint sites comes with a number of search scopes: People All Sites besides the implicit search scopes which change according to the context: This Site This List
The default search scope in the sharepoint is "All sites", but sometimes the client request "This site:xx" set as the default scope. Maybe some one will suggest to modify the setting directly via Sharepoint Designer. But only for one site, the solution is not problem. For more than 100 sites, how to deal with it?
In order to solve such problem, customing code should be added to the search feature file. The following lineShowDD_DefaultContextual should be added to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\FEATURES\OSearchEnhancedFeature\SearchArea.xml
and the file will be:
http://schemas.microsoft.com/sharepoint/"> /_layouts/images/gosearch.gif /_layouts/images/goRTL.gif /_layouts/images/gosearch.gif /_layouts/images/goRTL.gif true None true ShowDD_DefaultContextual
In order to avoid the Sharepoint Upgrade problem in the future, we suggest you to write a new feature for the change and deploy the feature to the site collection.
The default search scope in the sharepoint is "All sites", but sometimes the client request "This site:xx" set as the default scope. Maybe some one will suggest to modify the setting directly via Sharepoint Designer. But only for one site, the solution is not problem. For more than 100 sites, how to deal with it?
In order to solve such problem, customing code should be added to the search feature file. The following line
and the file will be:
In order to avoid the Sharepoint Upgrade problem in the future, we suggest you to write a new feature for the change and deploy the feature to the site collection.
Microsoft Visual Studio 2008 automatically generated setup.bat can't be fully trusted
last week we deployed a new webpart to the Qual-Server, and got the following error.
e:\Solutions\teamapps>setup.bat Validating the content of solution TeamApps.wsp ... Adding solution TeamApps.wsp to the SharePoint ... Operation completed successfully. Deploying solution TeamApps.wsp ... DeploymentFailedFileCopy : HAMA0690 : http://moss-qual..... / : MOSS-QUAL MOSS -Qual : Error: The web.config is invalid on this IIS Web Site: e:\WebSites\MOSS-QUAL Moss-Qu al\web.config. teamapps.wsp: Operation completed with errors. Activating feature TeamApps ... Feature 'f96bf563-74e9-4d41-a5f7-213f8983f2cd' is not installed in this farm, and can not be added to this scope. Hit enter key to quit.
It is very strange, as the webpart was deployed and tested successfully on our development server, intergration server, also test server. It seems that is no reasons to get such error.
The difference between T system and Q system is that Q system has two frondend server and T system is a single farm server. Before we used the setup script that we manuelly wrote, but this time we use the script that Visual studio automatically generated.
After we test a very simplest webpart "hello world", and found the automatically generated script had problem for multi-server farm. And we deployed the webpart with our simple script successfully.... The difference is that the
Mittwoch, 11. August 2010
Deployment: Failed to connect to an IPC Port: Access is denied.
Today I deployed a wsp file on a new machine, and got the following error info:
E:\wsps>stsadm -o deploysolution -name xxxxxCORE.wsp -immediate -allowGacDeployment -allowCasPolicies -url http://localhost:4712/
Timer job successfully created.
E:\wsps>stsadm -o execadmsvcjobs
Executing .Executing solution-deployment-xxxxxxcore.wsp-0.The solution-deployment-bdfkmcore.wsp-0 job completed successfully, but could not be properly cleaned up. This job may execute again on this server.Executing SharePoint Worker Process Group Update4c6b5f51-434a-4536-8699-4420fe5ca118.The SharePoint Worker Process Group Update4c6b5f51-434a-4536-8699-4420fe5ca118 job failed with the following error. This job will be skipped. Failed to connect to an IPC Port: Access is denied.
It seems that the SharePoint Service Timer has no access to run the task. Go to Compenonts Services--> Service(Local). I check the logon accout in the service timer property and found that the account is "network service", which has no access for our sharepoint system. When I change the logon to "Local system account " and restart the timer agian. Then I try to update the wsp again and it works prefect! The problem is resolved.
E:\wsps>stsadm -o deploysolution -name xxxxxCORE.wsp -immediate -allowGacDeployment -allowCasPolicies -url http://localhost:4712/
Timer job successfully created.
E:\wsps>stsadm -o execadmsvcjobs
Executing .Executing solution-deployment-xxxxxxcore.wsp-0.The solution-deployment-bdfkmcore.wsp-0 job completed successfully, but could not be properly cleaned up. This job may execute again on this server.Executing SharePoint Worker Process Group Update4c6b5f51-434a-4536-8699-4420fe5ca118.The SharePoint Worker Process Group Update4c6b5f51-434a-4536-8699-4420fe5ca118 job failed with the following error. This job will be skipped. Failed to connect to an IPC Port: Access is denied.
It seems that the SharePoint Service Timer has no access to run the task. Go to Compenonts Services--> Service(Local). I check the logon accout in the service timer property and found that the account is "network service", which has no access for our sharepoint system. When I change the logon to "Local system account " and restart the timer agian. Then I try to update the wsp again and it works prefect! The problem is resolved.
Abonnieren
Posts (Atom)