Archive for April, 2014

PerformancePoint Unable to Create Report QueryProducedTooManyResults

Tuesday, April 29th, 2014
Issue Summary:
In SharePoint 2010, using PerformancePoint Dashboard Designer tool, you are trying to create report and it brings the following message:Unable to create report. Query produced too many results.
Contact the administrator for more details.

Event Viewer Errors on SharePoint App Server:

Error 1:
Log Name:      Application
Source:        Microsoft-SharePoint Products-PerformancePoint Service
Date:          2/4/2014 11:37:55 AM
Event ID:      1
Task Category: PerformancePoint Services
Level:         Error
Keywords:      
User:          DomainSPFarmAct
Computer:      SrvApp02.domain.com
Description:
An exception occurred while running a report.  The following details may help you to diagnose the problem:
Error Message: Error running data source query.
<br>
<br>
Contact the administrator for more details.
Dashboard Name: 
Dashboard Item name: 
Report Location: {6ed9a727-029b-1e22-d81a-f39274d4d9e2}
Request Duration: 300,564.30 ms
User: DomainBIDeveloper
Parameters: 
Exception Message: Error running data source query.
Inner Exception Message: 
Stack Trace:    at Microsoft.PerformancePoint.Scorecards.Server.PmServer.ExecuteAnalyticReportWithParameters(RepositoryLocation 
analyticReportViewLocation, BIDataContainer biDataContainer)
   at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.ExtractReportViewData()
   at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.CreateRenderedView(StringBuilder sd)
   at Microsoft.PerformancePoint.Scorecards.ServerRendering.NavigableControl.RenderControl(HtmlTextWriter writer)

PerformancePoint Services error code 20604.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-PerformancePoint Service” Guid=”{A7CD5295-CBBA-4DCA-8B67-D5BE061B6FAE}” />
    <EventID>1</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-04-18T16:37:55.171984000Z” />
    <EventRecordID>603586</EventRecordID>
    <Correlation ActivityID=”{43305F92-CD1F-4E75-B19B-2581FE7C04CD}” />
    <Execution ProcessID=”6420″ ThreadID=”6468″ />
    <Channel>Application</Channel>
    <Computer>SrvApp02.domain.com</Computer>
    <Security UserID=”S-1-5-41-1623458274-11437692956-399368559-1726″ />
  </System>
  <EventData>
    <Data Name=”string1″>An exception occurred while running a report.  The following details may help you to diagnose the problem:
Error Message: Error running data source query.
&lt;br&gt;
&lt;br&gt;
Contact the administrator for more details.
Dashboard Name: 
Dashboard Item name: 
Report Location: {6ed9a727-029b-1e22-d81a-f39274d4d9e2}
Request Duration: 300,564.30 ms
User: DomainBIDeveloper

Parameters: 
Exception Message: Error running data source query.
Inner Exception Message: 
Stack Trace:    at Microsoft.PerformancePoint.Scorecards.Server.PmServer.ExecuteAnalyticReportWithParameters(RepositoryLocation 

analyticReportViewLocation, BIDataContainer biDataContainer)
   at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.ExtractReportViewData()
   at Microsoft.PerformancePoint.Analytics.ServerRendering.OLAPBase.OlapViewBaseControl.CreateRenderedView(StringBuilder sd)
   at Microsoft.PerformancePoint.Scorecards.ServerRendering.NavigableControl.RenderControl(HtmlTextWriter writer)
PerformancePoint Services error code 20604.</Data>
  </EventData>
</Event>

Error 2:
Log Name:      Application
Source:        Microsoft-SharePoint Products-PerformancePoint Service
Date:          2/4/2014 11:37:55 AM
Event ID:      2
Task Category: PerformancePoint Services
Level:         Warning
Keywords:      
User:          DomainSPFarmAct
Computer:      SrvApp02.domain.com
Description:
Error running data source query.
XML for Analysis parser: The XML for Analysis request timed out before it was completed.

Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: XML for Analysis parser: The XML for Analysis request timed out before it was completed.
   at 
Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.ExecuteMultidimensional(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection parameters)
   at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteCellSet()
   at Microsoft.PerformancePoint.Scorecards.DataSourceProviders.AdomdDataSourceProvider.RunQueryInternal(String query, Boolean 
isCellSet, Int32 sessionTimeout)

PerformancePoint Services error code 10116.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-PerformancePoint Service” Guid=”{A7CD5295-CBBA-4DCA-8B67-D5BE061B6FAE}” />
    <EventID>2</EventID>
    <Version>14</Version>
    <Level>3</Level>
    <Task>1</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-04-18T16:37:55.156358900Z” />
    <EventRecordID>603585</EventRecordID>
    <Correlation ActivityID=”{43305F92-CD1F-4E75-B19B-2581FE7C04CD}” />
    <Execution ProcessID=”6420″ ThreadID=”6468″ />
    <Channel>Application</Channel>
    <Computer>SrvApp02.domain.com</Computer>
    <Security UserID=”S-1-5-21-1627688274-1190192956-3999157559-1626″ />
  </System>
  <EventData>
    <Data Name=”string1″>Error running data source query.
XML for Analysis parser: The XML for Analysis request timed out before it was completed.

Microsoft.AnalysisServices.AdomdClient.AdomdErrorResponseException: XML for Analysis parser: The XML for Analysis request timed out before it was completed.
   at 
Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.IExecuteProvider.Ex

ecuteMultidimensional(ICommandContentProvider contentProvider, AdomdPropertyCollection commandProperties, IDataParameterCollection 

parameters)
   at Microsoft.AnalysisServices.AdomdClient.AdomdCommand.ExecuteCellSet()
   at Microsoft.PerformancePoint.Scorecards.DataSourceProviders.AdomdDataSourceProvider.RunQueryInternal(String query, Boolean 
isCellSet, Int32 sessionTimeout)

