When you try to run the CU.exe file to upgrade your SP farm, you get the below message
The installation of this package failed
Solution:- The way it works is that you need to have the ca file also installed in the same folder where you have the EXE file. It looks for some content through that cab file and hence needed during the upgrade process.
Another way around is that you can run from a network directory.
Tuesday, November 25, 2014
microsoft.sharepoint.administration.spserver needs upgrade when you upgrade your SP farm
You get this message when you are trying to upgrade your SP farm by running the following command
stsadm.exe -o localupgradestatus
It displays the mess saying that upgrade required. Because there are still some features which did not get install, run the following command under bin directory
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Once done, refresh the page and upgrade status message should disappear.
stsadm.exe -o localupgradestatus
It displays the mess saying that upgrade required. Because there are still some features which did not get install, run the following command under bin directory
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures
Once done, refresh the page and upgrade status message should disappear.
Monday, November 17, 2014
How to extract files out of SharePoint service Packs and CU?
All,
when we are doing scripted SP installation, we are looking to have all files at one place so that we can update the SP with all updates in once. But .exe files doesnt get carry from the scripts.
Below is the command we run to extract the files and put in our CU updates folder.
1) Open cmd
2)
when we are doing scripted SP installation, we are looking to have all files at one place so that we can update the SP with all updates in once. But .exe files doesnt get carry from the scripts.
Below is the command we run to extract the files and put in our CU updates folder.
1) Open cmd
2)
"D:\Software\Office 2007\microsoft_office_suite_service_pack_2_x64.exe" /extract:"d:\updates\CUExtractFiles"
Thursday, November 13, 2014
How to configure Search from scratch in SharePoint 2010 farm?
This is for every SP person who is configuring search i the environment.
Here is a very excellent article on dng that and explainng all the components of the search.
http://sharepointgeorge.com/2010/configuring-enterprise-search-sharepoint-2010/
Here is a very excellent article on dng that and explainng all the components of the search.
http://sharepointgeorge.com/2010/configuring-enterprise-search-sharepoint-2010/
The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component ‘ ′ in search application ‘Search Service Application’ is in a good state and try again
There is an issue when you configure serach service application but do not see admini components running in search service administartion and you cannot go to content sources and any other parts of it.
Use below to fix the issue. there is very nice article on this:-
http://blogs.technet.com/b/poojk/archive/2011/11/28/sharepoint-2010-search-service-is-not-able-to-connect-to-administration-component-server.aspx
Run below PowerShell command:
$varInstance = Get-SPEnterpriseSearchServiceInstance -local (Assuming that you have only one SSA in farm)
If you type $varInstance and hit Enter key, you should see SharePoint Server Search instance details.
If you see it disabled then run another PS command -----> Start-SPEnterpriseSearchServiceInstance -Identity <servername>
Once above runs successfully, execute below:
$varSearchApp = get-spenterprisesearchserviceapplication
Now set search Admin component:
set-spenterprisesearchadministrationcomponent –searchapplication $varSearchApp –searchserviceinstance $varInstance
After it gets completed successfully, you need to wait for sometime, may be about 10 minutes.(It took 10 min in my case) Make sure you restart search service and then wait. Admin component should be ready and you should be able to browse SSA.
Use below to fix the issue. there is very nice article on this:-
http://blogs.technet.com/b/poojk/archive/2011/11/28/sharepoint-2010-search-service-is-not-able-to-connect-to-administration-component-server.aspx
Run below PowerShell command:
$varInstance = Get-SPEnterpriseSearchServiceInstance -local (Assuming that you have only one SSA in farm)
If you type $varInstance and hit Enter key, you should see SharePoint Server Search instance details.
If you see it disabled then run another PS command -----> Start-SPEnterpriseSearchServiceInstance -Identity <servername>
Once above runs successfully, execute below:
$varSearchApp = get-spenterprisesearchserviceapplication
Now set search Admin component:
set-spenterprisesearchadministrationcomponent –searchapplication $varSearchApp –searchserviceinstance $varInstance
After it gets completed successfully, you need to wait for sometime, may be about 10 minutes.(It took 10 min in my case) Make sure you restart search service and then wait. Admin component should be ready and you should be able to browse SSA.
Failed to retrieve RS configuration information: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException
This is the issue where you configure report server in SharePoint integrated mode and runs fine opening the web service url which shows that reports are configured properly. But you get into an issue when you try to use the web service url in CA and report server configuration settings.
1) Open Central admin adn go to general settings- report server configuration
2) Open the settings and add the web service url to the page and choose the trusted account (should be the same taht you user while configuring report server on Sql side) and click OK. It takes a while and then thorw the error "Failed to retrieve RS configuration information: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException"
To fix this, in our case it was related to our sql server side where port 80 was blocked and thats why SP was not able to make connection to the sql side.
Go to Sql server and open configuration manager- under report web service url- change the url to port 8080 or whatever you want and reconfigure again.Then once done, use that url and go back to CA and it should work
How you can check whether port is blocked. Use Telent client feature on your server
Open cmd and type:-
Telnet "ServerName" port
If it gets black out, it means port is open if not then its blocked and you will see a message.
1) Open Central admin adn go to general settings- report server configuration
2) Open the settings and add the web service url to the page and choose the trusted account (should be the same taht you user while configuring report server on Sql side) and click OK. It takes a while and then thorw the error "Failed to retrieve RS configuration information: System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException"
To fix this, in our case it was related to our sql server side where port 80 was blocked and thats why SP was not able to make connection to the sql side.
Go to Sql server and open configuration manager- under report web service url- change the url to port 8080 or whatever you want and reconfigure again.Then once done, use that url and go back to CA and it should work
How you can check whether port is blocked. Use Telent client feature on your server
Open cmd and type:-
Telnet "ServerName" port
If it gets black out, it means port is open if not then its blocked and you will see a message.
Subscribe to:
Posts (Atom)