ClR Function errror cant get to lcoal file system

My users complain that they cant run a CLR function. I am told that it cant get access to the local file system. I do not how to code these so from SSIS is there any way to let the users gain access to this. If this is a permission issue what is the lease privilege that I can configure for this to work?

Thanks
AdminAnupHow are they connecting to SQL Server ? If you are using SQL Server authenitcation, they will use the SQL Server account permissions to access the files, if this one does not have any permissions, they will get a Access denied. The same situation if you are using Windows authentication and the individual users do not have access to the files. Did you try to run the function individually ? Which error do you get there if you try to let it run at a user context (and not probably one with administrative priviledges :-) )

Jens K. Suessmeyer.

http://www.sqlserver2005.de
|||it is using sql authentication.

Can you let me know which permission does sql authentication need to execute

and also if i change it to be windows does it need any admin privileges|||If you are using SQL Server Authentication, the SQL Server service account SQL Server is running with, will need to have rights on the accessed files / shares. If you are using Windows authentication, the logged in User wil need to have those rights.

Jens K. Suessmeyer

http://www.sqlserver2005.de
|||Has the CLR assembly been granted EXTERNAL_ACCESS?|||Yes that was it as it was in Safe mode
Thanks

close all existing connections and processes to a database

Dear all

I created this trigger on a table that i think failed while execution. I tried to modify it and run it again but it seems that i cant do that. If i try and delete the database i also cant - saying that it is still in use. But i am not using it and ther are no other users connected to it. I think the trigger has probably hit a loop and that is holding the link.

To close that i know that a solution would be to restart the SQL server instance but that would be a bit hard since the SQL server where my test database resides is a production server and has few other databases that are important and few users use them.

Is there any way through a SQL statement that there can be forced a delete? Or force close all the connections? Or force close all the processes without actually restarting the SQL server instance.

I have tried all options that were offered on some other forums like forcing it to a single user but even that operation can not be performed saying that the database is still in use.

Thank you so much for all your help and time.

Sincerely

Dan

You could cycle through the SPID's in master.dbo.sysprocess and KILL off any SPID's using the test database_id.

And then you have learned why you 'should' not 'play' on a production server. Create yourself a local server for experiementation and testing. Get an 'old', decommissioned desktop and convert it to a test server. There is no excuse for mucking up a production server.

clients sometimes get locked and can't write

I have an SQL 2000 back end. We have a couple of databases with about 12-20
tables a piece. About once or twice a month there are times for up to an
hour or so where no one can write from any of the front end applications to
the SQL 2000 back end. Each application gives their own error which all are
basically a time out waiting to write. Often times the system will just
start working again on its own.
When this happens the first thing we check in the Enterprise Manager is for
any locks and there are none. We then check to see if one of the other
applications like Access 2003, Labview or others can write to the database
and we see they cannot. Next we see if we can open the table on the SQL
server and edit or append and we CAN from the Enterprise Manager?
Thinking that there might be someone locking a record or a page we kick
everyone out and just let one person (sometimes myself as an admin) try to
work and they cannot. We then restart the SQL server and the workstations
and have someone try again and they still fail.
The only thing that I have seen help get it out of this state is when I go
to my daily maintenance jobs and run both my integrity check and my
optimization plan. The Integrety Check plan was done with the wizard and
it:
1. Checks the integrity of all user database
2. Includes indexes
3. Attempts to repair minor problems.
4. Run every day at 12:00 AM
The Optimization plan is set to:
1. Reorganize Data and Index Pages
2. Change free space to 10%
3. Run every day at 1:30 AM
Finally, when I look in the Event Viewer logs for anything strange I really
do not see anything in the app, security, or system logs anywhere near the
time of the start of the errors.
Sounds like the SQL Server Agents for the SQL Server instances aren't
running sometimes. Goto start->administrative tools->services and
look for the SQL Server Agent (your server instance name) entries and
see their status. Should be in "Started" state. If not started,
click on the entry and click start in top left corner of pane.
SQL Server Agents are the programs that act as proxies to enable
remote access to a SQL server instance. If they are not running,
nobody will be able to gain access to the server, and will receive
time out errors instead.
Some programs, such as backups, may stop the agents so they can take a
snapshot of the database. These programs should start the agents as
soon as they are done. If you find the agents in a stopped state in
the next outage, you should try to trace down what program was
executing at the time they were stopped, and check if that program is
configured properly.
|||I don't think it is the agent because the users are able to read the data
remotely. Also, the only maintenance that is done is done at 1-3 AM. This
problem happens randomly mid day.
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:e1159a72-4a2a-449d-a8d7-d22be76d6595@.q78g2000hsh.googlegroups.com...
> Sounds like the SQL Server Agents for the SQL Server instances aren't
> running sometimes. Goto start->administrative tools->services and
> look for the SQL Server Agent (your server instance name) entries and
> see their status. Should be in "Started" state. If not started,
> click on the entry and click start in top left corner of pane.
> SQL Server Agents are the programs that act as proxies to enable
> remote access to a SQL server instance. If they are not running,
> nobody will be able to gain access to the server, and will receive
> time out errors instead.
> Some programs, such as backups, may stop the agents so they can take a
> snapshot of the database. These programs should start the agents as
> soon as they are done. If you find the agents in a stopped state in
> the next outage, you should try to trace down what program was
> executing at the time they were stopped, and check if that program is
> configured properly.
>
>
>

