Sonntag, 19. September 2010
.net Framework 3.5 won't install on Server 2003 SP2 x64
[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
Freitag, 13. August 2010
How to change the default search scope from "all sites" to "this site:xx"
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.
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.
Dienstag, 20. Oktober 2009
Sharepoint Server 2010 technical diagrams
- Services in SharePoint 2010 Products--Describes and illustrates the services architecture, including and common ways to deploy services in your overall solution design
- Cross-farm Services in SharePoint 2010 Products--Illustrates how to deploy services across farms to provide centralized administration of services.
- Topologies for SharePoint Server 2010--Describes common ways to build and scale farm topologies, including planning which servers to start services on.
- Hosting Environments in SharePoint 2010 Products--Summarizes the support for hosting environments and illustrates common hosting architectures.
- Business Connectivity Services Model--Microsoft Business Connectivity Services are a set of services and features in Microsoft SharePoint Server 2010 and Microsoft SharePoint Foundation 2010 that support integrating data from external systems into solutions based on Microsoft SharePoint Server and Microsoft SharePoint Foundation. This model poster describes the architecture of Microsoft Business Connectivity Services in SharePoint Server 2010 and provides information about how to create solutions that are based on the service.
Use this model with the following article: Business Connectivity Services overview (SharePoint Server 2010) - Microsoft SharePoint Server 2010 Upgrade Planning--This model covers planning for an upgrade from Microsoft Office SharePoint Server 2007 to SharePoint Server 2010. It includes information about the following:
Upgrade requirements: Hardware, operating system, and database
Upgrade process: specific steps to follow before, during, and after the upgrade
Use this model with the following article: Upgrading to SharePoint Server 2010 - Microsoft SharePoint Server 2010 Upgrade Approaches--This model helps you understand the in-place, database attach, and hybrid approaches to upgrading from Office SharePoint Server 2007 to SharePoint Server 2010.
See the farm topologies before, during, and after upgrade
Compare the advantages of each type of upgrade approach
Use this model with the following articles:
Determine upgrade approach (SharePoint Server 2010)
Upgrade process overview (SharePoint Server 2010) - Microsoft SharePoint Server 2010 — Test Your Upgrade Process--This model explains the methodology for testing the upgrade process before upgrading from Office SharePoint Server 2007 to SharePoint Server 2010.
Understand the goals for testing your upgrade process: customizations, hardware, timing, planning
See specific steps to follow for testing your upgrade process
Use this model with the following article: Use a trial upgrade to find potential issues (SharePoint Server 2010) - Microsoft SharePoint Server 2010 — Services Upgrade--This model covers upgrading services from Office SharePoint Server 2007 to SharePoint Server 2010.
Considerations for specific services: Personalization, Search, InfoPath Forms, Excel, Business Data Catalog, Single Sign-on
In-place upgrade with services
Database attach upgrade with services - Choose a tool for business intelligence in SharePoint Server 2010--Discusses the tools available for business intelligence
Montag, 19. Oktober 2009
Getting Started with SharePoint 2010
Microsoft SharePoint Server 2010 Evaluation Guide
You can download the guide here