PerformancePoint Services error code 10116.</Data>
  </EventData>
</Event>

Resolution:
I went to Central Admin > Manage Service Applications > PerformancePoint Service Application Settings and found these default settings.

There wasn’t any relevant setting. I then used Power shell commands.

Run this PowerShell Get command to see current values.
Get-SPPerformancePointServiceApplication -identity “PerformancePoint Service Application”

Then run following PowerShell to set a higher value for AnalyticQueryCellMax.
Set-SPPerformancePointServiceApplication -identity “PerformancePoint Service Application” -AnalyticQueryCellMax 10000000

References:
1. http://technet.microsoft.com/en-us/library/ee906547(v=office.14).aspx
2. http://social.technet.microsoft.com/Forums/en-US/3e676663-0d5f-4cbf-9694-14e82772c8e6/unable-to-create-report-query-produced-too-many-results?forum=ppsmonitoringandanalytics

MOSS MA Not Found error UserProfile Connection

Friday, April 25th, 2014
In SharePoint 2010, you want to setup User Profile Connection to Active Directory. You configure everything and click OK and it brings error message.

Issue Scenario:

  1. Go to SharePoint Central Administration website
  2. Click on ‘Manage Service Applications’ under Application Management
  3. Click on ‘User Profile Service Application’ or the name of your user profile service app
  4. On ‘Manage Profile Service’ page, click on ‘Configure Synchronization Connections’ under Synchronization section
  5. Click ‘Create New Connection’
  6. Enter the Connection Name, Forest Name, Account Name, Password, select OU levels under Containers section to sync profiles from that OU level
  7. Click OK to configure the connection

In this case, you will get error:

Error

MOSS MA Not Found
Troubleshoot Issues with Microsoft Sharepoint Foundation
Correlation ID: f8224450-ea42-742a-d8c6-5de674235e32

Date and Time: MM/DD/YYYY hh:mm:ss AM
Go back to site
MOSS MA Not Found Error
Finding the Correlation ID Error Details:
I had the following Codeplex tool deployed that helps in searching the ULS logs for the Correlation ID details. The tool is available under Central Administration website > Monitoring > Query correlation ID (under Logging section). You enter the Correlation ID from the error page, specify a date / time range and it shows the results.
That tool provided the following query result on its page. Looking at the query details, I saw the highlighted line. That section was telling that it could not connect to App Server 1 at port 5725. That server at this point was not configured for the User Profile Service. The service was setup on App Server 3.
Correlation Query Result:
Time Process Area Category Level EventID Message 
04/2/2014 10:14:38.90  w3wp.exe (SrvApp03:0x1C6C)  SharePoint Foundation  Logging Correlation Data  Medium xmnv Name=Request 
(POST:http://SrvApp03:19999/_layouts/EditDSServer.aspx?ApplicationID=abb4158a%2De70a%2D4185%2D86e2%2Df02f1c25966e) 
04/2/2014 10:14:38.90  w3wp.exe (SrvApp03:0x1C6C)  SharePoint Foundation  Logging Correlation Data  Medium xmnv Site=/ 
04/2/2014 10:14:39.97  w3wp.exe (SrvApp03:0x1C6C)  SharePoint Portal Server  User Profiles  High d3b3 LoadConnections failed trying to fill the connections list. Most likely during RetriveResources because of permissions — {1}. Available parameters: 
System.ServiceModel.EndpointNotFoundException: Could not connect to http://SrvApp01:5725/ResourceManagementService/MEX. TCP error code 10061: No connection could be made because the target machine actively refused it 10.1.0.103:5725. —> 

System.Net.WebException: Unable to connect to the remote server —> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 10.1.0.103:5725 at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, 

SocketAddress socketAddress) at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& 
… 
04/2/2014 10:14:39.97* w3wp.exe (SrvApp03:0x1C6C)  SharePoint Portal Server  User Profiles  High d3b3 …socket, IPAddress& address, 

ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception) — End of inner exception stack trace — 

at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context) at System.Net.HttpWebRequest.GetRequestStream() at 

System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream() — End of inner exception stack trace — Server 

stack trace: at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream() at 

System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout) at 

System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout) 

at System.ServiceModel.Channels.RequestChannel.Req… 
04/2/2014 10:14:39.97* w3wp.exe (SrvApp03:0x1C6C)  SharePoint Portal Server  User Profiles  High d3b3 …uest(Message message, 

TimeSpan timeout) at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout) at 

System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, 

Object[] outs, TimeSpan timeout) at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, 

ProxyOperationRuntime operation) at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message) Exception rethrown at 

