Showing posts with label failed. Show all posts
Showing posts with label failed. Show all posts

Thursday, March 22, 2012

Cannot delete SQL 2000 backup file

I have a .bak file that I am trying to delete because the backup failed due
to insufficient space on the disk drive. The message I get is that it is
in use by another person or program. I cannot find the person or program.
What should I be looking for? I use native SQL backup.
Message posted via http://www.sqlmonster.com
You may have to stop the SQLServerAgent service so that it will release the
file.
If that doesn't work (try the MSSQLServer service). One of the two is
holding on to the file.
Rick Sawtell
MCT, MCSD, MCDBA
"Debra Camacho-Padron via SQLMonster.com" <forum@.SQLMonster.com> wrote in
message news:2a3f51e677de49ec92f681f87f14936c@.SQLMonster.c om...
> I have a .bak file that I am trying to delete because the backup failed
due
> to insufficient space on the disk drive. The message I get is that it is
> in use by another person or program. I cannot find the person or program.
> What should I be looking for? I use native SQL backup.
> --
> Message posted via http://www.sqlmonster.com
|||That's what I thought too. I tried both, and it still indicates that the
file is in use.
Message posted via http://www.sqlmonster.com
|||Try using FileMon from sysinternals to see what is accessing
the file:
http://www.sysinternals.com/ntw2k/source/filemon.shtml
-Sue
On Tue, 15 Mar 2005 18:01:24 GMT, "Debra Camacho-Padron via
SQLMonster.com" <forum@.SQLMonster.com> wrote:

>That's what I thought too. I tried both, and it still indicates that the
>file is in use.

Cannot delete SQL 2000 backup file

I have a .bak file that I am trying to delete because the backup failed due
to insufficient space on the disk drive. The message I get is that it is
in use by another person or program. I cannot find the person or program.
What should I be looking for? I use native SQL backup.
Message posted via http://www.droptable.comYou may have to stop the SQLServerAgent service so that it will release the
file.
If that doesn't work (try the MSSQLServer service). One of the two is
holding on to the file.
Rick Sawtell
MCT, MCSD, MCDBA
"Debra Camacho-Padron via droptable.com" <forum@.droptable.com> wrote in
message news:2a3f51e677de49ec92f681f87f14936c@.SQ
droptable.com...
> I have a .bak file that I am trying to delete because the backup failed
due
> to insufficient space on the disk drive. The message I get is that it is
> in use by another person or program. I cannot find the person or program.
> What should I be looking for? I use native SQL backup.
> --
> Message posted via http://www.droptable.com|||That's what I thought too. I tried both, and it still indicates that the
file is in use.
Message posted via http://www.droptable.com|||Try using FileMon from sysinternals to see what is accessing
the file:
http://www.sysinternals.com/ntw2k/source/filemon.shtml
-Sue
On Tue, 15 Mar 2005 18:01:24 GMT, "Debra Camacho-Padron via
droptable.com" <forum@.droptable.com> wrote:

>That's what I thought too. I tried both, and it still indicates that the
>file is in use.

Cannot delete SQL 2000 backup file

I have a .bak file that I am trying to delete because the backup failed due
to insufficient space on the disk drive. The message I get is that it is
in use by another person or program. I cannot find the person or program.
What should I be looking for? I use native SQL backup.
--
Message posted via http://www.sqlmonster.comYou may have to stop the SQLServerAgent service so that it will release the
file.
If that doesn't work (try the MSSQLServer service). One of the two is
holding on to the file.
Rick Sawtell
MCT, MCSD, MCDBA
"Debra Camacho-Padron via SQLMonster.com" <forum@.SQLMonster.com> wrote in
message news:2a3f51e677de49ec92f681f87f14936c@.SQLMonster.com...
> I have a .bak file that I am trying to delete because the backup failed
due
> to insufficient space on the disk drive. The message I get is that it is
> in use by another person or program. I cannot find the person or program.
> What should I be looking for? I use native SQL backup.
> --
> Message posted via http://www.sqlmonster.com|||That's what I thought too. I tried both, and it still indicates that the
file is in use.
--
Message posted via http://www.sqlmonster.com|||Try using FileMon from sysinternals to see what is accessing
the file:
http://www.sysinternals.com/ntw2k/source/filemon.shtml
-Sue
On Tue, 15 Mar 2005 18:01:24 GMT, "Debra Camacho-Padron via
SQLMonster.com" <forum@.SQLMonster.com> wrote:
>That's what I thought too. I tried both, and it still indicates that the
>file is in use.

Wednesday, March 7, 2012

Cannot connect weird issue

