Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
Bedrock Mission!

Learn more

View all

Sign in to view all badges

Environment Not trusted error HELP

Avatar

Level 2

I'm using the Microsoft Jet 4.0 connect string to connect to an Access database. I have 4 data connections to the database, 1 to a table (main connection), 2 to queries to populate drop downs and 1 to an SQL query to do a lookup.

When I open the extended form I get the "connection for sourceSet dataconnection failed" due to the environment not being trusted. How can I get arround this or make the environment trusted?

The form is being opend from My Documents and the database in on my Local network.

12 Replies

Avatar

Level 10

To work with the databases/ webservices the form needs to be Reader extend by using the Server Component. If you Reader Extend the form using Acrobat Pro it will not help. Because Acrobat Pro has limited functionality in Reader Extending the form.

If you can open the same form in Acrobat it should work as expected. But for Adobe Reader you need the Server Component.

Hope this gives an idea..

Thanks

Srini

Avatar

Level 10

I have seen this error a couple of times but I do not have an answer for you. I do not think it has anything to do with Reader Extensions though because I have seen it with Acrobat as well. I am looking into it but it will take some time to get the answers. I will post what I find when I have something to report.

.

Paul

Avatar

Level 2

Thanks Sirini and Paul.

I have to send the form to another agency to get extended. I THOUGHT they were doing it via LiveCycle server. I'll have to contact them and find out which way they're doing the extension.

It doesn't seem to matter if the document is in the same domain as the database or if it is local.

Any ideas on which documentation I might check in?

Avatar

Level 2

Here are the connect string generated by LC Designer:

Provider=Microsoft.Jet.OLEDB.4.0;User ID=Admin;Data Source=V:\mb\hr\PAR_PES Database\PAR_2003.mdb;Mode=Share Deny None;Extended Properties="";Jet OLEDB:System database="";Jet OLEDB:Registry Path="";Jet OLEDB:Database Password="";Jet OLEDB:Engine Type=5;Jet OLEDB:Database Locking Mode=1;Jet OLEDB:Global Partial Bulk Ops=2;Jet OLEDB:Global Bulk Transactions=1;Jet OLEDB:New Database Password="";Jet OLEDB:Create System Database=False;Jet OLEDB:Encrypt Database=False;Jet OLEDB:Don't Copy Locale on Compact=False;Jet OLEDB:Compact Without Replica Repair=False;Jet OLEDB:SFP=False

It's the same for all 4 connections.

Avatar

Level 10

Did you define this as a system DSN or a user DSN?

It shoudl be a system DSN to give it appropriate priveledges.

Paul

Avatar

Level 2

No, Paul, I didn't. Nor do I want to.

This app will eventually be going out to about 50,000 employees. I don't know of a way to push out a DSN to all the PC's and I'm not about to tell the IT office they have to go around to all the employees to install one. Well I could tell them but I don't think they'll do it as they have limited resources.

Anyway, if I can't make it work without creating a DSN then I'll have to try something else.

I'm sorry, but between the Micosoft trust, certificate authority and such, it is becomming a problem. The sad part is this is an Internal Network app that will never go beyond the firewall. It's hard enough setting up an interdepartmental trust between domains let alone not getting the form to trust something that is on the same domain or on the same network.

Thanks for letting me vent.

Avatar

Level 10

It is an absolute must that you setup a DSN on each machine and there is no way that I know of to automate it without someone touching each machine. This is one of the reasons why I do not recommend accessingn a DB from a form unless it is for a small manageable group.

Your alternative is to do it the database connectivity from a central server and have the form submit (roound trip) to that server. Or expose all of the database stuff through web services.

Paul

Avatar

Level 2

Thanks, Paul, buth that's just not an option. (not my call). I have been emailing with someone else on the project and he says there is an answer and that he is doing just what I want to do but with a different form using code in the background. Once I find out what it is I'll post it.

Avatar

Level 2

OK, from what I've been told, the code is in VB and is using the Windows login ID to authenticate. I'm trying to get the code to look at how he does it.

Avatar

Level 2

Hi,

I am having a similar problem when using the OLEDB Conntections.

Trying to connect to the database, and it only reads the first record. I am using OLEDB connections to

the SQL server. I have extended the form using the ReaderExtenstions.

But this "Connection for Source DBConnection failed because the environment is not trusted"

Do you what causes this error message, and how to get around.

Please advice.

Thanks

Ds

Avatar

Level 10

If you set up your DSN as a system DSN instead of a user DSN then that message shoudl disappear.

Paul

Avatar

Level 1

Paul:   I am not sure if this thread is still active.  I

hope it is still being monitored.  I am having the same issue as mentioned at the beginning of this. I have a similar situation as the PDF form being used would be used enterprise wide, without the required support from IT.  My solution has been to use a file DSN that is being used to create an ODBC connection for users to access a SQL database.  When attempting to connect my form to the database, I get the "Environment Not trusted" error.  I have created a system DSN for my computer for testing, but I still get the same error.  Is there something else i may be missing or can check?