[0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at 

System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at 

System.ServiceModel.Description.IMetad… 
04/2/2014 10:14:39.97* w3wp.exe (SrvApp03:0x1C6C)  SharePoint Portal Server  User Profiles  High d3b3 …ataExchange.Get(Message 

request) at Microsoft.ResourceManagement.WebServices.MetadataClient.Get(String dialect, String identifier) at 

Microsoft.ResourceManagement.WebServices.Client.ResourceManagementClient.SchemaManagerImplementation.RefreshSchema() at 

Microsoft.ResourceManagement.WebServices.ResourceManager.get_SchemaManager() at 

Microsoft.ResourceManagement.WebServices.ResourceManager..ctor(String typeName, LocaleAwareClientHelper localePreferences, 

ContextualSecurityToken securityToken) at Microsoft.Office.Server.UserProfiles.ConnectionManager.LoadConnections(Boolean fForUI) . 
04/2/2014 10:14:39.97  w3wp.exe (SrvApp03:0x1C6C)  SharePoint Portal Server  User Profiles  High a3xu 

ConnectionManager.LoadConnections(): Could not find MOSS MA despite being marked as fully configured, was it deleted? 
04/2/2014 10:14:40.09  w3wp.exe (SrvApp03:0x1C6C)  SharePoint Foundation  Monitoring  Medium b4ly Leaving Monitored Scope (Request 

(POST:http://SrvApp03:8000/_layouts/EditDSServer.aspx?ApplicationID=abb4158a%2De70a%2D4185%2D86e2%2Df02f1c25966e)). Execution Time=1193.10918007736 
Correlation Query Tool’s Result based on Correlation ID Error
Troubleshooting and Resolution:
  1. Looking at the query results, I saw that connection was trying to connect to first server and connection was refused. That server has been having issues and was already planned for removal from the farm. It was not running the User Profile Service.
  2. I then looked at the ‘Manage Servers in the Farm‘ page in SharePoint Central Administration > System Settings. I looked for ‘User Profile‘ service on that page to confirm which servers in the farm are running that service. It was not configured on App Server 1. I then went to ‘Manage Service Applications‘ page under Application Management in Central Administration Website. 
    SharePoint Manage Service Applications Page – Properties icon grayed out 

     Hover over the ‘User Profile Service Application‘, don’t click on the name but click on the right side of it. That will select the service application and activate the Operations Ribbon group on top. 

    SharePoint Manage Service Applications Page – Properties icon active

     

  3. Click on Properties icon in the SharePoint ribbon. That will bring the ‘Edit User Profile Service Application‘ dialog box. Scroll to the lower half of page and look under ‘Profile Synchronization Instance‘ field. It is fourth field from the bottom. In my case, it was set to the App Server 1. I changed it to the server that was actively running User Profile Service and clicked OK at the bottom.
    SharePoint – User Profile Service Application – Profile Synchronization Instance – Old Server

     

  4. Message was displayed saying ‘Profile Service Application successfully updated.’ Click ok on that dialog box to close it.
  5. I tried to configure the Profile Synchronization Connection again (Steps in Issue Scenario section above). Same error happened. I looked at the ‘Profile Synchronization Instance’ field (step 3 above), the same old App Server 1 was listed there. Not good.
  6. I started the ‘User Profile Service’ on that old App Server 1 from the Central Administration > ‘Manage Services on Server’ page for App Server 1.
    Sharepoint – Started User Profile Service from Manage Services on Server page

      

  7. I then changed the server under ‘Profile Synchronization Instance‘ to a new server that was running the User Profile Service. This time the setting stayed permanently and didn’t revert back as in last attempt.
    SharePoint – User Profile Service Application – Profile Synchronization Instance – Active Server

      

  8. I tried to configure user profile sync again. (Steps in Issue Scenario section above). It was successful this time.
Important Thing:
One important thing. I didn’t have to start the ‘Forefront Identity Manager Service‘ on the old server using Windows Services console. That service was in disabled state as before. After successfull Sync connection, I then stopped the ‘User Profile Service‘ on the App Server 1 that was started in step 6 above. I used SharePoint Central Administration website. It is not recommended to start / stop FIM service using  Windows Services console.

Sharepoint – Forefront Identity Manager Service (part of User Profile Service App) in Windows Services Console

References:
1. http://blogs.msdn.com/b/sofocle/archive/2011/06/28/user-profile-syncronization-failure-quot-moss-ma-not-found-quot.aspx
2. http://manojviduranga.wordpress.com/2013/05/18/moss-ma-not-found-when-creating-a-new-connection-to-aduser-profile-synchronization-in-sharepoint-2010/
3. http://mohamedelkassas.wordpress.com/2013/03/15/moss-ma-not-found-user-profile-syncronization-failure/
4. http://social.technet.microsoft.com/Forums/sharepoint/en-US/cf35f233-c6a9-440a-aa61-8be190782fcc/user-profile-synchronization-error-moss-ma-not-found
5. http://social.msdn.microsoft.com/Forums/en-US/81684a0f-30a0-4a29-b433-54e382666f47/user-profile-services-sync-connection-disappearing-after-a-few-days-moss-ma-not-found?forum=sharepointadminprevious

Database is too new and is not supported

Friday, April 11th, 2014
Issue Summary:
—————
In SharePoint Central Administration  > Upgrade and Migration > Database Status page, ProjectServer_Published DB is showing the status as “Database is too new and is not supported“.

Sometime ‘new’ is not good :o)

The farm had SP2 + August Cumulative Update applied to it.

‘Database is too new and is not supported’ status message
PWA Site Error:
The end user when go to Project Web Access (PWA) site get 503 – Service Unavailable error on page. Looking at the IIS Application Pool for PWA, you will see it is stopped. Even if you start, it will disable after sometime.
Server Side Event Viewer Errors:

Event Viewer Error 1:
In Application log of Event Viewer on Project Server Application server, following error is reported every minute:

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          1/10/2014 12:33:18 PM
Event ID:      3759
Task Category: Database
Level:         Error
Keywords:      
User:          CompanyDomainSPFarmAct
Computer:      AppServer1.CompanyDomain.com
Description:
Database ‘ProjectServer_Published’ on SQL Server instance ‘SQLDBServer1’ is not empty and does not match current database schema.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-SharePoint Foundation” Guid=”{E0CD6FB7-56E7-48DD-997A-

2413743931FT7}” />
    <EventID>3759</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>3</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T17:33:18.835143500Z” />
    <EventRecordID>596174</EventRecordID>
    <Correlation />
    <Execution ProcessID=”5448″ ThreadID=”3644″ />
    <Channel>Application</Channel>
    <Computer>AppServer1.CompanyDomain.com</Computer>
    <Security UserID=”S-1-5-21-1627799274-1190182956-3998267559-1676″ />
  </System>
  <EventData>
    <Data Name=”string0″>ProjectServer_Published</Data>
    <Data Name=”string1″>SQLDBServer1</Data>
  </EventData>
</Event>

Event ID 3759

Event Viewer Error 2
Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          1/10/2014 11:41:25 AM
Event ID:      5586
Task Category: Database
Level:         Error
Keywords:      
User:          CompanyDomainSPFarmAct
Computer:      AppServer1.CompanyDomain.com
Description:
Unknown SQL Exception 0 occurred. Additional error information from SQL Server is included below.

Cannot generate SSPI context.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-SharePoint Foundation” Guid=”{6FB7E0CD-52E7-47DD-997A-

241563931FC2}” />
    <EventID>5586</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>3</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T16:41:25.298131300Z” />
    <EventRecordID>596117</EventRecordID>
    <Correlation />
    <Execution ProcessID=”3664″ ThreadID=”7240″ />
    <Channel>Application</Channel>
    <Computer>AppServer1.CompanyDomain.com</Computer>
    <Security UserID=”S-1-5-21-1627799274-1180182956-3999268559-1629″ />
  </System>
  <EventData>
    <Data Name=”int0″>0</Data>
    <Data Name=”string1″>Cannot generate SSPI context.</Data>
  </EventData>
</Event>

Event ID 5586

Event Viewer Error 1 on AppServer 2

Log Name:      Application
Source:        Microsoft-SharePoint Products-Project Server
Date:          1/10/2014 12:47:07 PM
Event ID:      7761
Task Category: Queue
Level:         Error
Keywords:      
User:          CompanyDomainSPFarmAct
Computer:      AppServer2.CompanyDomain.com
Description:
Standard Information:PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)
An unxpected exception occurred in the Project Server Queue. Queue type (Project Queue/Timesheet Queue): 

ProjectQ. Exception details: PeriodicTasks failed.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-SharePoint Products-Project Server” Guid=”{B2178104-1B5B-4C20-8C8F-

960678CED9E5}” />
    <EventID>7761</EventID>
    <Version>14</Version>
    <Level>2</Level>
    <Task>21</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T17:47:07.776616700Z” />
    <EventRecordID>2026034</EventRecordID>
    <Correlation ActivityID=”{111A6951-5B30-454E-828C-73CC48CBD72A}” />
    <Execution ProcessID=”10012″ ThreadID=”1228″ />
    <Channel>Application</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security UserID=”S-1-5-21-1627799274-1180182956-3999268559-1629″ />
  </System>
  <EventData>
    <Data Name=”string0″>PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)</Data>
    <Data Name=”string1″>ProjectQ</Data>
    <Data Name=”string2″>PeriodicTasks failed</Data>
  </EventData>
