I've got SQL Server Express 2005 running as a backend and a front-end
made with microsoft access. I can connect when I run the front-end on
the same machine as the SQL Server but as soon as I try to set up a
network ODBC connection I get these errors. (The access front-end can
see the SQL Server - just not login to it).
This is the error I get:
Connection failed.
SQLState. '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for
user
'sa'. The user is not associated with a trusted SQL Server connection.
I have tried this with several different user name/password
combinations with varying degrees of permissions but none of them can
login. There is norton protection on but I set it to allow this type of
connection.
I went through the SQL Server 2005 connection FAQ with no result.Perhaps one of these articles will help:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/defaul...kb;EN-US;914277
Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/ar.../23/192044.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"p" <p.macrae@.gmail.com> wrote in message
news:1165358176.124238.273490@.73g2000cwn.googlegroups.com...
> I've got SQL Server Express 2005 running as a backend and a front-end
> made with microsoft access. I can connect when I run the front-end on
> the same machine as the SQL Server but as soon as I try to set up a
> network ODBC connection I get these errors. (The access front-end can
> see the SQL Server - just not login to it).
> This is the error I get:
> Connection failed.
> SQLState. '28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed fo
r user
> 'sa'. The user is not associated with a trusted SQL Server connection.
> I have tried this with several different user name/password
> combinations with varying degrees of permissions but none of them can
> login. There is norton protection on but I set it to allow this type of
> connection.
> I went through the SQL Server 2005 connection FAQ with no result.
>
Showing posts with label backend. Show all posts
Showing posts with label backend. Show all posts
Sunday, March 11, 2012
Cannot log-in to SQL Server
I've got SQL Server Express 2005 running as a backend and a front-end
made with microsoft access. I can connect when I run the front-end on
the same machine as the SQL Server but as soon as I try to set up a
network ODBC connection I get these errors. (The access front-end can
see the SQL Server - just not login to it).
This is the error I get:
Connection failed.
SQLState. '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'sa'. The user is not associated with a trusted SQL Server connection.
I have tried this with several different user name/password
combinations with varying degrees of permissions but none of them can
login. There is norton protection on but I set it to allow this type of
connection.
I went through the SQL Server 2005 connection FAQ with no result.
Perhaps one of these articles will help:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"p" <p.macrae@.gmail.com> wrote in message
news:1165358176.124238.273490@.73g2000cwn.googlegro ups.com...
> I've got SQL Server Express 2005 running as a backend and a front-end
> made with microsoft access. I can connect when I run the front-end on
> the same machine as the SQL Server but as soon as I try to set up a
> network ODBC connection I get these errors. (The access front-end can
> see the SQL Server - just not login to it).
> This is the error I get:
> Connection failed.
> SQLState. '28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'sa'. The user is not associated with a trusted SQL Server connection.
> I have tried this with several different user name/password
> combinations with varying degrees of permissions but none of them can
> login. There is norton protection on but I set it to allow this type of
> connection.
> I went through the SQL Server 2005 connection FAQ with no result.
>
made with microsoft access. I can connect when I run the front-end on
the same machine as the SQL Server but as soon as I try to set up a
network ODBC connection I get these errors. (The access front-end can
see the SQL Server - just not login to it).
This is the error I get:
Connection failed.
SQLState. '28000'
SQL Server Error: 18452
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
'sa'. The user is not associated with a trusted SQL Server connection.
I have tried this with several different user name/password
combinations with varying degrees of permissions but none of them can
login. There is norton protection on but I set it to allow this type of
connection.
I went through the SQL Server 2005 connection FAQ with no result.
Perhaps one of these articles will help:
Configuration -Configure SQL Server 2005 to allow remote connections
http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277
Configuration -Connect to SQL Express from "downlevel clients"
http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"p" <p.macrae@.gmail.com> wrote in message
news:1165358176.124238.273490@.73g2000cwn.googlegro ups.com...
> I've got SQL Server Express 2005 running as a backend and a front-end
> made with microsoft access. I can connect when I run the front-end on
> the same machine as the SQL Server but as soon as I try to set up a
> network ODBC connection I get these errors. (The access front-end can
> see the SQL Server - just not login to it).
> This is the error I get:
> Connection failed.
> SQLState. '28000'
> SQL Server Error: 18452
> [Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user
> 'sa'. The user is not associated with a trusted SQL Server connection.
> I have tried this with several different user name/password
> combinations with varying degrees of permissions but none of them can
> login. There is norton protection on but I set it to allow this type of
> connection.
> I went through the SQL Server 2005 connection FAQ with no result.
>
Friday, February 10, 2012
Cannot find stored procedure
I developed a ASP.net web application with a MSDE database backend on my laptop(vs.net 2003 XP Pro), then I transferred the website onto a server(Windows Server 2003) and generated a SQL Server 2000 database from the scripts I exported from MSDE(web administrator). The problem I am having is that it can't find any stored procedures. I keep getting errors when logging on, 'Could not find stored procedure "_myProc" '.
Any one with any clues what might be the problem?
Yes I have changed the connection strings.
Thanks in advance
PPerhaps the owner of the SP is not what you expect? I have not used web_administrator, but perhaps it does not prefix SPs scripted with dbo., and so the SPs are owned by a different user.|||My Error, SP is case sensitive and somehow during the transfer of the site and DB one letter in SP name was changed to upper case. Buggered if I know how.
Have a great weekend Doug
Thanks for the help
Pete
Any one with any clues what might be the problem?
Yes I have changed the connection strings.
Thanks in advance
PPerhaps the owner of the SP is not what you expect? I have not used web_administrator, but perhaps it does not prefix SPs scripted with dbo., and so the SPs are owned by a different user.|||My Error, SP is case sensitive and somehow during the transfer of the site and DB one letter in SP name was changed to upper case. Buggered if I know how.
Have a great weekend Doug
Thanks for the help
Pete
Subscribe to:
Comments (Atom)