clients sometimes get locked and can't write

I have an SQL 2000 back end. We have a couple of databases with about 12-20
tables a piece. About once or twice a month there are times for up to an
hour or so where no one can write from any of the front end applications to
the SQL 2000 back end. Each application gives their own error which all are
basically a time out waiting to write. Often times the system will just
start working again on its own.
When this happens the first thing we check in the Enterprise Manager is for
any locks and there are none. We then check to see if one of the other
applications like Access 2003, Labview or others can write to the database
and we see they cannot. Next we see if we can open the table on the SQL
server and edit or append and we CAN from the Enterprise Manager'
Thinking that there might be someone locking a record or a page we kick
everyone out and just let one person (sometimes myself as an admin) try to
work and they cannot. We then restart the SQL server and the workstations
and have someone try again and they still fail.
The only thing that I have seen help get it out of this state is when I go
to my daily maintenance jobs and run both my integrity check and my
optimization plan. The Integrety Check plan was done with the wizard and
it:
1. Checks the integrity of all user database
2. Includes indexes
3. Attempts to repair minor problems.
4. Run every day at 12:00 AM
The Optimization plan is set to:
1. Reorganize Data and Index Pages
2. Change free space to 10%
3. Run every day at 1:30 AM
Finally, when I look in the Event Viewer logs for anything strange I really
do not see anything in the app, security, or system logs anywhere near the
time of the start of the errors.Sounds like the SQL Server Agents for the SQL Server instances aren't
running sometimes. Goto start->administrative tools->services and
look for the SQL Server Agent (your server instance name) entries and
see their status. Should be in "Started" state. If not started,
click on the entry and click start in top left corner of pane.
SQL Server Agents are the programs that act as proxies to enable
remote access to a SQL server instance. If they are not running,
nobody will be able to gain access to the server, and will receive
time out errors instead.
Some programs, such as backups, may stop the agents so they can take a
snapshot of the database. These programs should start the agents as
soon as they are done. If you find the agents in a stopped state in
the next outage, you should try to trace down what program was
executing at the time they were stopped, and check if that program is
configured properly.|||I don't think it is the agent because the users are able to read the data
remotely. Also, the only maintenance that is done is done at 1-3 AM. This
problem happens randomly mid day.
"Andy" <anedza@.infotek-consulting.com> wrote in message
news:e1159a72-4a2a-449d-a8d7-d22be76d6595@.q78g2000hsh.googlegroups.com...
> Sounds like the SQL Server Agents for the SQL Server instances aren't
> running sometimes. Goto start->administrative tools->services and
> look for the SQL Server Agent (your server instance name) entries and
> see their status. Should be in "Started" state. If not started,
> click on the entry and click start in top left corner of pane.
> SQL Server Agents are the programs that act as proxies to enable
> remote access to a SQL server instance. If they are not running,
> nobody will be able to gain access to the server, and will receive
> time out errors instead.
> Some programs, such as backups, may stop the agents so they can take a
> snapshot of the database. These programs should start the agents as
> soon as they are done. If you find the agents in a stopped state in
> the next outage, you should try to trace down what program was
> executing at the time they were stopped, and check if that program is
> configured properly.
>
>
>

