SQL server at (Blank) has an unsupported version 10.0.2531.0

You update SQL 2008 to SP1 thinking ok I am ready......NO U R NOT! You will get the folowing error:

SQL server at [Your-DATABASE-SERVER] has an unsupported version 10.0.2531.0. Please refer to “http://go.microsoft.com/fwlink/?LinkId=165761” for information on the minimum required SQL Server versions and how to download them.

You might see threads here an there say that the minimum build number for SQL server is 10.0.2531.0. This is not very accurate as the minimum build for SPS 2010 for the SQL 2008 Enterprise Edition is the version number 10.0.2714.0 which is the cumulative update package 2. They are up to five now which I will post the link here: http://support.microsoft.com/kb/975977/en-us

If I had read the Pre-req from Microsoft for SharePoint 2010 it does state this.......But who reads! :)

SharePoint 2010 n SQL 2008 can't connect to DB

1. Open the SQL Server Configuration Manager (Start > SQL Server 2008 > Configuration Tools > SQL Server Configuration Manager
2. Navigate to the SQL Server Network Configuration > Protocols for MSSQLSERVER node in the tree view
3. Enable TCP/IP and Named Pipes (you’ll be warned that these changes will not apply until you the service is shut down)

That will allow you when installing SPS 2010 to connect to a SQL 2008 Server. This took 4 hours to finally figure out.

Infopath - no access to pull ad data?

I was getting the following error during my first try:
The query cannot be run for the following DataObject: GetUserProfileByNameInfoPath cannot run the specified query.The SOAP response indicates that an error occurred on the server:
Server was unable to process request. ---> Attempted to perform an unauthorized operation.

Cause: I was calling the web service against the server root that I didn’t have access to. For example http://server/_vti_bin/userprofileservice.asmx but I didn’t have access to http://server

Solution: Call the web service against the site the InfoPath template lives in, which the current user has access to. For example http://server/sites/sitename/_vti_bin/userprofileservice.asmx

Infopath - pull into the form current user

http://blogs.microsoft.co.il/blogs/itaysk/archive/2007/04/05/InfoPath-_2D00_-Get-the-current-user-without-writing-code.aspx

This worked like a charm, good find and great post.

Still need help and I hope all these posts help someone else like me who is in the process of living inside SharePoint :)

Spellcheck does not work

Stumbled across this and found two options as a workaround for now.

Solution:

1) Give all necessary users the contribute permission level on the top site (“read” is not sufficient). Next, break the inheritance on all lists, libraries and subsites of the top site where you do not want those users to have contributor access.
Which users? You can use all authenticated users, but it is only those users that will be wanting to use the spell check for whom it’s necessary. So de facto that means only contributors or higher.

2) If you think the above solution is quite drastic and requires too much maintenance or could cause a security leak later, you can also

a. On the top site, create a new permission level, e.g. “spellcheck”. Assign only the following site permissions to the permission level:
- browse directories

- view pages

- use remote interfaces

- open

Any other will give more rights, any less will not solve the problem.

b. On the top site again, assign the new permission level to the necessary users. The effect will be that

i. they càn access the topsite but not view any content. They can use it to browse to their subsite

ii. they can use the spellcheck


http://social.technet.microsoft.com/forums/en-US/sharepointadmin/thread/1fd7350f-742d-4e32-8b57-3c32e5838d2a/

Populate InfoPath forms with AD Information - NO CODE

http://kwizcom.blogspot.com/2007/11/importing-data-from-ad-to-infopath-2007.html

This is so easy, Kudos for the post Thank you....

Import AD accounts into InfoPath form...EASY!

http://kwizcom.blogspot.com/2007/11/importing-data-from-ad-to-infopath-2007.html

This is a perfect way to not use code to obtain information from AD in an InfoPath form.

Kudos to this blog, and its so easy a caveman could do it!