locked
MOSS 2007 Database Migration using SQL connection alias change throwing error RRS feed

  • Question

  • Hi Folks,

    We are trying to move SharePoint SQL server from one DC to another DC.

    Since we have made SQL server in new DC with other name so opted SQL server connection alias method to remap SQL mapping with existing farm.

    After creating SQL alias we are able to browse central admin sites but could not able to browse any other sharepoint sites.

    Event viewer showing below exception

    SQL database login failed. Additional error information from SQL Server is included below.

    Login failed for user 'computername$'.

    Any view will be much appreciable.

    Regards

    Friday, January 9, 2015 3:14 PM

All replies

  • Hi Folks,

    We are trying to move SharePoint SQL server from one DC to another DC.

    Since we have made SQL server in new DC with other name so opted SQL server connection alias method to remap SQL mapping with existing farm.

    After creating SQL alias we are able to browse central admin sites but could not able to browse any other sharepoint sites.

    Event viewer showing below exception

    SQL database login failed. Additional error information from SQL Server is included below.

    Login failed for user 'computername$'.

    Any view will be much appreciable.

    Regards

    Friday, January 9, 2015 3:14 PM
  • Hi Soni,

    check this link to migrate from one domain to another

    http://blogs.technet.com/b/sushrao/archive/2011/12/02/sharepoint-migrating-sharepoint-server-from-one-domain-to-another.aspx


    Kind Regards,

    John Naguib

    Technical Consultant/Architect

    MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation

    Please remember to mark your question as answered if this solves your problem

    Sunday, January 11, 2015 12:43 PM
  • Hi John,

    In my case the domain is same.Can you please suggest more specific on SQL aliasing part.

    We have followed below msdn link to move all databases to a different database server 

    http://technet.microsoft.com/en-us/library/cc512725(v=office.12).aspx#Section2

    Regards

    Soni K


    • Edited by Soni K Monday, January 12, 2015 10:22 AM
    Monday, January 12, 2015 10:21 AM
  • First: Putting SQL Server on a domain controller is not recommended. 

    Are the two domain controllers in different domains? Is the SharePoint server in the same domain as the new SQL instance?

    Do you have a SharePoint farm or a standalone installation? A common cause of the error you're seeing is if the application pools are using Network Service or Local System which can be the case of a standalone installation.


    Monday, January 12, 2015 5:21 PM
  • Hi Jason,

    Thanks for your reply.

    Both the domain controllers are in the same domain.Also SP server is in the same domain as the new SQL instance.

    I have a SharePoint farm where I am performing this activity.

    Regards

    Soni K

    Tuesday, January 13, 2015 10:41 AM