Upgrade SharePoint 2013 Enterprise 15.0.4569.1000 to 15.0.4641.1000

To upgrading SharePoint server 2013 Enterprise from 15.0.4569.1000 to 15.0.4641.1000 had a long investigation and searching on web made me confusion.  Even I didn’t find any clear way that to reach there.  So I kept my finger crossed and jump into my another SP Farm which has the same build.  Finally got a clue and spins a toss.  What does it? Just keep down your’s eyes 🙂

Once we upgraded SP1 then have to install Aug 2014 CU’s (KB2883086, KB2883085,  KB2883078, KB2880559, KB2760213).

After that we have to install the security update for SP server KB2880994 file.

Finally you will get an updated SharePoint server 2013 enterprise with Build 15.0.4641.1000.


Transact-SQL Restore Latest Backup File

Here the very basic steps to restore latest SQL backup file on the backup media location using the below Transact-SQL statement (T-SQL Statement).

  1. Open SQL management studio and make sure the SQL Server Agent is running.  If its not go to windows services.msc and start SQLSERVERAGENT service or use “net start SQLSERVERAGENT” cmd.
    Screenshot 2016-02-25 13.04.20
  2. Expand the Management from object explorer section and right click Maintenance Plans  to create create new maintenance plan.
  3. Drag and drop the Execute T-SQL Statement Task tool from Toolbox windows to design panel.
    Screenshot 2016-02-25 12.52.41
  4. Right click the task to put the below T-SQL statement on it
    Screenshot 2016-02-25 12.52.22
  5. Save the task and run from Jobs under SQL Server Agent
    Screenshot 2016-02-25 12.53.52
    Screenshot 2016-02-25 12.54.03
  6. Make sure the job successfully completed and check the database updates.



GP Web client error with SSL/TLS

We have already seen the cross domain issue with the previous post. Here the security issue with SSL/TLS to establish trust relationship to session central service.


An error occurred during session monitoring: ‘System.ServiceModel.Security.SecurityNegotiationException: Could not establish trust relationship for the SSL/TLS secure channel with authority ‘marinerydynamics.cloudapp.net:48650’. —> System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel. —> System.Security.Authentication.AuthenticationException: The remote certificate is invalid according to the validation procedure.

The web application ssl has been configured in IIS, but we have to create the trust certification access from windows certificate manager console.
Hove to copy the SSL certificate from personal to “Trust Root Certificate Authority” section. Now the service certification will be authorized to establish the connection.

1. Go to Run command and type certmgr.msc.

2. Now expand the Certificate–>Personal -> Certificate

3. Select the web site certificate which is installed on IIS. Right click and copy the certificate

4. Now expand the Certificate–>Trusted Root Certification Authorities -> Certificate. Right click and past it

6. Now enter the GP web client url.

Cross Domain Error in Dynamic GP 2013 Web Client

The cross domain error would be occurred on Silverlight. Because distinct URL has been configured on session central service, session service and run time service.

Severity: Critical
Summary: An error occurred while initializing communication with the server.
Arguments: https://marinerydynamics.cloudapp.net:48652/RuntimeService/3468
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.41212.00&File=System.ServiceModel.dll&Key=CrossDomainError

Scenario 01:
For example I have configured session central and session service with out SSL and runtime service with SLL, in my scenario looks like;
Here the service URL has been configured in same domain.

http://gpserver:48650/SessionCentralService (without SSL)
http://gpserver:48651/SessionService (without SSL)
https://webclient.sathiya.local:48652/ (SSL mandatory for GP web client Runtime service)

Scenario 01:
If suppose the web client is accessible thought internet and configured public url then the Runtime service will be configured like https://public.sathiya.io:48652/.
So the silver light wont communicate between cross domains.

http://gpserver:48650/SessionCentralService (Local url)
http://gpserver:48651/SessionService (Local url)

So you have to configure all three service url should be in same domain. Either it would be local FQDN urls or public urls,

https://webclient.sathiya.local:48650/SessionCentralService (without SSL)
https://webclient.sathiya.local:48651/SessionService (without SSL)


https://public.sathiya.io:48650/SessionCentralService (Local url)
https://public.sathiya.io:48651/SessionService (Local url)

Security issue may happen after installed this setup. To resolve Web client error with SSL/TLS

Verifying SMTP SharePoint Outbound mail settings

Once we configured the SharePoint outbound mail server then our responsible to test the setup. Here the small powershell snippet will do!

If you get “True” the configuration perfectly alright, else you have to check the ULS log to find an issue. Suppose if you are not getting a mail you have to check smtp log or address to exchange/wintel team.