Hello,
I am getting the following errors when I try to connect to SQL from a XP
workstation:
Connection Failed.
SQL State '01000'
SQL Server Error:10061
[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.
But when I connect from a different PC I can connect fine. I have changed
network cables and switch ports for this PC but still the same errors appear.
I can bring a laptop over to where the PC is that is having the problem,
unplug the pc from the network and plug the la[top in using same line and the
laptop will connect right up to the SQL server no problem.
TIA
Phil Andersen
There are some issues with Windows XP, you have to open the appropiate
ports:
841252 How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
Server 2000
839980 How to use a script to programmatically open ports for SQL Server to
use on systems that are running Windows XP Service Pack 2
839269 You may not be able to connect to an instance of SQL Server that is
configured to use the Named Pipes server network library on a computer that
is running Windows XP Service Pack 2
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Phil Andersen" <PhilAndersen@.discussions.microsoft.com> schrieb im
Newsbeitrag news:F546FC62-5C16-4ED3-889A-E4F541FC0953@.microsoft.com...
> Hello,
> I am getting the following errors when I try to connect to SQL from a XP
> workstation:
> Connection Failed.
> SQL State '01000'
> SQL Server Error:10061
> [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.
> But when I connect from a different PC I can connect fine. I have changed
> network cables and switch ports for this PC but still the same errors
> appear.
> I can bring a laptop over to where the PC is that is having the problem,
> unplug the pc from the network and plug the la[top in using same line and
> the
> laptop will connect right up to the SQL server no problem.
> TIA
> Phil Andersen
>
|||I am using service pack 1
"Jens Sü?meyer" wrote:

> There are some issues with Windows XP, you have to open the appropiate
> ports:
> 841252 How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
> Server 2000
>
> 839980 How to use a script to programmatically open ports for SQL Server to
> use on systems that are running Windows XP Service Pack 2
>
> 839269 You may not be able to connect to an instance of SQL Server that is
> configured to use the Named Pipes server network library on a computer that
> is running Windows XP Service Pack 2
>
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Phil Andersen" <PhilAndersen@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:F546FC62-5C16-4ED3-889A-E4F541FC0953@.microsoft.com...
>
>
|||ARe you sure you are using the same connection string ? Or with what kind of
program are you connecting ? If you have installed the client components yo
could try to make a broadcast for SQL Servers via OSL -L on the commandline.
There wasnt much information about your client components...
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Phil Andersen" <PhilAndersen@.discussions.microsoft.com> schrieb im
Newsbeitrag news:D324055E-80BD-40B7-9928-4E5C434E547D@.microsoft.com...[vbcol=seagreen]
>I am using service pack 1
>
> "Jens Smeyer" wrote:
|||OK in ODBC I switched from using TCP/IP to using NAMED PIPE and that made it
work. Still can't figure out why it all of the sudden needed this change and
only on like 5 machines out of 50
"Jens Sü?meyer" wrote:

> ARe you sure you are using the same connection string ? Or with what kind of
> program are you connecting ? If you have installed the client components yo
> could try to make a broadcast for SQL Servers via OSL -L on the commandline.
> There wasn′t much information about your client components...
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Phil Andersen" <PhilAndersen@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:D324055E-80BD-40B7-9928-4E5C434E547D@.microsoft.com...
>
>
|||Hi Phil,
There was a issue on that on the newsgroups, so i post it here (Thanks to
Ashwin Kowtha for that):
1)Ping the SQL Server by name. See if it returns an IP address
2)If the IP returned by Ping is not the same IP as should be, you have a
problem right there.
3) Check if you have any static entries for your SQL Server in your LMHOSTS
or HOSTS file on the
client.
4) If you do, make sure that the IP is mapped to the correct name and vice
versa.
5) Connections going through by IP and named pipes, so you have basic NT and
SQL connectivity.
Check with your NT network admins to see if Name Resolution is working well.
6) run Select @.@.servername on the SQL server and see if the correct name is
being returned.
7) Instead of using Dynamically determine port, if connecting to a default
instance, try giving
the actual port number SQL is listening on.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
"Phil Andersen" <PhilAndersen@.discussions.microsoft.com> schrieb im
Newsbeitrag news:248A248F-1D75-4837-B2C0-B1B362F62619@.microsoft.com...[vbcol=seagreen]
> OK in ODBC I switched from using TCP/IP to using NAMED PIPE and that made
> it
> work. Still can't figure out why it all of the sudden needed this change
> and
> only on like 5 machines out of 50
> "Jens Smeyer" wrote:

Cannot connect weird issue