</Event>

Event ID 7761
Event Viewer Error 2 on AppServer 2
Log Name:      Application
Source:        Microsoft-SharePoint Products-Project Server
Date:          1/10/2014 12:47:07 PM
Event ID:      7758
Task Category: Queue
Level:         Critical
Keywords:      
User:          CompanyDomainSPFarmAct
Computer:      AppServer2.CompanyDomain.com
Description:
Standard Information:PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)
Queue SQL call failed. Error: System.Data.SqlClient.SqlException: Invalid object name 

‘MSP_QUEUE_RENDEZVOUS’.
Invalid object name ‘dbo.MSP_QUEUE_RENDEZVOUS’.
Invalid object name ‘dbo.MSP_QUEUE_RENDEZVOUS’.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader 

dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, 

String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, 

Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureReturnVal(String 

storedProcedureName, SqlParameter[] parameters)
   at Microsoft.Office.Project.Server.DataAccessLayer.QueueDal.PeriodicTasks(String prefix, Guid 

ServerUID, String machineName, String serviceName, Int32 queueId, Int32 TimeOut, Int32 recoverPriority, 

Nullable1 sendIncompleteTimeOut)
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Exe

cute()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{B2178104-1B5B-4C20-8C8F-

960678CED9E5}" />
    <EventID>7758</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>21</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-10T17:47:07.776616700Z" />
    <EventRecordID>2026033</EventRecordID>
    <Correlation ActivityID="{111A6951-5B30-454E-828C-73CC48CBD72A}" />
    <Execution ProcessID="10012" ThreadID="1228" />
    <Channel>Application</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security UserID="S-1-5-21-1627799274-1180182956-3999268559-1629" />
  </System>
  <EventData>
    <Data Name="string0">PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)</Data>
    <Data Name="string1">System.Data.SqlClient.SqlException: Invalid object name 'MSP_QUEUE_RENDEZVOUS'.
Invalid object name 'dbo.MSP_QUEUE_RENDEZVOUS'.
Invalid object name 'dbo.MSP_QUEUE_RENDEZVOUS'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader 

dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, 

String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, 

Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureReturnVal(String 

storedProcedureName, SqlParameter[] parameters)
   at Microsoft.Office.Project.Server.DataAccessLayer.QueueDal.PeriodicTasks(String prefix, Guid 

ServerUID, String machineName, String serviceName, Int32 queueId, Int32 TimeOut, Int32 recoverPriority, 

Nullable1 sendIncompleteTimeOut)
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Exe

cute()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()</Data>
  </EventData>
</Event>
Event Viewer Error 3 on AppServer 2
Log Name:      Application
Source:        Microsoft-SharePoint Products-Project Server
Date:          1/10/2014 12:46:02 PM
Event ID:      7754
Task Category: Queue
Level:         Critical
Keywords:      
User:          CompanyDomainSPFarmAct
Computer:      AppServer2.CompanyDomain.com
Description:
Standard Information:PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)
Queue unable to interact with SQL. Queue type (Project Queue, Timesheet Queue etc): ProjectQ Exception: 

Microsoft.Office.Project.Server.BusinessLayer.Queue.QueueSqlException: PeriodicTasks failed —> 

