certificate error connecting to sql server express from ms/access

This question is related to the question

but I can't find the link to ask a related question

The problem is "ms/access link to sql/server express" is not working"


I have a working app in ms/access that uses, as backend, sqlserver express.

It is working, but now I need to deploy to a proper server, not on my development computer.

1. I Installed sql server express en MMSM, backed up my DB and restored it to the server. Verified connection and it is perfect. I can even edit table contents using MMSM
2. Now I need to create a link to it
2.1 created a new user (bddplus) which is a database (not windows) user
2.2 tested connection (was OK) - screenshot 1
2.2 view/edit table (was OK) - screenshot 2
3. started access and initiate the set up of link to tables in the DB (always on the server computer)
3.1 start - screenshot 3
3.2 link wizard - screenshot 4
3.3 select new data source - screenshot 5
3.4 select data source source - screenshot 6
3.4 ODBC driver as recommended (screenshot 7, 8, 9)
3.5 server/ selection (NOTE: no server shows on the list  in the server name box, so we need to input it directly) screenshot 10
3.6 details of the data source screenshot 11, 12 & 13
3.7 tests failed screenshot 14

It is Portuguese, and the error states "the certificate chain was issued by a non-reliable authority

Below I am embedding the images.

Is there another manner to connect? Can anyone help?


João serras-pereiraAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
If your not using a 3rd party certificate, then you should check "Trust Server Certificate" when setting up the DSN.  That should take care of it.

 Note that using a self-signed certificate for communications between the client and the server is not ideal.  


Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
João serras-pereiraAuthor Commented:
Well.. a Bit btter. Now it accepts and the connection test runs perfect. But the new created  link does not appear in the link data source for access so I cannot link the tables.

Can you help?
Jim Dettman (Microsoft MVP/ EE MVE)President / OwnerCommented:
<<Can you help?>>

  Make sure your creating a DSN in the correct "bitness"   If your using Access 32 bit, then you must use the ODBC applet in  C:\Windows\SysWOW64:


and for 64 bit:


  and make sure it's a system level DSN.   I would also use a DSN suffix on the name (i.e.  myDSNName_32 vs myDSNName_64).

  Last, I would consider ditching the DSN's entirely.   Two articles to help with that:


which covers taking an existing app and converting it.  And then:


which shows you how to do it with new tables and really is just further detail on the first article.   However I would not use the second method in that article, which is register database.  It has some issues.    

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.