Hello,
I am getting the following errors when I try to connect to SQL from a XP
workstation:
Connection Failed.
SQL State '01000'
SQL Server Error:10061
[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 do
es not exist
or access denied.
But when I connect from a different PC I can connect fine. I have changed
network cables and switch ports for this PC but still the same errors appear
.
I can bring a laptop over to where the PC is that is having the problem,
unplug the pc from the network and plug the la[top in using same line an
d the
laptop will connect right up to the SQL server no problem.
TIA
Phil AndersenThere are some issues with Windows XP, you have to open the appropiate
ports:
841252 How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
Server 2000
839980 How to use a script to programmatically open ports for SQL Server to
use on systems that are running Windows XP Service Pack 2
839269 You may not be able to connect to an instance of SQL Server that is
configured to use the Named Pipes server network library on a computer that
is running Windows XP Service Pack 2
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Phil Andersen" <PhilAndersen@.discussions.microsoft.com> schrieb im
Newsbeitrag news:F546FC62-5C16-4ED3-889A-E4F541FC0953@.microsoft.com...
> Hello,
> I am getting the following errors when I try to connect to SQL from a XP
> workstation:
> Connection Failed.
> SQL State '01000'
> SQL Server Error:10061
> [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.
> But when I connect from a different PC I can connect fine. I have changed
> network cables and switch ports for this PC but still the same errors
> appear.
> I can bring a laptop over to where the PC is that is having the problem,
> unplug the pc from the network and plug the la[top in using same line
and
> the
> laptop will connect right up to the SQL server no problem.
> TIA
> Phil Andersen
>|||I am using service pack 1
"Jens Sü?meyer" wrote:

> There are some issues with Windows XP, you have to open the appropiate
> ports:
> 841252 How to manually enable TCP/IP on Windows XP Service Pack 2 for SQL
> Server 2000
>
> 839980 How to use a script to programmatically open ports for SQL Server t
o
> use on systems that are running Windows XP Service Pack 2
>
> 839269 You may not be able to connect to an instance of SQL Server that is
> configured to use the Named Pipes server network library on a computer tha
t
> is running Windows XP Service Pack 2
>
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Phil Andersen" <PhilAndersen@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:F546FC62-5C16-4ED3-889A-E4F541FC0953@.microsoft.com...
>
>|||ARe you sure you are using the same connection string ? Or with what kind of
program are you connecting ? If you have installed the client components yo
could try to make a broadcast for SQL Servers via OSL -L on the commandline.
There wasnt much information about your client components...
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Phil Andersen" <PhilAndersen@.discussions.microsoft.com> schrieb im
Newsbeitrag news:D324055E-80BD-40B7-9928-4E5C434E547D@.microsoft.com...[vbcol=seagreen]
>I am using service pack 1
>
> "Jens Smeyer" wrote:
>|||OK in ODBC I switched from using TCP/IP to using NAMED PIPE and that made it
work. Still can't figure out why it all of the sudden needed this change and
only on like 5 machines out of 50
"Jens Sü?meyer" wrote:

> ARe you sure you are using the same connection string ? Or with what kind
of
> program are you connecting ? If you have installed the client components y
o
> could try to make a broadcast for SQL Servers via OSL -L on the commandlin
e.
> There wasn′t much information about your client components...
> --
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "Phil Andersen" <PhilAndersen@.discussions.microsoft.com> schrieb im
> Newsbeitrag news:D324055E-80BD-40B7-9928-4E5C434E547D@.microsoft.com...
>
>|||Hi Phil,
There was a issue on that on the newsgroups, so i post it here (Thanks to
Ashwin Kowtha for that):
1)Ping the SQL Server by name. See if it returns an IP address
2)If the IP returned by Ping is not the same IP as should be, you have a
problem right there.
3) Check if you have any static entries for your SQL Server in your LMHOSTS
or HOSTS file on the
client.
4) If you do, make sure that the IP is mapped to the correct name and vice
versa.
5) Connections going through by IP and named pipes, so you have basic NT and
SQL connectivity.
Check with your NT network admins to see if Name Resolution is working well.
6) run Select @.@.servername on the SQL server and see if the correct name is
being returned.
7) Instead of using Dynamically determine port, if connecting to a default
instance, try giving
the actual port number SQL is listening on.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"Phil Andersen" <PhilAndersen@.discussions.microsoft.com> schrieb im
Newsbeitrag news:248A248F-1D75-4837-B2C0-B1B362F62619@.microsoft.com...[vbcol=seagreen]
> OK in ODBC I switched from using TCP/IP to using NAMED PIPE and that made
> it
> work. Still can't figure out why it all of the sudden needed this change
> and
> only on like 5 machines out of 50
> "Jens Smeyer" wrote:
>

Thursday, February 16, 2012

cannot connect to sql 2005 from isql

