Sign in
Share-n-dipity
SharePoint serendipity is the effect by which one accidentally discovers something fortunate, especially while looking for something else entirely. In this case, it is the occassional musings, observations, and Ouija board readings about the phabulously
Options
Blog Home
Share this
RSS for posts
Atom
RSS for comments
Search Blogs
Tags
ACS
ADFS
App Model
Authentication
Azure
CASI Kit
Claims
Client OM
Debugging
Development
FAST
Installation
Monitoring
New Features
oAuth
Operations
Performance
PowerShell
Search
SharePoint 2010
SharePoint 2013
Social
Troubleshooting
Visual Studio 2010
Windows Phone 7
Archive
Archives
May 2013
(3)
April 2013
(4)
March 2013
(1)
February 2013
(6)
January 2013
(3)
December 2012
(8)
November 2012
(4)
October 2012
(2)
September 2012
(5)
August 2012
(9)
July 2012
(14)
June 2012
(3)
May 2012
(3)
April 2012
(1)
March 2012
(3)
February 2012
(3)
January 2012
(2)
December 2011
(3)
November 2011
(1)
October 2011
(5)
September 2011
(5)
August 2011
(4)
July 2011
(5)
June 2011
(6)
May 2011
(3)
April 2011
(4)
March 2011
(6)
February 2011
(5)
January 2011
(4)
December 2010
(2)
November 2010
(12)
October 2010
(2)
September 2010
(6)
August 2010
(8)
July 2010
(8)
June 2010
(8)
May 2010
(8)
April 2010
(4)
March 2010
(6)
February 2010
(11)
January 2010
(4)
December 2009
(5)
November 2009
(13)
October 2009
(10)
June 2009
(4)
May 2009
(1)
Problems Joining a Server to a Farm?
TechNet Blogs
>
Share-n-dipity
>
Problems Joining a Server to a Farm?
Problems Joining a Server to a Farm?
Steve Peschka
27 Oct 2009 10:44 PM
Comments
1
If you try and join a new server to the farm, but can't get the config wizard to load the list of databases from the SQL Server, double check the firewall settings on the SQL Server and SharePoint server. You will often see what seems like a really bizarre error; something like System.ArgumentNullException was thrown. Additional exception information: The errorData argument cannot be null or zero length. Parameter name: errorData. Chances are the exceptions for SQL Server have not been properly configured. This has already tripped up a few different people I know, and since SharePoint is now going to require Windows Server 2008 you may not be used to having that firewall in place. Just one quick thing to check and try before that first wave of installation panic sets in.
1 Comments
SharePoint 2010
,
Installation
Comments
Comments
Loading...
Leave a Comment
Name
Comment
Please add 3 and 5 and type the answer here:
Post