Tuesday 17 April 2012

error failed to connet to the configuration database: an exception of type system.argumentnullexception was thrown. additional exception information: value cannot be null parameter name: service.

Error failed to connet to the configuration database: an exception of type system.argumentnullexception was thrown. additional exception information: value cannot be null parameter name: service.

I was adding a new WFE in an existing SharePoint farm and when I ran the configuration Wizard got the error:

 Failed to connet to the configuration database: an exception of type system.argumentnullexception was thrown. additional exception information: value cannot be null parameter name: service.

I figured out we moved our database servers from old to new sometime back and the configuration database had entries for the old database server name.

Solution 1: Created SQL Alias on the WFE server pointing to new databse server and ran the configuration wizard worked all good for me

Click on the below link to check the steps on how to create an SQL Alias

Solution 2: If the first one didn’t work, you may have to create a new configuration database but that has its own dependencies. Number of Solution packages you have , settings etc. it’s an addition overload but may have to do this if SQL Alias doesn’t help.

Login to the SharePoint Server
Click on All Programs > Microsoft SharePoint 2010 Products
Launch SharePoint 2010 Management Shell

Run the following command
New-SPConfigurationDatabase

This will ask for following details:
Database Name: New Configuration Database Name
Database Server: Database Server Name
Prompts for Farm Credentials, enter the same

Now run the Product and Configuration wizard this will solve the issue.


6 comments:

  1. Thanks, you saved my day!

    ReplyDelete
  2. Thanks, method #1 was not working for me so I used the 2nd method and then ran Config. wizard. It created a new farm that has to configured all again.

    The trick in Solution 1 is to use EXACT same alias name as previous Database Server - it worked! presto!


    ReplyDelete
  3. Method 1 Worked for me too . tyvm

    ReplyDelete
  4. In my case, i just needed to specify the server name in registry
    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\14.0\Secure\ConfigDB\DSN
    It solved my issue.

    ReplyDelete
    Replies
    1. Wow, you saved me Anonymous. I can't exp^lain why, but one of my Front End corrupted this key. I copied the value from another server and it solved my issue.

      Delete
  5. Attractive component to content. I simply stumbled
    upon your web site and in accession capital to say that I acquire actually enjoyed account your weblog posts.

    Anyway I'll be subscribing to your augment and even I fulfillment you get admission to consistently rapidly.


    my web site Saffron Cleanse Supplement

    ReplyDelete