I just setup my server with win2k3 sp1 and ALL the latest patches, plus
sql 2004 standard sp4.
I keep getting this error on a table with 39000 records where I am
running a basic wildcard CONTAINS fulltext query for "cer*"
Server: Msg 7643, Level 16, State 1, Line 1
Your search generated too many results. Please perform a more specific
search.
There should be about 30000 records.
I noticed on technet that this was a problem pre sp2 in sql, but was
since patched. Has the bug recently been re-introduced in some combo
of win2k3 and sql patches?
Phadke,
Yes, there was some additional logic added in SP3 that generates the below
error message. SQL FTS is optimized for returning 2000 results per query,
primarily for performance reasons. You may want to re-write your query using
CONTAINSTABLE and use the Top_N_by_Rank parameter to limit the results to
2000 or use a similar TOP restriction in the select list.
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
<phadke@.gmail.com> wrote in message
news:1129632193.545575.218860@.g47g2000cwa.googlegr oups.com...
>I just setup my server with win2k3 sp1 and ALL the latest patches, plus
> sql 2004 standard sp4.
> I keep getting this error on a table with 39000 records where I am
> running a basic wildcard CONTAINS fulltext query for "cer*"
> Server: Msg 7643, Level 16, State 1, Line 1
> Your search generated too many results. Please perform a more specific
> search.
> There should be about 30000 records.
> I noticed on technet that this was a problem pre sp2 in sql, but was
> since patched. Has the bug recently been re-introduced in some combo
> of win2k3 and sql patches?
>
|||John,
Just to clarify, is this a hard limit of 2000, because I am able to see
the result set for queries that return a con query with 17-18k records
with no problem.
I saw another technote that the problem limit was at approx 20k
records:
http://support.microsoft.com/default...;en-us;Q296456
Thanks for the info,
Aditya
|||Also, is this limitation common to sql 2005?
|||Ok, now I am really confused...I ran a fulltext query for "c*" on a
database on another server. This database has 2.4 Million Records.
This server is Win2k3 (no SP) and SQL 2k SP3.
When I run the query, I get 900,000 records back without an error
message.
|||Aditya,
Yes, this is the KB article that I couldn't find early this morning when in
a rush to get off to work...
Still for performance reasons, it might be best to use Top_N_Rank with
CONTAINSTABLE or is there a specific reason you want to return this many
rows?
Thanks,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
<phadke@.gmail.com> wrote in message
news:1129660216.247521.205300@.g47g2000cwa.googlegr oups.com...
> John,
> Just to clarify, is this a hard limit of 2000, because I am able to see
> the result set for queries that return a con query with 17-18k records
> with no problem.
> I saw another technote that the problem limit was at approx 20k
> records:
> http://support.microsoft.com/default...;en-us;Q296456
> Thanks for the info,
> Aditya
>
|||Aditya,
I need to confirm this with a large table in order to generate the large
results. However, I would suspect that it is still in SQL 2005 until proved
otherwise...
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Aditya Phadke" <phadke@.gmail.com> wrote in message
news:1129660966.529955.176010@.g44g2000cwa.googlegr oups.com...
> Also, is this limitation common to sql 2005?
>
|||Aditya,
Different servers can behavior differently for FTS results based upon the OS
platform (different wordbreakers) and due to different noise word file
contents. In this case, and on this server is the single letter "C" removed
from the language-specific noise word file (noise.enu = US English) for the
specific FT-enable column's "Language for Word Breaker"?
As they say the devil is in the details... ;-)
Regards,
John
SQL Full Text Search Blog
http://spaces.msn.com/members/jtkane/
"Aditya Phadke" <phadke@.gmail.com> wrote in message
news:1129672239.794380.257680@.o13g2000cwo.googlegr oups.com...
> Ok, now I am really confused...I ran a fulltext query for "c*" on a
> database on another server. This database has 2.4 Million Records.
> This server is Win2k3 (no SP) and SQL 2k SP3.
> When I run the query, I get 900,000 records back without an error
> message.
>
Showing posts with label standard. Show all posts
Showing posts with label standard. Show all posts
Monday, March 26, 2012
Frustration with UniqueIdentifiers (GUIDs)
We're trying to set a new standard at my office, of using GUIDs as database ID fields - all new tables in all databases will have a GUID as the ID field, using the UniqueIdentifier data type.
The problem that we are running into, is that different applications interpret the UniqueIdentifier data type differently - ADO 2.x interprets it with the opening and closing { } braces. ADO.NET does not include the { and } in the GUID structure, SQL Server Query Analyzer does not include the { } braces, and SQL Server Enterprise Manage does include the { }
so we end up with results like this:
ADO 2.x: {012345678-abcd-ef01-2345-6789abcd}
ADO.NET: 012345678-abcd-ef01-2345-6789abcd
Query Analyzer: 012345678-abcd-ef01-2345-6789abcd
Enterprise Manager: {012345678-abcd-ef01-2345-6789abcd}
The problem with this is in two parts:
1) VB6 does not have a GUID structure or data type, so we are treating GUIDs as strings... but VB6 doesn't recognize "{012345678-abcd-ef01-2345-6789abcd}" and "012345678-abcd-ef01-2345-6789abcd" as the same string
2) when sending a URL link through an email, the { } braces break the link - in all email applications that we have tested. This include Groupwise 6, Groupwise 6.5, IPSwitch Web IMail, Outlook 2000, and Outlook Express (IE 6).
We're becoming very frustrated with the problems at hand, and need to know how others have worked around these problems. Please respond with any kind of advice or any real life situations where you have encountered this and found a solution, etc.
Thanks.The workaround is simple: program around it.
Standardize on the "new form" without curly braces and never show the m in any other way.
In "old vb" this means writing two little transform methods. Hardly a hugh task.|||so you're basically saying that every application we ever write with GUIDs has to have special processing code inside of it to handle guids?
that doesn't seem to be very smart, if you ask me.|||Well every application you ever write will not connect to several different types of data sources, will it?
And the 2 odd lines of code in every application... is too much? Really? Then I question the need for GUIDs in your application. Why did you feel the need to use them?
Friday, March 23, 2012
Frontpage & MS SQL Connection Error-Please Help
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
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-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
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
> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-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
Frontpage & MS SQL Connection Error-Please Help
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
This error means that the account is unknown on the SQL Server machine.
For example, suppose I create a user named User1 on computer Machine1.
Then I try to log into SQL Server on Machine2 using User1 from Machine1.
This is not possible because Machine2 has no idea about User1.
However, there is one trick you can employ to make this work, an old NTLM
trick that is used here.
If you create same user name on 2 machines with same exact password, then it
is possible for these accounts to work in this fashion (User1 from Machine1
to log into Machine2 as User1).
So in your case you need to create SQLUser on both machines with exact same
password and in theory it should work.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbmhoqAck6beRVn-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
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
This error means that the account is unknown on the SQL Server machine.
For example, suppose I create a user named User1 on computer Machine1.
Then I try to log into SQL Server on Machine2 using User1 from Machine1.
This is not possible because Machine2 has no idea about User1.
However, there is one trick you can employ to make this work, an old NTLM
trick that is used here.
If you create same user name on 2 machines with same exact password, then it
is possible for these accounts to work in this fashion (User1 from Machine1
to log into Machine2 as User1).
So in your case you need to create SQLUser on both machines with exact same
password and in theory it should work.
Matt Neerincx [MSFT]
This posting is provided "AS IS", with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbmhoqAck6beRVn-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
Frontpage & MS SQL Connection Error-Please Help
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> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-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
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> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-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
Frontpage & MS SQL Connection Error-Please Help
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> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
--
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-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
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> "Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection"
Should give you a clue. One server does not trust the other BECAUSE THEY ARE
NOT IN A DOMAIN.
There is no way for the SQL server to know anything about the IIS server, it
could be anything trying to hack into the SQL Server.
I don't know how to get IIS to log into SQL using SQL authentication either
but perhaps you could post that question to an IIS newsgroup.
The other option is to add them both to a domain and set up an account on
SQL that refers to the IIS account and this time they will be authenticated
via the Domain Controller.
--
Nik Marshall-Blank MCSD/MCDBA
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbqhoqA4k6beRVn-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
Frontpage & MS SQL Connection Error-Please Help
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
If you are not on a domain your best bet is probably to use SQL
Authentication. You will pass a user name and password from the web page to
SQL Server.
Keith
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbihoqAZk6beRVn-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
|||I meant to mention in my previous post that you can look up connection
string examples on www.connectionstrings.com
Keith
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbihoqAZk6beRVn-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
sql
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
If you are not on a domain your best bet is probably to use SQL
Authentication. You will pass a user name and password from the web page to
SQL Server.
Keith
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbihoqAZk6beRVn-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
|||I meant to mention in my previous post that you can look up connection
string examples on www.connectionstrings.com
Keith
"Sam White" <noSPAM@.Please.com> wrote in message
news:wuCdnbihoqAZk6beRVn-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
sql
Subscribe to:
Posts (Atom)