client.exe

Hi
I'd like to find client.exe tool to simulate SQL load.
I have technet & MSDN subscription but can't find it. Where can I download
it ?
Also what tools can I use for SQL load simulation instead client.exe ?
I am not sure what client.exe is, but I have a list of load testing tools
at: http://vyaskn.tripod.com/analyzing_profiler_output.htm
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Jan" <jedec@.email.si> wrote in message
news:e54YW$9TFHA.3280@.TK2MSFTNGP09.phx.gbl...
Hi
I'd like to find client.exe tool to simulate SQL load.
I have technet & MSDN subscription but can't find it. Where can I download
it ?
Also what tools can I use for SQL load simulation instead client.exe ?

client side

how does one install client side from MSDE? Developer told us we need to install client side so he can configure database links. I can't find anything on it in MSDE 2000 Release A.
I dont understand what you meant by client side? If it is to access the MSDE
database through ADO/ADO.NET/ASP code then all you would need is MDAC 2.6.
That would be a part of normal Windows OS itself. If you are interested in
tools to access and use MSDE as Enterprise Manager etc then you can always
use third party tools for the same.
HTH,
Vinod Kumar
MCSE, DBA, MCAD, MCSD
http://www.extremeexperts.com
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
"steve" <anonymous@.discussions.microsoft.com> wrote in message
news:0931AC39-990A-4543-AEE0-52417600280A@.microsoft.com...
> how does one install client side from MSDE? Developer told us we need to
install client side so he can configure database links. I can't find
anything on it in MSDE 2000 Release A.
|||It sounds like he meant to install an instance of MSDE on the "client" e.g.
whatever is running the application that requires a database. I assume he
meant this, rather than having the database hosted on a separate machine.
If this is the case, then run MSDE setup on the client machine, rather than
on a server.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"steve" <anonymous@.discussions.microsoft.com> wrote in message
news:0931AC39-990A-4543-AEE0-52417600280A@.microsoft.com...
> how does one install client side from MSDE? Developer told us we need to
> install client side so he can configure database links. I can't find
> anything on it in MSDE 2000 Release A.
|||yes, I think this is what he wants, that the msde components are installed for the application to be able to use them. WHen I use the current MSDE 2000 release a, it doesn't give me an option of installing anything but the MSDE SQL server side. is there
a command line, file or something that we need to be able to install the client side? He told me that he hasn't used the current MSDE 2000 Service release a yet, but that in prior versions and SQL one has the option of just installing the application /
client side. Thanks in advance - Steve
|||> MSDE 2000 release a, it doesn't give me an option of installing anything
but the MSDE SQL server side.
You're thinking about this entirely in the wrong way. What your other
people are suggesting is that you treat the client as the server. So, if
you run MSDE setup on the client, it is the server. MSDE doesn't understand
what you mean by "server side"... wherever it installs, that is the server!
Now, think about the app. The app lives on the client. Install MSDE on the
machine that is running the app. Now you have a client-side MSDE install.
Pretty simple, huh?

