SQL Server Login when opening up a form

[JD]

I created an InfoPath form on a terminal server. When a particlular
user logs in and clicks the shortcut for the InfoPath form .xsn file,
the regular SQL Server/ADO security popups...um...well pop-up, but then
they get a SQL Server login box. How do I get rid of this? I want
them to use a trusted connection but when they click OK they get an
error.....they are in sql server as a user login. This is freaking me
out cause myself and other users can log in and get to the form with no
problems.......

Thanks in advance,
John

[Henning Krause [MVP - Exhange]]

Hello,

this *might* have to do with the Internet Security settings. InfoPath uses
the zone information and their corresponding restrictions from Internet
Explorer.

Perhaps the user experiencing these problems have more tight security
settings?

Greetings,
Henning Krause [MVP - Exchange]
==========================
Visit my website: http://www.infinitec.de
Try my free Exchange Explorer: Mistaya
(http://www.infinitec.de/software/mistaya.aspx)

"John" <NOSPAMJohnPeriodMurphy@IndigoEngineperiodcom> wrote in message
news:F446023F-479B-40C0...@microsoft.com...
> Carier & John
> I too have the same problem. Any hints?
>
> Regards,
> John
>
> "Carie" wrote:
>
>> I am having this same problem..... did you find the resolution?
>> Thanks in advance,
>> Carie

[John]

Hi.
I have found my own solution. It appears as if the users who were
encountering this error could not get to the database. (They had access, but
not connection.)

I had to go to all the laptops in question and add a System DSN, via Data
Sources (ODBC) in the Administrative tools. The issue seemed to be that the
default was Named Pipes, but my application and InfoPath were expecting
TCP/IP.

Hope this helps.
Regards,
John

[Patrick Temple]

I too am having this issue, only one guy but I'm expecting more.

John, could you eloborate on what you did to fix the problem. Not really
familiar with the ODBC and what not.

I do know I checked his security settings and he is using the same as
everyone else. He is using Win 2K instead of XP but Office 2003 same as
everyone else.

anyway if anyone heres of a fix for this let me know.

[John]

Patrick,
Hi - I found this issue happens in two situations:
1. The log in information to the database is not correct.
AND / OR
2. The computer in question is is trying to connect to the database via
Named Pipes, while the the database is expecting TCP/IP.

My recommendation to you is to extract the InfoPath form, open using WordPad
(or other text editor) and search for the word "connection". Around this you
will see the string of variables used to connect to the database. These
include the name of the server, the user name, the name of the catalog or
database and the password. Check these. If one of these is incorrect, you
will get the SQL Server Login popup.

If the connection string appears to be correct, open Control Panel ->
Administrative Tools -> Data Sources (ODBC). Then click on the System DSN
tab, and click Add. Find the correct driver from the list (SQL Server is
last), click Finish. Enter the name, descriptions and Server name on the next
page, then click Next.

Choose Win NT authentication or SQL Server authentication and click on
"Client Configuration". On this page, choose TCP/IP from the Network
Libraries list on the left. Then Next, and Next until you get the page that
says "Test Network Connection". If that works successfully, then try your
application again. If it does not, validate your login and password and other
variables.

Let me know if it works.
Regards,
John

[Patrick Temple]

John,

Thanks for elaborating. Unfortunately, I tried it and that does not appear
to be my problem, I can't make a connection with either named pipes or
TCP/IP. I verified all variable information for each user. For whatever
reason when the InfoPath form goes to connect these people to the SQL Server,
it drops their login information. So SQL server throws the login screen up
and then breaks. This only happens on a handful of my people. I'm guessing
its a combination of PC setup, IE Security settings, and something I haven't
thought of yet.

The weird part is that I use a web part that connects to the database to
retrieve a filtered view of data for the user. That works just fine, it only
breaks when you use and InfoPath form or one of the Microsoft Web Parts.

If anyoen has any ideas, let me know.

Thanks

--Patrick Temple