A connection could be established to the application database server but mixed mode authentication isn’t enabled… Wassssup Access!

It seems that sometimes in Microsoft, the right hand does not know what the left hand is doing… like where the right hand recommends the use of SQL Aliases when connecting to databases within SharePoint, but the left hand is building Access Services for SharePoint which does not recognise them… Ah yeah!

When you try to create a service app for Access in SharePoint 2013, you get an error message saying: A connection could be established to the application database server but mixed mode authentication isn’t enabled. Now if you are using Windows Authentication (and good on you for doing so) you don’t need to enable Mixed mode authentication just to get the app up and running, you simply need to use the SQL Server’s machine / cluster name (and instance if it’s not the default).

Problem solved!

Advertisements

About Brad Saide

I'm a SharePoint consultant. I'm also slowly going bald, seem to have a permanent spare tyre around my waist and enjoy socialising with friends over a beer or 10. The last 2 may possibly be related. Started working with SharePoint when the first version was in limited beta release (participated in the Technology Adoption Program while at Woolworths) and have been committed to the adoption of the technology as a business enabler ever since.
This entry was posted in Uncategorized. Bookmark the permalink.

4 Responses to A connection could be established to the application database server but mixed mode authentication isn’t enabled… Wassssup Access!

  1. Cat says:

    I’m having trouble getting the right combo here (I hope)… I’ve tried all kinds of combos and nothing is working. Also, did you mean “/” or “\” ? I don’t really have any other name that I set up other than the name of the SQL Server (I did setup an alias, but that obviously isn’t working). I do not see any property that says “cluster name” only server name. Where would I find this?

    • Brad Saide says:

      Hi Cat.

      Assuming you are getting the same error message, all you need to do is put in the name of the instance on your SQL server when setting up the Access App. Normally in simple implementations, this is just the machine name. It’ll be the same as the database server name your SharePoint farm connects to, normally. You do not need to enable mixed mode authentication on the SQL Server to get this running…

      • Cat says:

        Actually I found that this wasn’t the resolution to my issue – the final action that seemed to resolve the issue was stopping Microsoft SharePoint Foundation Web Application on the app server and I was then able to use the alias I had set up for SQL

  2. Indeed the web application need to be restarted because it seems that at starting time reads from the database what type of authentication the database server is configured for.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s