IIS 7 and Above
Problem setting up new WinServer2016 for ASP.NET and SQL Website
Last post Feb 14, 2018 02:26 AM by Yuk Ding
Feb 13, 2018 10:16 AM|cheezefrog|LINK
I have an error now showing after migrating my website from a Windows Server 2008 OS to a fresh install and upgraded OS for WinServer2016 with SQL Dev 2017 and IIS. Can anyone point me in the right direction to how I can resolve this error when attempting
to have my website connect to the SQL database? I am not sure why it's trying to access the database through "workgroup". Also would like to make sure it stays secure.
code in web.config
add name="SON_SERVER" connectionString="Data Source=WIN-2LRB**********;Initial Catalog=SON;Integrated Security=True" />
thanks in advance
Feb 13, 2018 03:34 PM|lextm|LINK
It goes back to your SQL Server connection string, and you probably should consult other ASP.NET developers on
As you are using WORKSPACE, instead of Active Directory, probably you should specify a user and its password directly in the connection string. When you don't specify such, by default the machine account (WORKSPACE\...) would be used to connect to the SQL
Server instance, which is what you observed.
As a developer, there is far too much you need to learn, so this alone won't be the "last snag" which I can assure.
Feb 13, 2018 06:40 PM|cheezefrog|LINK
I would rather not use a Mixed Mode Authentication because it is less secure........My website works perfect on my other machine with WinServer2008 and SQL Server 2008. The new SQL Server 2017 just hasn't been configured correctly to accept WORKSPACE groups
which is what I need help with in granting those permissions for the SQL Server.
Feb 14, 2018 02:26 AM|Yuk Ding|LINK
So could in log in the sql server database with the 'workgroup\username'. IIS should have nothing to do with the sql server connection string. If you failed to connect the sql server database. Please ensure you have set the sql server allow the windows authentication
via this user account. In addition, please ensure you have mapped the windows login to user account. Of course, please ensure the schema has been set correctly.