System.Data.SqlClient.SqlException: Invalid object name ‘MSP_QUEUE_RENDEZVOUS’.
Invalid object name ‘dbo.MSP_QUEUE_RENDEZVOUS’.
Invalid object name ‘dbo.MSP_QUEUE_RENDEZVOUS’.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader 

dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, 

String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, 

Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureReturnVal(String 

storedProcedureName, SqlParameter[] parameters)
   at Microsoft.Office.Project.Server.DataAccessLayer.QueueDal.PeriodicTasks(String prefix, Guid 

ServerUID, String machineName, String serviceName, Int32 queueId, Int32 TimeOut, Int32 recoverPriority, 

Nullable1 sendIncompleteTimeOut)
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Exe

cute()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()
   --- End of inner exception stack trace ---
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Per

iodicTasksRetry(Guid serverUID, String machineName, String serviceName, Int32 queueId, Int32 timeOut, 

Int32 recoverPriority, Nullable1 sendIncompleteTimeOut)
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.PeriodicTasks(Guid serverUID, 

String machineName, String serviceName, QueueID queueId, Int32 timeOut, QueueMsgPriority recoverPriority, 

Nullable1 sendIncompleteTimeout)
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.Receiver.PeriodicTasks()
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.Receiver.ThreadEntry()
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-Project Server" Guid="{B2289104-1A7B-4C80-8C8F-

960357WED9E5}" />
    <EventID>7754</EventID>
    <Version>14</Version>
    <Level>1</Level>
    <Task>21</Task>
    <Opcode>0</Opcode>
    <Keywords>0x4000000000000000</Keywords>
    <TimeCreated SystemTime="2014-01-10T17:46:02.761407800Z" />
    <EventRecordID>2026032</EventRecordID>
    <Correlation ActivityID="{111A6951-5B30-454E-828C-73CC48CBD72A}" />
    <Execution ProcessID="10012" ThreadID="1228" />
    <Channel>Application</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security UserID="S-1-5-21-1627799274-1180182956-3999268559-1629" />
  </System>
  <EventData>
    <Data Name="string0">PSI Entry Point: 
Project User: CompanyDomainSPFarmAct
Correlation Id: f9863c76-c68f-4764-b51e-ad01dd237dd7
PWA Site URL: http://PS.CompanyDomain.com/PWA
SSP Name: Project Server Service Application
PSError: NoError (0)</Data>
    <Data Name="string1">ProjectQ</Data>
    <Data Name="string2">Microsoft.Office.Project.Server.BusinessLayer.Queue.QueueSqlException: 

PeriodicTasks failed ---&gt; System.Data.SqlClient.SqlException: Invalid object name 

'MSP_QUEUE_RENDEZVOUS'.
Invalid object name 'dbo.MSP_QUEUE_RENDEZVOUS'.
Invalid object name 'dbo.MSP_QUEUE_RENDEZVOUS'.
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader 

dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, 

String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior 

runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, 

Boolean sendToPipe)
   at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
   at Microsoft.Office.Project.Server.DataAccessLayer.DAL.SubDal.ExecuteStoredProcedureReturnVal(String 

storedProcedureName, SqlParameter[] parameters)
   at Microsoft.Office.Project.Server.DataAccessLayer.QueueDal.PeriodicTasks(String prefix, Guid 

ServerUID, String machineName, String serviceName, Int32 queueId, Int32 TimeOut, Int32 recoverPriority, 

Nullable1 sendIncompleteTimeOut)
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Exe

cute()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()
   — End of inner exception stack trace —
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.RetryableSqlCallBase.Exe

cuteRetryableSqlCall()
   at 

Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.SqlCallRetry.PeriodicTasksSqlCall.Per

iodicTasksRetry(Guid serverUID, String machineName, String serviceName, Int32 queueId, Int32 timeOut, 

Int32 recoverPriority, Nullable1 sendIncompleteTimeOut)
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.BaseQueueAccess.PeriodicTasks(Guid serverUID, 

String machineName, String serviceName, QueueID queueId, Int32 timeOut, QueueMsgPriority recoverPriority, 

Nullable1 sendIncompleteTimeout)
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.Receiver.PeriodicTasks()
   at Microsoft.Office.Project.Server.BusinessLayer.Queue.Receiver.ThreadEntry()</Data>
  </EventData>
</Event>
Event Viewer System Error 4 on AppServer 2
Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          1/10/2014 11:19:16 AM
Event ID:      5059
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      AppServer2.CompanyDomain.com
Description:
Application pool SharePoint – PS.CompanyDomain.com80 has been disabled. Windows Process Activation 

Service (WAS) encountered a failure when it started a worker process to serve the application pool.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-Windows-WAS” Guid=”{524B5D04-133C-4A62-8362-64E8EDB9CE40}” 

EventSourceName=”WAS” />
    <EventID Qualifiers=”49152″>5059</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T16:19:16.000000000Z” />
    <EventRecordID>132221</EventRecordID>
    <Correlation />
    <Execution ProcessID=”0″ ThreadID=”0″ />
    <Channel>System</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name=”AppPoolID”>SharePoint – PS.CompanyDomain.com80</Data>
    <Binary>
    </Binary>
  </EventData>
</Event>
Event ID 5059

Event Viewer System Error 5 on AppServer 2:
Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          1/10/2014 11:19:16 AM
Event ID:      5057
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      AppServer2.CompanyDomain.com
Description:
Application pool SharePoint – PS.CompanyDomain.com80 has been disabled. Windows Process Activation 

Service (WAS) did not create a worker process to serve the application pool because the application pool 

identity is invalid.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-Windows-WAS” Guid=”{524B5D04-133C-4A62-8362-64E8EDB9CE40}” 

