Front Page - Frontpage & MS SQL Connection Error-Please Help

Author

Frontpage & MS SQL Connection Error-Please Help

Sam White

2005-09-28, 6:26 pm

Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers
are NOT in a domain. The second server has SQL 2000, the first has IIS 6.0

Through OBDC (System DSN) I created a connection to the SQL db. Then on
my laptop I opened up frontpage to create a page to view the db results.
But, I get the this error when I select the "System Data Source on Web
Server":

"Login failed for user '(null)'. Reason: Not associated with a trusted
SQL Server connection"

I have been browsing through the web for some time now and can not seem
to get a direct resolution to this error.

On the SQL Server Management under Logins I have selected "Windows
Authentication", I have added the IIS_WPG, created a new account named
SQLUSER, etc..

Nothing seems to work. Every solution I have found so far on the web has
to do with another application, most often it seems it is a .net issue.

Basically I am trying to create forms via Frontpage to input and view
data entered into a SQL db.

Any help will be very much appriciated

Thomas A. Rowe

2005-09-28, 6:26 pm

You need to post to the MS SQL server and/or Windows 2003 server newsgroups as this is not a FP
issue.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================

"Sam White" <noSPAM@Please.com> wrote in message news:wuCdnbahoqA2k6beRVn-3g@giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are NOT in a domain. The
> second server has SQL 2000, the first has IIS 6.0
>
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my laptop I opened up
> frontpage to create a page to view the db results. But, I get the this error when I select the
> "System Data Source on Web Server":
>
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection"
>
> I have been browsing through the web for some time now and can not seem to get a direct resolution
> to this error.
>
> On the SQL Server Management under Logins I have selected "Windows Authentication", I have added
> the IIS_WPG, created a new account named SQLUSER, etc..
>
> Nothing seems to work. Every solution I have found so far on the web has to do with another
> application, most often it seems it is a .net issue.
>
> Basically I am trying to create forms via Frontpage to input and view data entered into a SQL db.
>
> Any help will be very much appriciated
>

Jon Spivey

2005-09-28, 6:26 pm

Hi Sam,

You're going to find it much easier to connect using sql server
authentication.
1/ Open Enterprise Manager right click your server and hit the Security tab.
Then under authentication click SQL Server and windows.
2/ Open up FP, go to Tools - Site Settings - Database - Add. Choose Network
Connection to Server. Hit Browse type the IP of your SQL Server in the
Server Name box and the db name under Database name. Hit Advanced and enter
your the Username and Password. You can connect as sa just to test this out,
but you'd obviously want to set up an appropriate account at some point.

This will get you connected without needing to mess with dsns and windows
authentication.

--
Cheers,
Jon
Microsoft MVP

oSPAM@Please.com> wrote in message
news:wuCdnbahoqA2k6beRVn-3g@giganews.com...
> Hi, I have 2 servers, both with Windows 2003 Standard edition. Servers are
> NOT in a domain. The second server has SQL 2000, the first has IIS 6.0
>
> Through OBDC (System DSN) I created a connection to the SQL db. Then on my
> laptop I opened up frontpage to create a page to view the db results. But,
> I get the this error when I select the "System Data Source on Web Server":
>
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
>
> I have been browsing through the web for some time now and can not seem to
> get a direct resolution to this error.
>
> On the SQL Server Management under Logins I have selected "Windows
> Authentication", I have added the IIS_WPG, created a new account named
> SQLUSER, etc..
>
> Nothing seems to work. Every solution I have found so far on the web has
> to do with another application, most often it seems it is a .net issue.
>
> Basically I am trying to create forms via Frontpage to input and view data
> entered into a SQL db.
>
> Any help will be very much appriciated
>

Sam White

2005-09-28, 10:26 pm

Thank you very much, it works perfectly. I already made up some forms
and can both save data as well as view it. Of course in all the mess
that has been going on, I forget when importing the tables from mysql to
insure that the ID field was set to autonumber. No problem as that is
easily fixed.

I cant begin to tell you how much of a relief this is that I can finally
get started on making up the forms I needed. I spend 3 weeks trying to
get mysql to work, 1 day to find that Access was not a viable option and
2 days trying to get SQL going. Strange, because I do remeber years back
setting up a SQL server on NT 4 and using Frontpage to connect without
problems, although those were very early versions and was years ago.

Again, thank you very much!

Jon Spivey wrote:
> Hi Sam,
>
> You're going to find it much easier to connect using sql server
> authentication.
> 1/ Open Enterprise Manager right click your server and hit the Security tab.
> Then under authentication click SQL Server and windows.
> 2/ Open up FP, go to Tools - Site Settings - Database - Add. Choose Network
> Connection to Server. Hit Browse type the IP of your SQL Server in the
> Server Name box and the db name under Database name. Hit Advanced and enter
> your the Username and Password. You can connect as sa just to test this out,
> but you'd obviously want to set up an appropriate account at some point.
>
> This will get you connected without needing to mess with dsns and windows
> authentication.
>