> has the option of just installing the application / client side.
He is confused as well. Maybe he is thinking about client tools (Enterprise
Manager, Query Analyzer) which is an installation option, but client tools
don't ship with MSDE at all so it wouldn't be relevant in this case.
Re-read the above paragraph and let me know if I need to clarify further.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||hi Steve,
"steve" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:23DA0332-ACC4-4A13-82CD-604671210454@.microsoft.com...
> yes, I think this is what he wants, that the msde components are installed
for the application to be able to use them. WHen I use the current MSDE
2000 release a, it doesn't give me an option of installing anything but the
MSDE SQL server side. is there a command line, file or something that we
need to be able to install the client side? He told me that he hasn't used
the current MSDE 2000 Service release a yet, but that in prior versions and
SQL one has the option of just installing the application / client side.
Thanks in advance - Steve
MSDE insatalls only as a whole package and there has never been a Client
Components Setup for it, only just for SQL Server...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||First - thank you for the replies.
I am at a loss then what it is that he needs. MSDE 2000 SRa is installed on a Windows 2000 Advanced Server that I set up for this. He then installed the database onto that computer and I created a VPN so he could use his Enterprise Tools remotely to make
some configuration changes. The application that interfaces with it he built on a VB / Access97 platform. He said the client side was needed to link the application to the MSDE server and that he was having trouble linking it but that they were some oth
er ways he could try. His suggestion was that I install the "client side" items on the workstation that was going to be running the VB / Access97 user interface. While I am MS certified, in prior jobs I haven't worked much with SQL server at the install
ation phase but have rather supported the interfaces after they were written and installed by the programers. I apologize for my lack of understanding and use of wrong syntax. We've used this programmer for years and everything else he has done has been
sucessful. Perhaps he isn't able to explain what it is that he wants.
-- Andrea Montanari wrote: --
hi Steve,
"steve" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:23DA0332-ACC4-4A13-82CD-604671210454@.microsoft.com...
> yes, I think this is what he wants, that the msde components are installed
for the application to be able to use them. WHen I use the current MSDE
2000 release a, it doesn't give me an option of installing anything but the
MSDE SQL server side. is there a command line, file or something that we
need to be able to install the client side? He told me that he hasn't used
the current MSDE 2000 Service release a yet, but that in prior versions and
SQL one has the option of just installing the application / client side.
Thanks in advance - Steve
MSDE insatalls only as a whole package and there has never been a Client
Components Setup for it, only just for SQL Server...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi Steve,
"steve" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:8EBB34FC-64EC-4B21-9221-73CDECEF9DC0@.microsoft.com...
> First - thank you for the replies.
> I am at a loss then what it is that he needs. MSDE 2000 SRa is installed
on a Windows 2000
> Advanced Server that I set up for this. He then installed the database
onto that computer and I created
> a VPN so he could use his Enterprise Tools remotely to make some
configuration changes. The
> application that interfaces with it he built on a VB / Access97 platform.
He said the client side was
> needed to link the application to the MSDE server and that he was having
trouble linking it but that
> they were some other ways he could try. His suggestion was that I install
the "client side" items on the
> workstation that was going to be running the VB / Access97 user interface.
While I am MS certified,
> in prior jobs I haven't worked much with SQL server at the installation
phase but have rather supported
> the interfaces after they were written and installed by the programers. I
apologize for my lack of
> understanding and use of wrong syntax. We've used this programmer for
years and everything else
> he has done has been sucessful. Perhaps he isn't able to explain what it
is that he wants.
usually, at client side, you shoul'd only install MDAC that provides the
client side dirvers and interfaces to connect to remote SQL Server/MSDE
instances...
what your guy intended is not wrong at all, becouse he indicates to install
the Client Components for SQL Server, that includes MDAC and the whole tools
as Enterprise Manager, Query Analyzer and so on to manage SQL Server
instances.. this is fine as long as you own a full SQL Server edition that
license you to do it, while MSDE only provides a server side setup with no
management tools bu oSql.exe, a command line tool
(http://support.microsoft.com/default...;EN-US;q325003)
you reported the client application is a VB / Access97 platform... then you
are only required to install VB/Access runtime dependencies and MDAC on the
clients... or just VB/Access runtime dependencies on the server... as long
as the app =;-)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||thank you. Steve

client logins

How come when I make a SQL Server login that login can't be used to login
from my C# application (OLEDBConnection.Open()) or the properties menu
wizard.
Randy
If Windows logins work and SQL logins do not then the server
may be set to Windows Authentication only. You also need to
make sure that you also add the login as a user to whatever
database the app is using and the database user needs the
appropriate permissions. But it could be a lot of different
things. Without any specific error message, it's all just a
guess.
-Sue
SQL Server MVP
On Tue, 4 Apr 2006 19:34:01 -0700, rseedle
<rseedle@.discussions.microsoft.com> wrote:

>How come when I make a SQL Server login that login can't be used to login
>from my C# application (OLEDBConnection.Open()) or the properties menu
>wizard.
>Randy

Client cant connect to server