EventSourceName=”WAS” />
    <EventID Qualifiers=”32768″>5057</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T16:19:16.000000000Z” />
    <EventRecordID>132220</EventRecordID>
    <Correlation />
    <Execution ProcessID=”0″ ThreadID=”0″ />
    <Channel>System</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name=”AppPoolID”>SharePoint – PS.CompanyDomain.com80</Data>
    <Binary>
    </Binary>
  </EventData>
</Event>

Event ID 5057

Event Viewer System Error 6 on AppServer 2:
Log Name:      System
Source:        Microsoft-Windows-WAS
Date:          1/10/2014 11:19:16 AM
Event ID:      5021
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      AppServer2.CompanyDomain.com
Description:
The identity of application pool SharePoint – PS.CompanyDomain.com80 is invalid. The user name or 

password that is specified for the identity may be incorrect, or the user may not have batch logon 

rights. If the identity is not corrected, the application pool will be disabled when the application pool 

receives its first request.  If batch logon rights are causing the problem, the identity in the IIS 

configuration store must be changed after rights have been granted before Windows Process Activation 

Service (WAS) can retry the logon. If the identity remains invalid after the first request for the 

application pool is processed, the application pool will be disabled. The data field contains the error 

number.
Event Xml:
<Event xmlns=”http://schemas.microsoft.com/win/2004/08/events/event”>
  <System>
    <Provider Name=”Microsoft-Windows-WAS” Guid=”{524B5D04-133C-4A62-8362-64E8EDB9CE40}” 

EventSourceName=”WAS” />
    <EventID Qualifiers=”32768″>5021</EventID>
    <Version>0</Version>
    <Level>3</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime=”2014-01-10T16:19:16.000000000Z” />
    <EventRecordID>132219</EventRecordID>
    <Correlation />
    <Execution ProcessID=”0″ ThreadID=”0″ />
    <Channel>System</Channel>
    <Computer>AppServer2.CompanyDomain.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name=”AppPoolID”>SharePoint – PS.CompanyDomain.com80</Data>
    <Binary>75070780</Binary>
  </EventData>
</Event>

Event ID 5021

Resolution:
The Sharepoint / Project Server farm had SP2 and August 2013 Cumulative Update.

A quick run of the following SQL statement against ProjectServer_Published database verified its schema version.

select * from versions

ProjectServer_Published Database Schema in SQL Server

I then created a SQL update query to update the schema version of last row under ProjectServer_Published database – above screenshot. I changed the version from 14.2.151.0 to 14.1.653.0.

SQL Update Statement:

select * from Versions 
where VersionId = ‘AE40B1C1-23C6-4FA5-95D0-29FD61DDB2DA’
— Change from current version 14.2.151.0 to version 14.1.653.0

/* 
— Make sure to backup your databases and farm before modifying SQL tables.
update Versions
set Version = ‘14.1.653.0’
where VersionId = ‘AE40B1C1-23C6-4FA5-95D0-29FD61DDB2DA’
*/

ProjectServer_Published Database Schema in SQL Server before change – SQL Update statement above

After changing the schema version in database, I ran the following SharePoint command.
psconfig -cmd upgrade -inplace b2b  -wait -force

Sharepoint PSConfig Upgrade Force command status

At this point looking at the schema version in the ProjectServer_Published database’s Versions table showed new updated version. See below screenshot.

ProjectServer_Published Database Schema in SQL Server after manual change and PSConfig

Now looking at the SharePoint Central Administration  > Upgrade and Migration > Database Status page, I found that the database was showing as ‘No Action Required‘ – the target achieved.

ProjectServer_Published database with ‘No Action Required’ status

References:

  1. http://blogs.msdn.com/b/projectengineeringde/archive/2013/09/16/patchen-august-2013-cu-amp-sp2-beim-project-server-2010.aspx
  2. http://blogs.technet.com/b/projectsupport/archive/2013/09/12/project-server-2010-service-pack2-and-august-2013-cumulative-update-installation-issues.aspx
  3. http://blogs.msdn.com/b/projectengineeringde/archive/2013/09/16/patchen-august-2013-cu-amp-sp2-beim-project-server-2010.aspx

Adding new SharePoint ProjectServer to Farm Issue

Friday, April 11th, 2014
Scenario:

SharePoint 2010 farm with multiple servers in web and App layer. You want to add a new Web server for Microsoft SharePoint / Microsoft Project Server, and SharePoint Configuration fails on the new server. The farm has been running Sharepoint 2010, MS Project Server 2010, Office Web Apps and Language Packs. 
Error Message:
SharePoint Products Configuration Wizard brings the following message after you select the SQL Database server and then the SharePoint Farm Configuration DB.
Server Farm Products and Patch Status
The following SharePoint Technologies based products and patches were detected on your server farm.

Error:
Some farm products and patches were not detected on this or other servers. If products or patches are missing locally, you must quit this program and install the required products and patches on this server before restarting the wizard. If products or patches are missing on other servers, you must install the required products and patches on the specific servers, and you may then click the Refresh button to perform the status check again.

