error 18456 when running job

sql2k sp3
Ive got a job that creates a folder both on the local box
and on the remote box. This job has run every nite
successfully for a few weeks now. Last nite it failed with
message: Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
I havent changed anything security or services related.
The sql services for both boxes run in the same domain
admin account.
Any ideas?
Thanks, Chris.Try making the job owner sa. I've seen this and it ideespeared when I did that.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"chris" <chrisr@.fingps.com> wrote in message news:034901c36693$a4ce8750$a501280a@.phx.gbl...
> sql2k sp3
> Ive got a job that creates a folder both on the local box
> and on the remote box. This job has run every nite
> successfully for a few weeks now. Last nite it failed with
> message: Login failed for user 'NT AUTHORITY\ANONYMOUS
> LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
> I havent changed anything security or services related.
> The sql services for both boxes run in the same domain
> admin account.
> Any ideas?
> Thanks, Chris.

Error : SQL server does not exist or access denied.

Error : SQL server does not exist or access denied.
We are replacing the box the SQL server resides on and we have set up the
new server as a copy of the old one. It is a Win2000server with DNS and
active directory.
SQL server ver 8.00.760
We are able to:
Attach to the new server from workstations including exploring and
mapping the drives (actually our old server mappings worked)
We can establish an ODBC connection to the SQL server from the new box
and it tests fine so the server is started and running.
We were able to get one workstation to access the SQL server after
enabling name pipes but another still could not.
We are able to connect to the old DNS server and SQL server from all
workstations with no difficlties. Only one of the servers is connected at at
ime.
We can not set up an ODBC connection from any other workstation attached to
the new server. This is the error message we receive:
Connection failed:
SQL State 01000
SQL Server error: 10060
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
()).
Connection failed:
SQL State 08001
SQL Server error 17
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
or access denied.
There is no firewall in between the server and workstations (a fire wall
resides between the server and the internet with NAT enabled).
Login is set to use both windows and SQL authentication. We have tried it
as SQL only login with the same error message.
We have worked through Microsoft document 328306 "Potential causes of the
"SQL Server does not exist or access denied" error message"
Any ideas where our problem is?
Thank you,
Michael
Hi All,
We are facing exactly similar problem. Does anyone have any idea/thoughts as
to why this could be happening and what we can do to troubleshoot/solve this
problem.
Many Thanks,
Parag
"MABrown58" wrote:

> Error : SQL server does not exist or access denied.
> We are replacing the box the SQL server resides on and we have set up the
> new server as a copy of the old one. It is a Win2000server with DNS and
> active directory.
> SQL server ver 8.00.760
> We are able to:
> Attach to the new server from workstations including exploring and
> mapping the drives (actually our old server mappings worked)
> We can establish an ODBC connection to the SQL server from the new box
> and it tests fine so the server is started and running.
> We were able to get one workstation to access the SQL server after
> enabling name pipes but another still could not.
> We are able to connect to the old DNS server and SQL server from all
> workstations with no difficlties. Only one of the servers is connected at at
> ime.
> We can not set up an ODBC connection from any other workstation attached to
> the new server. This is the error message we receive:
> Connection failed:
> SQL State 01000
> SQL Server error: 10060
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
> ()).
> Connection failed:
> SQL State 08001
> SQL Server error 17
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
> or access denied.
> There is no firewall in between the server and workstations (a fire wall
> resides between the server and the internet with NAT enabled).
> Login is set to use both windows and SQL authentication. We have tried it
> as SQL only login with the same error message.
> We have worked through Microsoft document 328306 "Potential causes of the
> "SQL Server does not exist or access denied" error message"
> Any ideas where our problem is?
> Thank you,
> Michael
|||Since you didn't provide any specifics (other than "exactly similar"), how
about:
http://support.microsoft.com/?kbid=328306
http://support.microsoft.com/?kbid=888228
http://www.aspfaq.com/
(Reverse address to reply.)
"Parag Gaikwad" <Parag Gaikwad@.discussions.microsoft.com> wrote in message
news:7F1BC52B-CF3E-4661-B50B-5DA4E460F666@.microsoft.com...
> Hi All,
> We are facing exactly similar problem. Does anyone have any idea/thoughts
as
> to why this could be happening and what we can do to troubleshoot/solve
this
> problem.
> Many Thanks,
> Parag

Error : SQL server does not exist or access denied.