We have installed a SQL 2000 server on a windows xp-pro machine and succesfully installed DotNetNuke. Now is the problem that there is no way we can manage to get a client connected. We have tried everything, changing tcp port, setting permissions, changing registry according to document 307197 in the microsoft database and nothing helps.
The only thing we can see is that in the serverlog we get a message stating that "SuperSocket Info : Bind failed on TCP port 1433". Can anyone help?
Regards Ulla & TomI assume you mean MSDE since SQL Server itself won't run on XP Pro. Have you looked at these yet:
http://support.microsoft.com/kb/293107/EN-US/
http://support.microsoft.com/kb/312935/
Have you checked to see if anything else is listening on port 1433? Have you tried using SQL on another port?
Jeff|||first thanx for yor reply - but no - I do mean Microsoft SQL Server 2000 Enterprise (evaluation version) - and it does run on an XP pro SP2 machine...
I am able to connect to the server locally by eg running my DotNetNuke portal and access it via http, but I cant access the portal from other computers in my home network.
I did have a look at the docs you mention. Regarding doc 293107 I have shot down all other software running on the server and it dosnt help. I checked the TCP ports with TCPVIEW and found nothing utilizing port 1433. I also changed the default TCP port for the server.
Regarding doc 312935: this does not refer to the same error message that I receive, however in lack of other good ideas I will try to get hold of the file from MS containing the fix fo that problem....
I hope you have other good ideas to fix my problem......|||

ujep wrote:

I do mean Microsoft SQL Server 2000 Enterprise(evaluation version) - and it does run on an XP pro SP2machine...

Are you 100% certain about that? Do you have a reference? Anything I have ever seen (e.g.Choosing an Edition of SQL Server 2000 andA Comparison of SQL Server 2000 with Access 2000) indicates that Windows XP can only run these versions of SQL Server 2000: Personal, Developer, and Desktop.
|||I downloaded the server from MS herehttp://www.microsoft.com/downloads/details.aspx?FamilyID=d20ba6e1-f44c-4781-a6bb-f60e02dc1335&DisplayLang=en , the documentation states that it can run on XP...
the welcome picture in setup states that this is a Windows 2000 server Enterprise edition....
I still havent found a fix for the problem, hope someone can help|||

ujep wrote:

I am able to connect to the server locally by eg running my DotNetNuke portal and access it via http, but I cant access the portal from other computers in my home network.

Most likely a firewall or security policy issue then. Though I wouldn't think you'd get the SQL port error, since DNN doesn't need to cross the network to reach a local SQL server and the clinet systems don't access SQL directly. Try a simple Hello World HTMP and ASPX page from the clients.
Jeff|||I am able to open html and aspx pages from the cliens - the only thing I can't do is open DNN - so if the problem is a security policy issue then it should then be within the server (or DNN) -|||

Yeah, but DNN works on the server itself, so it isn't a DNN or server problem either. When you opne DNN on the server, can you use the FQDN name justa s you would on the client, or are you just able to use "localhost"?

Jeff

Client can't be connected.

Hi,
I want to connect my win-XP client with win-server-2003 SQL Server.
I had done following task-
- I had installed SQL-2000 (Ent. Edition) on Win-Server 2003. And it is
successfully installed.
- In Win-S-2003 with the help of Active Directory I created domain and
created user on it.
- Client computer (Win-XP Prof.) configured with domain system. and I can
successfully login on that computer as a administrator.
- On client computer installed Sql-2000 (Ent. Edition) client tool.
- In Client Network Utility Configured my SQL Server
- In Enterprise Manager I done new registration with following configuration
-- Connect using = window authontication
-- Here I found following error : SQL Server does not exist or
access denied Connection Open(Connect())
Please help me to connect my client.
Hardik.
Hi
Can you connect to SQL Server, though EM, from the SQL Server console?
If not, is SQL Server running?
Can the client ping the SQL Server server?
Regards
Mike
"Hardik Shah" wrote:

> Hi,
> I want to connect my win-XP client with win-server-2003 SQL Server.
> I had done following task-
> - I had installed SQL-2000 (Ent. Edition) on Win-Server 2003. And it is
> successfully installed.
> - In Win-S-2003 with the help of Active Directory I created domain and
> created user on it.
> - Client computer (Win-XP Prof.) configured with domain system. and I can
> successfully login on that computer as a administrator.
> - On client computer installed Sql-2000 (Ent. Edition) client tool.
> - In Client Network Utility Configured my SQL Server
> - In Enterprise Manager I done new registration with following configuration
> -- Connect using = window authontication
> -- Here I found following error : SQL Server does not exist or
> access denied Connection Open(Connect())
> Please help me to connect my client.
>
> Hardik.
>
>
|||Hi,
Thanks for your reply.
I don't know how ping work . Please tell me how can client ping the SQL
Server
Hardik Shah
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:99ED019E-B7C0-473F-90D2-1AB2B7C059FC@.microsoft.com...[vbcol=seagreen]
> Hi
> Can you connect to SQL Server, though EM, from the SQL Server console?
> If not, is SQL Server running?
> Can the client ping the SQL Server server?
> Regards
> Mike
> "Hardik Shah" wrote:
can[vbcol=seagreen]
configuration[vbcol=seagreen]
|||Yes, I tried to ping my server it run successfully..
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> wrote in message
news:99ED019E-B7C0-473F-90D2-1AB2B7C059FC@.microsoft.com...[vbcol=seagreen]
> Hi
> Can you connect to SQL Server, though EM, from the SQL Server console?
> If not, is SQL Server running?
> Can the client ping the SQL Server server?
> Regards
> Mike
> "Hardik Shah" wrote:
can[vbcol=seagreen]
configuration[vbcol=seagreen]

Client can't access SQL Server

Hi,
one of my database is running in SQL6.5, Windows NT.
Some times clients can not access the server due to
unknown reason.Even at server side using Enterprise
Manager and or ISQL_w we are not able connect to the
server. When we are trying to connect to the server there
is no error/warning message, it seems SQL Server hang. At
this situation we are not able to stop SQL services
using "Net stop", control panel services, and even we are
not able to kill the SQL processes from Task Manager.
Since there is no message in the Error Log, Event Log we
are not able to findout root cause of the problem.
Everytime we are rebooting the Windows NT server to solve
the problem.
Anyone knows what could be the root cause of the
problem?
Thanks & Regards,
Raja.Please post fursther informationen SP and Windows evrioment... What about
the momory and processor usage ?
Jens Süßmeyer.
"Raja" <NilaRaja@.yahoo.com> schrieb im Newsbeitrag
news:075501c37d92$11296a90$a401280a@.phx.gbl...
> Hi,
> one of my database is running in SQL6.5, Windows NT.
> Some times clients can not access the server due to
> unknown reason.Even at server side using Enterprise
> Manager and or ISQL_w we are not able connect to the
> server. When we are trying to connect to the server there
> is no error/warning message, it seems SQL Server hang. At
> this situation we are not able to stop SQL services
> using "Net stop", control panel services, and even we are
> not able to kill the SQL processes from Task Manager.
> Since there is no message in the Error Log, Event Log we
> are not able to findout root cause of the problem.
> Everytime we are rebooting the Windows NT server to solve
> the problem.
> Anyone knows what could be the root cause of the
> problem?
> Thanks & Regards,
> Raja.
>|||Exactly the sam thing is happening from time to time on our 6.5 servers. And
the only thing we can do about that is rebooting the box. Memory, and
processor usage are as usual...
Peja
"Jens Süßmeyer" <jsuessmeyer@.[REJECT_SPAM]web.de> wrote in message
news:epMN5RafDHA.2484@.TK2MSFTNGP09.phx.gbl...
> Please post fursther informationen SP and Windows evrioment... What about
> the momory and processor usage ?
> Jens Süßmeyer.
>
> "Raja" <NilaRaja@.yahoo.com> schrieb im Newsbeitrag
> news:075501c37d92$11296a90$a401280a@.phx.gbl...
> > Hi,
> >
> > one of my database is running in SQL6.5, Windows NT.
> > Some times clients can not access the server due to
> > unknown reason.Even at server side using Enterprise
> > Manager and or ISQL_w we are not able connect to the
> > server. When we are trying to connect to the server there
> > is no error/warning message, it seems SQL Server hang. At
> > this situation we are not able to stop SQL services
> > using "Net stop", control panel services, and even we are
> > not able to kill the SQL processes from Task Manager.
> > Since there is no message in the Error Log, Event Log we
> > are not able to findout root cause of the problem.
> > Everytime we are rebooting the Windows NT server to solve
> > the problem.
> >
> > Anyone knows what could be the root cause of the
> > problem?
> >
> > Thanks & Regards,
> > Raja.
> >
> >
>