Scroll down the list and you will see other updates as missing as well. In my case it listed the following updates as missing on three existing servers and the new server.
Server Farm Products Status
——————————————————–
1. Microsoft Word Server
———————
HotFix for Sharepoint Server 2010 x64    Missing on SPServer01, 02 and 03
KB2825949
Security Update for Sharepoint 2010        Missing Locally [SPServer07new]
KB2837577
2. Excel Services Components
————————–
Hotfix for Sharepoint 2010 x64              Missing on SPServer01, 02 and 03
KB2825949
Security Update for Ms Sharepoint X64 Missing Locally [SPServer07new]
KB2826029
3. Access Services
——————–
Hotfix for Sharepoint 2010 x64 Missing on SPServer01, 02 and 03
KB2825949
Security Update for 2010 MS Business Missing Locally [SPServer07new]
Productivity Servers
KB2553298
The error listed basically the MS KB 2825949 patch as missing on all existing servers. That error was misleading. That patch was existed on existing servers.
I then looked for the three patches on local server – i.e the new server. The local server was missing these updates:
The new server is missing three MS KB updates.
a. KB2826029 – Excel Services Update
b. KB2553298 – Access Services / MS Business Productivity Update
c. KB2837577 – Word Automation Service Update
I went to Microsoft Knowledge base (KB) article page for KB 2826029 – Excel Services Patch to begin with. http://support.microsoft.com/kb/2826029
There wasn’t a patch download link on that KB article. I went to the IT Professional page link on that KB article and that took me to http://technet.microsoft.com/security/bulletin/MS13-084. Under ‘Affected and Non-Affected Software’ section, click the link for the SharePoint 2010 server SP2 related links. There are links for WSS, Excel Services, Word Automation. In our case the missing update KB number matches the Excel update 2826029. I downloaded and installed the Excel update. The same way I found the other two patches.
KB2826029 – Excel Services Patch – Download Link
KB2553298 – Access / Business Productivity – Download Link
KB2837577 – Word Automation Service – Download Link
I re-ran the Sharepoint Configuration wizard and it completed successfully. New Server was now part of the farm. 
Final Conclusion:
In my case, it was key to pay attention to ‘Missing Locally’ patches in the error screen. I confirmed the missing patches on new server by using Control Panel > Uninstall a Program > View Installed Updates section.
Some blogs suggest running following command to fix the issue. In my case, those smaller patches were indeed missing.
Get-SPProduct –local
psconfig -cmd installcheck -noinstallcheck
psconfig -cmd upgrade -inplace b2b -force -cmd -installcheck -noinstallcheck

Sharepoint Document Management Best Practices

Tuesday, April 8th, 2014

Sharepoint like any document management system, has best practices that needs to be followed to get maximum value out of the system. A planned roll out of document management features helps the organization and users. A planned roll out should have some sort of discipline (Plan, Do, Check, Act) around it. In an unplanned roll out you will come across discipline (Do, check, plan, act) that cause more pain. So, what are the “benefits of planned Sharepoint roll out” :

1.      With planning, staff knows what is coming and when
2.      You select the features that best fit into the organization in the beginning. It might be difficult to change user behavior of how they work in the systems later if you started with rudimentary features and process
3.      Users might use a Sharepoint library just like a network shared drive to dump files. Versus organizing a library with columns, content types or term store features might go long way
4.      Same department contents structured using right rights features might save lot of time and hence the cost (full time employees are not free, everyone has a cost associated)
5.      Structured information will help the team leads / Management make quick and intelligent decisions in short time
Now, what are some of the“common best practices around Sharepoint Document Management”?
There are no hard and fast rules. Every situation and roll out might require different combination of features. Below I’ve listed some of the ‘”common best practices for Sharepoint”. This list by no mean is complete and there might be additional best practices needed around different department contents. Use this list as a reference and come up with your plan.
1.      Use short Site, Library and List names
Don’t use long names in Sites, Libraries and lists in Sharepoint. Avoid having space in names. Like instead of ‘Billing Department’use BD or Billing. Another example for site name se short name like AECinstead of An Excellent Company. Create sites, libraries and list with short names. Once created go the Title configuration areas to change to long title and add text in the description field. Creating those items with shot names conserves the URL address space.
2.      255 Characters URL Limit and Windows file / folder path Limits
There is a limit of characters in the URL address as part of web standard. It is 255 characters. Using long site, library, folders, files path can lead to situation where that limit might be reached. In Sharepoint that could cause some hard stop. Few examples could be users not able to edit files even with right permissions, previous versions of file not working etc.
References:
a.       URL path length restrictions (SharePoint Server 2010)
b.      You receive a “The specified file or folder name is too long” error message when you create a new folder or a new document in a document library in SharePoint Portal Server or in Windows SharePoint Services
c.       A webpage that has a long URL may not print to a network printer in Internet Explorer 9
d.      You cannot delete long URLs from the browsing history in Internet Explorer on a computer that is running Windows 7 or Windows Server 2008 R2
e.      Maximum URL length is 2,083 characters in Internet Explorer
3.      Avoid Using Special Characters in File, Folders , Library and Site names
Special characters cause special problems. To make a file / folder on the top of the list, use Sharepoint views, filters and sorts option. If you really need to make something on top of the list manually, use period (.) or underscore (_) in the beginning of the name. But it is better to use simple names.
Reference:
Information about the characters that you cannot use in site names, folder names, and file
names in SharePoint
4.      Avoid Using Spaces in Names and avoid having space in beginning
If you need to use two words in names, avoid space in the middle. That one space takes three character (i.e. %20) in the URL address. For example use BestDocument instead of Best Document. You can use underscore (_) in the middle of two words without adding spaces. In same example that will look like Best_Document.
5.      Don’t add version number of file at the end of name
It is a common scenario users do on network shared drives. Don’t use the same practice in a content management system like Sharepoint. Instead turn on the versioning feature at the library or list level and use it to your advantage. Let the Sharepoint do its job of maintaining versions. Add those versioning columns in the view for users. On the side note, when you turn on the versioning feature don’t turn on unlimited versions, set a limit on the last number of versions to keep. For example 5 or 10 [Sharepoint site Admin can setup versioning for libraries and lists.].
6.      Use Metadata instead of Folders
Metadata is much better way of working with contents compared to organizing contents in folders. Using Columns, Content Types, Metadata Term store feature of Sharepoint are recommend ways.
Reference:
a.       SharePoint 2013 Best Practices: Using Folders [same concepts can apply to other Sharepoint editions]
7.      Don’t use long folder names
I’ve seen examples where people used kind of whole history of the folder as part of folder name. For  example “A Long Company Name, Contract Number, Customer Number, Customer Location” as part of folder name. Compare it to having a folder with just the short company name  ABC Company and using rest of the information as part of the metadata properties at file level to classify contents is much better and faster approach. You will run into long URL issues if you will have hierarchical chain of folders with longs names and long filenames inside those folders.
Just like people don’t use long names. They use first and last name or maybe middle name. But people don’t add their grandfather, great grandfather and whole ancestral names as part of their name. Another example, book writers don’t add the full summary of the book on the title. It is usually in next few pages.
8.      Think Before you Act
Always think and plan before you would like to do any important thing in Sharepoint. Try to get your information organized from the beginning. Unplanned start can cause you lots of rework later that might take twice or thrice the efforts and costs. It is like plan and pay early and save a lot later versus do it without planning and keep paying forever.
9.      Use Site, Library, List Templates
Sharepoint comes with lots of templates for sites, libraries and lists. You can create a customized site, library or list using out of the box features and then save it as template. Those template can then be used later by other department and team. Thus saving lots of time and efforts later.
10.  Know you Sharepoint Document Management features
Sharepoint offers lots of features for document management that help in different scenarios. Content Types, Content Organizer Rule, Documents Sets, DocumentID, workflows and others are some of the advanced features that can bring value to your contents. Know what you have at your disposal, before users start using your libraries.
Summary
Below are the “Best Pracices for Sharepooint Document Management“.
1. Use short Site, Library and List names
2. 255 Characters URL Limit and Windows file / folder path Limits
3. Avoid Using Special Characters in File, Folders , Library and Site names
4. Avoid Using Spaces in Names and avoid having space in beginning
5. Don’t add version number of file at the end of name
6. Use Metadata instead of Folders
7. Don’t use long folder names
8. Think Before you Act
9. Use Site, Library, List Templates
10. Know you Sharepoint Document Management features