I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
server, I can use sqlcmd to connect to the database. However, I failed
to connect to the database from a client machine using sql7's isql. The
error was
DB-Library: Unable to connect: SQL Server is unavailable or does not
exist.
Net-Library error 1326: ConnectionOpen (CreateFile()).
Please advise, thanks.Is the server instance listening to Named Pipes?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"AH" <hhhsu7a@.yahoo.com> wrote in message
news:1167102465.643393.154420@.73g2000cwn.googlegroups.com...
>I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
> server, I can use sqlcmd to connect to the database. However, I failed
> to connect to the database from a client machine using sql7's isql. The
> error was
> DB-Library: Unable to connect: SQL Server is unavailable or does not
> exist.
> Net-Library error 1326: ConnectionOpen (CreateFile()).
> Please advise, thanks.
>|||Hi
If this is SQL Express then network protocols are disabled by default. Check
which network protocols are being used, if necessary you may wish to create
an alias on the client to use TCP/IP to connect to the instance. Also make
sure that the client machine has the latest service packs.
John
"AH" wrote:
> I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
> server, I can use sqlcmd to connect to the database. However, I failed
> to connect to the database from a client machine using sql7's isql. The
> error was
> DB-Library: Unable to connect: SQL Server is unavailable or does not
> exist.
> Net-Library error 1326: ConnectionOpen (CreateFile()).
> Please advise, thanks.
>|||John,
I tried to open TCP on the server but still got the same error when
connecting from client machine. The client has SQL 7 SP2. Do I need to
go to SP 4?
Does Microsoft provide any tool to trace the connection?
Thanks,
Andy
John Bell wrote:
> Hi
> If this is SQL Express then network protocols are disabled by default. Check
> which network protocols are being used, if necessary you may wish to create
> an alias on the client to use TCP/IP to connect to the instance. Also make
> sure that the client machine has the latest service packs.
> John
>
> "AH" wrote:
> > I have a sql 2005 server runs on Windows 2003 Standard OS. On the same
> > server, I can use sqlcmd to connect to the database. However, I failed
> > to connect to the database from a client machine using sql7's isql. The
> > error was
> > DB-Library: Unable to connect: SQL Server is unavailable or does not
> > exist.
> > Net-Library error 1326: ConnectionOpen (CreateFile()).
> >
> > Please advise, thanks.
> >
> >

Sunday, February 12, 2012

Cannot connect to localhost

If I try to connect to localhost in the connection manager I get the error

"Test connection failed because of an error in initialising provider. Login timeout expired."

If I try to connect using server/instance in the connection mananger however, it connects just fine.

Any ideas?

Gary

hi Gary,

if you installed a named instance as it seems (server\Instance) you will not be able to just use "localhost".. you have to provide the full instance name, thus ServerName\InstanceName or "(Local)\InstanceName" or whatever... but the instancename must be provided as well..

regards

cannot connect to database: Login failed for user

Hello everyone,

When I try to connect to database I get this error message: Login failed for user 'databaseadmin'.

My connection code is:

Dim MyConnection As New SqlConnection( _
"server=(local); database=news; UID=databaseadmin; PWD=111111;")

I've tried "server=localhost:3066", and "server=." and many many other ways, but it's still not working! I don't know what other things should I try now... I asked the support people of my web host, and their answer is:"Mysql database usename and password is corect one. It seems that there is problem with the script code."

Please would anybody help me with this? Thank you very much!

If you are trying to connect to your web host's database server then the server should be something other than local. Also, you said the support people's answer is "Mysql database ...". You are using SQL Server not MySQL, right?

-Mike

|||Thank you so much for your reply!

Yes it is Microsoft SQL Server I'm using. The web host gave us some choice when adding a new database, and I also added another database which is using MySQL Server, and it didn't work neither...

Sorry I'm new to ASP.net, so I don't know what should I put for "server" if I'm working with the web host's database server? I tried to give it the IP address of my web host, but it didn't work...

Would you please give me some further assistance on the code? Thank you!|||For your information, after I login to phpMyAdmin I get this welcome message:

MySQL 4.1.7 running on localhost:3306 as databaseadmin@.localhost

Don't know whether this helps...
I'll really appreciate if someone could help me with this problem, thank you in advance!!|||Problem solved!

I've added a new MySQL database, and connected to that database using Odbc connection. And it's now working!!

cannot connect to database

i keep getting this error can anyone help me??

Cannot open database requested in login 'Match1'. Login fails. Login failed for user 'DURON\ASPNET'.

i used WINT Integrated security

code as following

Dim MySQL As String = "Insert into UserData ([UserName],[Password]) values (@.user, @.pass)"
Dim myConn As SqlConnection = New SqlConnection("data source=DURON\NETSDK;initial catalog=Match1;integrated security=SSPI;workstation id=DURON;packet size=4096")
Dim Cmd As New SqlCommand(MySQL, myConn)
Cmd.Parameters.Add(New SqlParameter("@.user", tbUser.Text))
Cmd.Parameters.Add(New SqlParameter("@.pass", tbPass1.Text))
myConn.Open()
Cmd.ExecuteNonQuery()You need to make DURON\ASPNET a user in SQL Server. Do you have Enterprise Manager?|||I do. I also have this problem.
settings:
winXP
iis5.1
sql2000 eval
mixed mode