Blog

  • 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.
    Details:
    [CrossDomainError]
    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)
    https://public.sathiya.io:48652/

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

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

    (or)

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

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

  • 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.

  • Analyse MS-SQL Database Memory Utilization

    In most of the development environment or staging server will not be monitored by daily. So the database auto growth can occupy countlessly. Here, we can analyze the memory utilization about the table and we can remove if the database has cache, temp or logs table.

    Cheers..!

  • Create claims-based web application from SharePoint PowerShell

    Creating claims-based web application is more flexible with SharePoint PowerShell script than CA. Here, the snippet for http and ssl site.

    Cheers…!

  • Delete SharePoint list items from PowerShell

    Here the quick solution to clean up/delete SharePoint list items that save a days lot if cleanup required. Manual efforts would take a lot so prefer to go with scripts;

    Cheers…!

  • Export Windows Service to Excel with Filter

    Another sample Powershell script to exporting “Running” and “Stopped” windows service to excel by using Powershell Array.

    Cheers!

  • Creating Managed Metadata Service Application by Powershell Script

    As we are all knows, the SharePoint Powershell can be fast and simple. Here the sample script for creating Managed Metadata Service Application;

    Cheers!

  • SharePoint continuous user login prompting with custom host header site

    SharePoint site with custom host header will prompting the user login screen on local machine but either you can login or view the site from your local network machines. Because the loop back is enabled by default on each and every machine. To resolve the issue you have to disable it.

    Open PowerShell as administrator privilege and run the below script;

    I hope the things are going good :)Cheers!

  • Import Users in Active Directory Using PowerShell

    Today, we are going to discuss about importing bulk users in Active Directory using PowerShell. We are all knows that we can do anything in PowerShell.
    You can check the required parameter for adding AD user. But I’m going to import the below sample fields.

    Basic Comment
    New-ADUser
    -Name “Disply Name”
    -GivenName “First Name”
    -Surname “Last Name”
    -SamAccountName “UserName”
    -UserPrincipalName “username@sathiya.io”
    -Path “OU=OrganizationUnit,DC=sathiya,DC=io”
    -Enabled $true
    -PasswordNeverExpires $true
    -AccountPassword (ConvertTo-SecureString “password” -AsPlainText -force)
    -PassThru

    The above script is for adding single user.

    Script

    Sample CSV file ImportUser.csv

    I hope the things are going good :)Cheers!

  • Application error when access “/_layouts/15/workflow.aspx”

    After, I installed and configured the workflow for SharePoint 2013 and register to the web application, it was getting an error while starting the workflow as;
    Error:
    Message: Application error when access /_layouts/15/workflow.aspx, Error=The pipe endpoint ‘net.pipe://localhost/SecurityTokenServiceApplication/appsts.svc’ could not be found on your local machine.
    EventID: 8nca
    Solution:
    Make sure the Net.Pipe Listener Adapter windows service is running, if not run net start NetPipeActivator. I hope this helps.