Softvative Sharepoint Brainstorming Plan V1.1

Tuesday, April 8th, 2014

On almost every major project, as the 3P Manager (one of the P being Project / Program / Portfolio), you come across different methodologies, standards and frameworks. Some departments / teams on the project require PMI, others may be talking about Agile, then comes the ITIL practices, SDLC, Security and compliance or GRC process and so on.

To simplify and consolidate the key aspects of any project, besides other project plans, I came up with my Brainstorming Plan Template – one page document to show the key pieces of project information. In my initial template, I used four key areas for a successful application / systems. Those were Availability, Reliability, Security and Performance. Over period of time, I added architecture, migration, licensing and custom development as other key areas into my template. I used that brainstorming plan successfully on different type of projects. In fact, I made it as requirement for every major project initiative at one of the company where I was managing their IT Project Portfolio. I used it for Office Move, Active Directory / Exchange upgrade, Storage or network upgrades, DataCenter Relocation and others. I’ve been using it for almost every Microsoft Sharepoint roll.

I’ve created a Sharepoint Brainstorming Template that covers all the key aspects of a successful Sharepoint roll out. I’m sharing that SharePoint Brainstorming Plan. Some project may require migrations, others might require custom development, another one might involve integration with Microsoft Project Server EPM / PPM, Microsoft Dynamics (CRM, AX etc), or may be Yammer or FAST Search. Based on your project, you can pick and choose the nodes and refine it.

The Sharepoint brainstorming plan allows you to set and communicate your project priorities, important info, warning areas, high / low importance areas and more on one page. On almost all of my projects, I publish the updated plans including this brainstorming plan on the Sharepoint Project. I put the image of the brainstorming plan on the homepage for quick visibility to all stakeholders and team.

You can download the plan at the link below:
Softvative-sharepoint-brain-storming-plan-v11

Here is the embedded view of my SharePoint Brainstorming Plan

http://bitly.com/sp0122

Sharepoint and MSProject Conference 2014 Slides and Videos

Tuesday, April 1st, 2014
In 2014, Microsoft had SharePoint Conference and Microsoft Project Conference. Those two conferences offer wealth of information including presentations, training, best practices and good knowledge base. Microsoft offered the full conference slides and videos this year. Here are the resources for those two conferences.

SharePoint Conference 2014 Slides and Videos on Channel 9
http://channel9.msdn.com/Events/SharePoint-Conference/2014/

MS Project Conference 2014 Slides and Videos on Channel 9
http://channel9.msdn.com/Events/Project/2014/

You can download the slides and videos for offline viewing. Manually downloading all contents will take too much time. Instead you can use the following Power Shell scripts to download the slides and videos in a folder on your local drive. SharePoint Conference contents are 72 GB and MS Project Conference 2014 contents are 29 GB in size

Power shell Script to Download All MS Project Conference Slides and Videos
http://gallery.technet.microsoft.com/PowerShell-Script-to-all-a0b94874/file/110942/1/DownloadProjectConferenceVideoandslides.ps1

Power shell Script to Download All Sharepoint 2014 Slides and Videos
http://gallery.technet.microsoft.com/PowerShell-Script-to-all-04e92a63/file/110503/3/DownloadSPC14Videoandslides.ps1

In my case, I renamed the scripts to DownloadPC14.ps1 and DownloadSPC14.ps1 on my local drive.

PowerShell Script in a folder

Run the scripts in Power Shell and it will start downloading the slides first and then all videos into a folders for each session.

MS Project Conference 2014 Contents 
SharePoint Conference Contents


????? ??????? ??? ? ?  ??????? ?????  
(Enjoy Sharepoint and MS Project learning)
🙂

References:
http://gallery.technet.microsoft.com/PowerShell-Script-to-all-04e92a63
http://gallery.technet.microsoft.com/PowerShell-Script-to-all-a0b94874