Error : SQL server does not exist or access denied.
We are replacing the box the SQL server resides on and we have set up the
new server as a copy of the old one. It is a Win2000server with DNS and
active directory.
SQL server ver 8.00.760
We are able to:
Attach to the new server from workstations including exploring and
mapping the drives (actually our old server mappings worked)
We can establish an ODBC connection to the SQL server from the new box
and it tests fine so the server is started and running.
We were able to get one workstation to access the SQL server after
enabling name pipes but another still could not.
We are able to connect to the old DNS server and SQL server from all
workstations with no difficlties. Only one of the servers is connected at at
ime.
We can not set up an ODBC connection from any other workstation attached to
the new server. This is the error message we receive:
Connection failed:
SQL State 01000
SQL Server error: 10060
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
()).
Connection failed:
SQL State 08001
SQL Server error 17
[Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
or access denied.
There is no firewall in between the server and workstations (a fire wall
resides between the server and the internet with NAT enabled).
Login is set to use both windows and SQL authentication. We have tried it
as SQL only login with the same error message.
We have worked through Microsoft document 328306 "Potential causes of the
"SQL Server does not exist or access denied" error message"
Any ideas where our problem is?
Thank you,
MichaelHi All,
We are facing exactly similar problem. Does anyone have any idea/thoughts as
to why this could be happening and what we can do to troubleshoot/solve this
problem.
Many Thanks,
Parag
"MABrown58" wrote:
> Error : SQL server does not exist or access denied.
> We are replacing the box the SQL server resides on and we have set up the
> new server as a copy of the old one. It is a Win2000server with DNS and
> active directory.
> SQL server ver 8.00.760
> We are able to:
> Attach to the new server from workstations including exploring and
> mapping the drives (actually our old server mappings worked)
> We can establish an ODBC connection to the SQL server from the new box
> and it tests fine so the server is started and running.
> We were able to get one workstation to access the SQL server after
> enabling name pipes but another still could not.
> We are able to connect to the old DNS server and SQL server from all
> workstations with no difficlties. Only one of the servers is connected at at
> ime.
> We can not set up an ODBC connection from any other workstation attached to
> the new server. This is the error message we receive:
> Connection failed:
> SQL State 01000
> SQL Server error: 10060
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] Connectionopen (Connect
> ()).
> Connection failed:
> SQL State 08001
> SQL Server error 17
> [Microsoft][ODBC SQL Server driver[tcp/ip sockets] SQL Server does not exist
> or access denied.
> There is no firewall in between the server and workstations (a fire wall
> resides between the server and the internet with NAT enabled).
> Login is set to use both windows and SQL authentication. We have tried it
> as SQL only login with the same error message.
> We have worked through Microsoft document 328306 "Potential causes of the
> "SQL Server does not exist or access denied" error message"
> Any ideas where our problem is?
> Thank you,
> Michael|||Since you didn't provide any specifics (other than "exactly similar"), how
about:
http://support.microsoft.com/?kbid=328306
http://support.microsoft.com/?kbid=888228
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Parag Gaikwad" <Parag Gaikwad@.discussions.microsoft.com> wrote in message
news:7F1BC52B-CF3E-4661-B50B-5DA4E460F666@.microsoft.com...
> Hi All,
> We are facing exactly similar problem. Does anyone have any idea/thoughts
as
> to why this could be happening and what we can do to troubleshoot/solve
this
> problem.
> Many Thanks,
> Parag

Error "The OLE DB provider "MSDASQL" has not been registered." on SQL 2005 6

Hi,
I am trying to create a linked server from SQL server 2005 (64bit) to IB 7.5 database.

I installed the driver for IB on SQL box and created a System DNS (using
%SystemRoot%\SysWOW64\odbcad32.exe), tested the connection fine.

Now, on SQL Management Studio, created a linked server to use the System DSN,
sp_addlinkedserver 'MyLinkedSrv', ' ', 'MSDASQL', 'MySYSDNS' -- went fine.

Then ran the openquery,
select * from OPENQUERY(MyLinkedSrv, 'select * from services')

An error msg returned fro the openquery.
The OLE DB provider "MSDASQL" has not been registered.

What am I missing here? I tried with "Native SQL Client" instead MSDASQL but it returns me invaild parameters...

Any advice on this would be aprreciated.

Regards,
Sunny

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=396615&SiteID=1

HTH