Feb 11, 2012 at 6:01 PM
Edited Feb 11, 2012 at 6:37 PM
Thanks for your December 22 response -- this post has a solution.
At the time, I was enjoying a holiday break in California (where I grew up), and got to see some new parts of the state.
Pardon the graphics: this post started as my response to yours (for debugging), but based on responses from February 10, 2012, I was able (today) to find exactly what was different in my setup.
The solution (in my case) is to install Windows Authentication as part of IIS. As with all parts of Windows Server 2008 R2, servers are set up different ways. In my case, I am not explicitly using IIS for other uses, so
I believe the reason other people had seen this same connection error is that we had installed IIS under default-type settings, but were not actively using it.
I will be including my corresponding screen shots based on your earlier message. I knew I was using Windows Authentication to connect to SQL Server, but was unaware that it was not included in IIS. As you recall from my initial message, I believed
the issue was related to IIS and authentication, but I did not know how to proceed. Given that this demo is for SQL Server, my debugging energy was focused on the new pieces of SQL Server 2012 instead of directed at IIS. Apparently, others were
of the same mindset.
Different compared with last time is that this response is based on the
January 17, 2012 build. I was motivated to make this sample work since I will be using it for some demos (I have been getting more speaking opportunities since entering the Microsoft MVP program). FYI -- I happened to see a past demo
of this software, and they had included a paper I wrote titled
Why Use Microsoft Data Mining -- I had to do a double take when I saw that prevous demo.
My OS is Windows Server 2008 R2, and Server Manager provides an enumeration of installed software and services.
In my case, I had not enabled Filestream during installation, but Filestream can be subsequently intialized by using Configuration Manager and also running a EXEC command (the latter I believe is equivalent to changing the properties on the server
Reference: How to Enable Filestream (for SQL Server 2008 R2, but still OK for SQL Server 2012 RC0):
I had previously installed the Semantic DB, and I am doing this demo using the "Administrator" account:
The files appear to be complete -- this build has the version of 11.0.1750.32
I already demonstrated in the above SSMS picture that I am able to connect to the database with this account.
Now, more on the Silverlight. First, here is the response I see:
I believed the issue had something to do with IIS and authentication. Reading the
Incomplete Install? No Desktop Shortcut
discussion, I saw the screenshot from IIS based on Windows Authentication. These days, that method is the standard way to connect to SQL Server. I noticed that this options was NOT available on my IIS this time, and to test my theory, I made one change:
I added Windows Authentication. Other forms like Digest and Basic were not included in my installation. Once I made this change, the Silverlight application connects.
I have several abstracts submitted for upcoming SQL Saturday events, and hope to use this demo as part of these potential presentations.