Installed SQL 2000 on a completely up to date windows 2003 advanced server,
then applied sp3a, then I installed reporting service developer addition,
then installed VS .net 2003 the reinstalled reporting services to get the
Report Developer.
Now I can't connect to the Server using EM.
I Get "SQL_alloc_handle on SQL_handle_env failed"
Tried all types of registrations.
Seems to be some sort of ODBC problem since I can attach to the database
remotely from access.
Any suggestions short of starting from scratch?I haven't encountered this particular problem, but I'd suggest you could try
re-intalling the SQL client tools only & see if that solves your problems.
Regards,
Greg Linwood
SQL Server MVP
"sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
news:OB0VFOO9DHA.2944@.TK2MSFTNGP11.phx.gbl...
> Installed SQL 2000 on a completely up to date windows 2003 advanced
server,
> then applied sp3a, then I installed reporting service developer addition,
> then installed VS .net 2003 the reinstalled reporting services to get the
> Report Developer.
> Now I can't connect to the Server using EM.
> I Get "SQL_alloc_handle on SQL_handle_env failed"
> Tried all types of registrations.
> Seems to be some sort of ODBC problem since I can attach to the database
> remotely from access.
> Any suggestions short of starting from scratch?
>|||Thanks, I will give it a try.
"Greg Linwood" <g_linwoodQhotmail.com> wrote in message
news:eYlgmYO9DHA.2656@.TK2MSFTNGP11.phx.gbl...
> I haven't encountered this particular problem, but I'd suggest you could
try
> re-intalling the SQL client tools only & see if that solves your problems.
> Regards,
> Greg Linwood
> SQL Server MVP
> "sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
> news:OB0VFOO9DHA.2944@.TK2MSFTNGP11.phx.gbl...
> > Installed SQL 2000 on a completely up to date windows 2003 advanced
> server,
> > then applied sp3a, then I installed reporting service developer
addition,
> > then installed VS .net 2003 the reinstalled reporting services to get
the
> > Report Developer.
> >
> > Now I can't connect to the Server using EM.
> >
> > I Get "SQL_alloc_handle on SQL_handle_env failed"
> >
> > Tried all types of registrations.
> >
> > Seems to be some sort of ODBC problem since I can attach to the database
> > remotely from access.
> >
> > Any suggestions short of starting from scratch?
> >
> >
>|||I solved the problem. Installing VS.net 2003 overwrote the ODBC and SQL
related DLL's in the windows\system32 directory. Restoring them fixed the
problem.
"Greg Linwood" <g_linwoodQhotmail.com> wrote in message
news:eYlgmYO9DHA.2656@.TK2MSFTNGP11.phx.gbl...
> I haven't encountered this particular problem, but I'd suggest you could
try
> re-intalling the SQL client tools only & see if that solves your problems.
> Regards,
> Greg Linwood
> SQL Server MVP
> "sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
> news:OB0VFOO9DHA.2944@.TK2MSFTNGP11.phx.gbl...
> > Installed SQL 2000 on a completely up to date windows 2003 advanced
> server,
> > then applied sp3a, then I installed reporting service developer
addition,
> > then installed VS .net 2003 the reinstalled reporting services to get
the
> > Report Developer.
> >
> > Now I can't connect to the Server using EM.
> >
> > I Get "SQL_alloc_handle on SQL_handle_env failed"
> >
> > Tried all types of registrations.
> >
> > Seems to be some sort of ODBC problem since I can attach to the database
> > remotely from access.
> >
> > Any suggestions short of starting from scratch?
> >
> >
>|||Thanks for the feedback
Regards,
Greg Linwood
SQL Server MVP
"sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
news:eHipkUyAEHA.3988@.tk2msftngp13.phx.gbl...
> I solved the problem. Installing VS.net 2003 overwrote the ODBC and SQL
> related DLL's in the windows\system32 directory. Restoring them fixed the
> problem.
> "Greg Linwood" <g_linwoodQhotmail.com> wrote in message
> news:eYlgmYO9DHA.2656@.TK2MSFTNGP11.phx.gbl...
> > I haven't encountered this particular problem, but I'd suggest you could
> try
> > re-intalling the SQL client tools only & see if that solves your
problems.
> >
> > Regards,
> > Greg Linwood
> > SQL Server MVP
> >
> > "sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
> > news:OB0VFOO9DHA.2944@.TK2MSFTNGP11.phx.gbl...
> > > Installed SQL 2000 on a completely up to date windows 2003 advanced
> > server,
> > > then applied sp3a, then I installed reporting service developer
> addition,
> > > then installed VS .net 2003 the reinstalled reporting services to get
> the
> > > Report Developer.
> > >
> > > Now I can't connect to the Server using EM.
> > >
> > > I Get "SQL_alloc_handle on SQL_handle_env failed"
> > >
> > > Tried all types of registrations.
> > >
> > > Seems to be some sort of ODBC problem since I can attach to the
database
> > > remotely from access.
> > >
> > > Any suggestions short of starting from scratch?
> > >
> > >
> >
> >
>
Showing posts with label manger. Show all posts
Showing posts with label manger. Show all posts
Thursday, March 22, 2012
Enterprise manger won't connect
Installed SQL 2000 on a completely up to date windows 2003 advanced server,
then applied sp3a, then I installed reporting service developer addition,
then installed VS .net 2003 the reinstalled reporting services to get the
Report Developer.
Now I can't connect to the Server using EM.
I Get "SQL_alloc_handle on SQL_handle_env failed"
Tried all types of registrations.
Seems to be some sort of ODBC problem since I can attach to the database
remotely from access.
Any suggestions short of starting from scratch?I haven't encountered this particular problem, but I'd suggest you could try
re-intalling the SQL client tools only & see if that solves your problems.
Regards,
Greg Linwood
SQL Server MVP
"sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
news:OB0VFOO9DHA.2944@.TK2MSFTNGP11.phx.gbl...
> Installed SQL 2000 on a completely up to date windows 2003 advanced
server,
> then applied sp3a, then I installed reporting service developer addition,
> then installed VS .net 2003 the reinstalled reporting services to get the
> Report Developer.
> Now I can't connect to the Server using EM.
> I Get "SQL_alloc_handle on SQL_handle_env failed"
> Tried all types of registrations.
> Seems to be some sort of ODBC problem since I can attach to the database
> remotely from access.
> Any suggestions short of starting from scratch?
>|||Thanks, I will give it a try.
"Greg Linwood" <g_linwoodQhotmail.com> wrote in message
news:eYlgmYO9DHA.2656@.TK2MSFTNGP11.phx.gbl...
> I haven't encountered this particular problem, but I'd suggest you could
try
> re-intalling the SQL client tools only & see if that solves your problems.
> Regards,
> Greg Linwood
> SQL Server MVP
> "sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
> news:OB0VFOO9DHA.2944@.TK2MSFTNGP11.phx.gbl...
> server,
addition,
the
>|||I solved the problem. Installing VS.net 2003 overwrote the ODBC and SQL
related DLL's in the windows\system32 directory. Restoring them fixed the
problem.
"Greg Linwood" <g_linwoodQhotmail.com> wrote in message
news:eYlgmYO9DHA.2656@.TK2MSFTNGP11.phx.gbl...
> I haven't encountered this particular problem, but I'd suggest you could
try
> re-intalling the SQL client tools only & see if that solves your problems.
> Regards,
> Greg Linwood
> SQL Server MVP
> "sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
> news:OB0VFOO9DHA.2944@.TK2MSFTNGP11.phx.gbl...
> server,
addition,
the
>|||Thanks for the feedback
Regards,
Greg Linwood
SQL Server MVP
"sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
news:eHipkUyAEHA.3988@.tk2msftngp13.phx.gbl...
> I solved the problem. Installing VS.net 2003 overwrote the ODBC and SQL
> related DLL's in the windows\system32 directory. Restoring them fixed the
> problem.
> "Greg Linwood" <g_linwoodQhotmail.com> wrote in message
> news:eYlgmYO9DHA.2656@.TK2MSFTNGP11.phx.gbl...
> try
problems.
> addition,
> the
database
>
then applied sp3a, then I installed reporting service developer addition,
then installed VS .net 2003 the reinstalled reporting services to get the
Report Developer.
Now I can't connect to the Server using EM.
I Get "SQL_alloc_handle on SQL_handle_env failed"
Tried all types of registrations.
Seems to be some sort of ODBC problem since I can attach to the database
remotely from access.
Any suggestions short of starting from scratch?I haven't encountered this particular problem, but I'd suggest you could try
re-intalling the SQL client tools only & see if that solves your problems.
Regards,
Greg Linwood
SQL Server MVP
"sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
news:OB0VFOO9DHA.2944@.TK2MSFTNGP11.phx.gbl...
> Installed SQL 2000 on a completely up to date windows 2003 advanced
server,
> then applied sp3a, then I installed reporting service developer addition,
> then installed VS .net 2003 the reinstalled reporting services to get the
> Report Developer.
> Now I can't connect to the Server using EM.
> I Get "SQL_alloc_handle on SQL_handle_env failed"
> Tried all types of registrations.
> Seems to be some sort of ODBC problem since I can attach to the database
> remotely from access.
> Any suggestions short of starting from scratch?
>|||Thanks, I will give it a try.
"Greg Linwood" <g_linwoodQhotmail.com> wrote in message
news:eYlgmYO9DHA.2656@.TK2MSFTNGP11.phx.gbl...
> I haven't encountered this particular problem, but I'd suggest you could
try
> re-intalling the SQL client tools only & see if that solves your problems.
> Regards,
> Greg Linwood
> SQL Server MVP
> "sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
> news:OB0VFOO9DHA.2944@.TK2MSFTNGP11.phx.gbl...
> server,
addition,
the
>|||I solved the problem. Installing VS.net 2003 overwrote the ODBC and SQL
related DLL's in the windows\system32 directory. Restoring them fixed the
problem.
"Greg Linwood" <g_linwoodQhotmail.com> wrote in message
news:eYlgmYO9DHA.2656@.TK2MSFTNGP11.phx.gbl...
> I haven't encountered this particular problem, but I'd suggest you could
try
> re-intalling the SQL client tools only & see if that solves your problems.
> Regards,
> Greg Linwood
> SQL Server MVP
> "sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
> news:OB0VFOO9DHA.2944@.TK2MSFTNGP11.phx.gbl...
> server,
addition,
the
>|||Thanks for the feedback
Regards,
Greg Linwood
SQL Server MVP
"sdrexler" <sdrexler@.nospam.optonline.net> wrote in message
news:eHipkUyAEHA.3988@.tk2msftngp13.phx.gbl...
> I solved the problem. Installing VS.net 2003 overwrote the ODBC and SQL
> related DLL's in the windows\system32 directory. Restoring them fixed the
> problem.
> "Greg Linwood" <g_linwoodQhotmail.com> wrote in message
> news:eYlgmYO9DHA.2656@.TK2MSFTNGP11.phx.gbl...
> try
problems.
> addition,
> the
database
>
Enterprise Manger Error
I am getting an error:
MMC cannot open the file C:\program files\Miscorosft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
creted by a later version of MMC. This may also by because you do not have
sufficient access rights to the file.
I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
I did find that renaming the file to anything else will allow it to work.
Which makes for an easy enough work around but was wondering if anybody knew
what is going on?
TIA
Hi
Have you tried running MMC and opening the file from there?
Check the file permissions.
If you have EM on another machine you may want to try copying the file.
Alternatively may want to extract the MSC file from the original CD.
John
"Ken Rinaman" <go@.away.net> wrote in message
news:%23sPCyhiUEHA.2972@.TK2MSFTNGP12.phx.gbl...
> I am getting an error:
> MMC cannot open the file C:\program files\Miscorosft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
> This may be because the file does not exist, is not an MMC console, or was
> creted by a later version of MMC. This may also by because you do not have
> sufficient access rights to the file.
> I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
> I did find that renaming the file to anything else will allow it to work.
> Which makes for an easy enough work around but was wondering if anybody
knew
> what is going on?
> TIA
>
|||
> Have you tried running MMC and opening the file from there?
Yes, same error.
> Check the file permissions.
I have the ability to rename, delete, etc.
> If you have EM on another machine you may want to try copying the file.
> Alternatively may want to extract the MSC file from the original CD.
I did pull the file from the CD which is how I discovered changing the name
fixes the problem. On the CD the file is called SQLEM.msc if I copy that
file to my computer it runs fine. However if I rename it to SQL Server
Enterprise Manger.msc it no longer runs.
sql
MMC cannot open the file C:\program files\Miscorosft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
This may be because the file does not exist, is not an MMC console, or was
creted by a later version of MMC. This may also by because you do not have
sufficient access rights to the file.
I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
I did find that renaming the file to anything else will allow it to work.
Which makes for an easy enough work around but was wondering if anybody knew
what is going on?
TIA
Hi
Have you tried running MMC and opening the file from there?
Check the file permissions.
If you have EM on another machine you may want to try copying the file.
Alternatively may want to extract the MSC file from the original CD.
John
"Ken Rinaman" <go@.away.net> wrote in message
news:%23sPCyhiUEHA.2972@.TK2MSFTNGP12.phx.gbl...
> I am getting an error:
> MMC cannot open the file C:\program files\Miscorosft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC.
> This may be because the file does not exist, is not an MMC console, or was
> creted by a later version of MMC. This may also by because you do not have
> sufficient access rights to the file.
> I've tried uninstalling/reinstalling reapplying SP3a etc. with no luck.
> I did find that renaming the file to anything else will allow it to work.
> Which makes for an easy enough work around but was wondering if anybody
knew
> what is going on?
> TIA
>
|||
> Have you tried running MMC and opening the file from there?
Yes, same error.
> Check the file permissions.
I have the ability to rename, delete, etc.
> If you have EM on another machine you may want to try copying the file.
> Alternatively may want to extract the MSC file from the original CD.
I did pull the file from the CD which is how I discovered changing the name
fixes the problem. On the CD the file is called SQLEM.msc if I copy that
file to my computer it runs fine. However if I rename it to SQL Server
Enterprise Manger.msc it no longer runs.
sql
Enterprise Manger Crash Creating user
Please can you help with this?
I created a new users for the first time in SQL Server 2000. While doing
that, Enterprise Manager crashed...and:
1. If I try to add the user again, I get an error because the User already
exists...yet I cannot see it on the console.
2. The user name does not show under Users (or Roles)
Any idea what I need to do to fix it - or what I might be doing wrong?
Is there a problem with Enterprise manager, how can it be fixed? (Looks to
me like it fails while waiting for a response from NT...)Patrik
Open Query Analyzer and use
sp_adduser ,sp_dropuser system stored procedures
"Patrick" <Patrick@.discussions.microsoft.com> wrote in message
news:899B491A-819F-4435-9CF5-6E5EB47BB13C@.microsoft.com...
> Please can you help with this?
> I created a new users for the first time in SQL Server 2000. While
> doing
> that, Enterprise Manager crashed...and:
> 1. If I try to add the user again, I get an error because the User already
> exists...yet I cannot see it on the console.
> 2. The user name does not show under Users (or Roles)
> Any idea what I need to do to fix it - or what I might be doing wrong?
> Is there a problem with Enterprise manager, how can it be fixed? (Looks
> to
> me like it fails while waiting for a response from NT...)
>|||Thx.
Q. Does a SQL Server User Id have be created on the NT Server on which SQL
Server resides? Or can the NT user id be on another server?
"Uri Dimant" wrote:
> Patrik
> Open Query Analyzer and use
> sp_adduser ,sp_dropuser system stored procedures
>
>
>
> "Patrick" <Patrick@.discussions.microsoft.com> wrote in message
> news:899B491A-819F-4435-9CF5-6E5EB47BB13C@.microsoft.com...
>
>|||Patrick
Users and Logins are two different things
1)Logins are created to allow the person access to SQL Server .
2) Users are created to grant/allow access to the database/s located on the
server
http://vyaskn.tripod.com/sql_server...t_practices.htm --sec
urity
best practices
"Patrick" <Patrick@.discussions.microsoft.com> wrote in message
news:21715426-1674-48EE-A782-0709C183E456@.microsoft.com...[vbcol=seagreen]
> Thx.
> Q. Does a SQL Server User Id have be created on the NT Server on which
> SQL
> Server resides? Or can the NT user id be on another server?
> "Uri Dimant" wrote:
>
I created a new users for the first time in SQL Server 2000. While doing
that, Enterprise Manager crashed...and:
1. If I try to add the user again, I get an error because the User already
exists...yet I cannot see it on the console.
2. The user name does not show under Users (or Roles)
Any idea what I need to do to fix it - or what I might be doing wrong?
Is there a problem with Enterprise manager, how can it be fixed? (Looks to
me like it fails while waiting for a response from NT...)Patrik
Open Query Analyzer and use
sp_adduser ,sp_dropuser system stored procedures
"Patrick" <Patrick@.discussions.microsoft.com> wrote in message
news:899B491A-819F-4435-9CF5-6E5EB47BB13C@.microsoft.com...
> Please can you help with this?
> I created a new users for the first time in SQL Server 2000. While
> doing
> that, Enterprise Manager crashed...and:
> 1. If I try to add the user again, I get an error because the User already
> exists...yet I cannot see it on the console.
> 2. The user name does not show under Users (or Roles)
> Any idea what I need to do to fix it - or what I might be doing wrong?
> Is there a problem with Enterprise manager, how can it be fixed? (Looks
> to
> me like it fails while waiting for a response from NT...)
>|||Thx.
Q. Does a SQL Server User Id have be created on the NT Server on which SQL
Server resides? Or can the NT user id be on another server?
"Uri Dimant" wrote:
> Patrik
> Open Query Analyzer and use
> sp_adduser ,sp_dropuser system stored procedures
>
>
>
> "Patrick" <Patrick@.discussions.microsoft.com> wrote in message
> news:899B491A-819F-4435-9CF5-6E5EB47BB13C@.microsoft.com...
>
>|||Patrick
Users and Logins are two different things
1)Logins are created to allow the person access to SQL Server .
2) Users are created to grant/allow access to the database/s located on the
server
http://vyaskn.tripod.com/sql_server...t_practices.htm --sec
urity
best practices
"Patrick" <Patrick@.discussions.microsoft.com> wrote in message
news:21715426-1674-48EE-A782-0709C183E456@.microsoft.com...[vbcol=seagreen]
> Thx.
> Q. Does a SQL Server User Id have be created on the NT Server on which
> SQL
> Server resides? Or can the NT user id be on another server?
> "Uri Dimant" wrote:
>
Enterprise Manger CLOSES!
Hello everyone,
I have SQL server 2000 installed on Windows 2003 std
edition. The first time I opened E manager I was able to
right click on any database and go to properties to set
the location of transaction logs and so forth! The second
time I went into it I tried the same thing and now E
manager shuts down. It does the same thing to all the
databases. Does anyone know why this is happening. I have
sp3 installed...
GiacomoI don't know what happening but my be able to supply
information for you to find out.
The 2003 should contain logs of programs / services that
have started an stopped including SQL Server, so have a
chat to your 2003 Administrator to see if you can have a
look at them.
SQL Server also keeps a log, under the server - Managment -
SQL Server Logs have a look at that and see if it helps.
Run a trace and see what the server was doing before the
shut down.
J
>--Original Message--
>Hello everyone,
>I have SQL server 2000 installed on Windows 2003 std
>edition. The first time I opened E manager I was able to
>right click on any database and go to properties to set
>the location of transaction logs and so forth! The second
>time I went into it I tried the same thing and now E
>manager shuts down. It does the same thing to all the
>databases. Does anyone know why this is happening. I have
>sp3 installed...
>Giacomo
>.
>
I have SQL server 2000 installed on Windows 2003 std
edition. The first time I opened E manager I was able to
right click on any database and go to properties to set
the location of transaction logs and so forth! The second
time I went into it I tried the same thing and now E
manager shuts down. It does the same thing to all the
databases. Does anyone know why this is happening. I have
sp3 installed...
GiacomoI don't know what happening but my be able to supply
information for you to find out.
The 2003 should contain logs of programs / services that
have started an stopped including SQL Server, so have a
chat to your 2003 Administrator to see if you can have a
look at them.
SQL Server also keeps a log, under the server - Managment -
SQL Server Logs have a look at that and see if it helps.
Run a trace and see what the server was doing before the
shut down.
J
>--Original Message--
>Hello everyone,
>I have SQL server 2000 installed on Windows 2003 std
>edition. The first time I opened E manager I was able to
>right click on any database and go to properties to set
>the location of transaction logs and so forth! The second
>time I went into it I tried the same thing and now E
>manager shuts down. It does the same thing to all the
>databases. Does anyone know why this is happening. I have
>sp3 installed...
>Giacomo
>.
>
Wednesday, March 7, 2012
Enterprise Manager HANGS
For some strange reason we cannot connect to both our databases and
Enterprise manger hangs when we try loading it? anyone have any ideas?
___________________________
Giacomo
Hi,
2 reasons may be the cause:-
1. See if Autoclose option is enabled for the database. If it is enabled
then disable the database option. This option will close the database once
the last user logs off. So while connecting back it open the database back
again and take some time
2. This can be slow if you have more backup history. So delete the history
using:-
sp_delete_database_backuphistoXry (see books online)
Thanks
Hari
SQL Server MVP
"Giacomo" <gdagostino@.vision2000.ca> wrote in message
news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
> For some strange reason we cannot connect to both our databases and
> Enterprise manger hangs when we try loading it? anyone have any ideas?
> --
>
> ___________________________
> Giacomo
|||Giacomo
There was a problem like this with the early version of SQL Server 2000.
What service pack are you on? Have a look at this article, it may be your
problem.
http://support.microsoft.com/default...b;en-us;282416
Hope this helps
John
"Hari Prasad" wrote:
> Hi,
> 2 reasons may be the cause:-
> 1. See if Autoclose option is enabled for the database. If it is enabled
> then disable the database option. This option will close the database once
> the last user logs off. So while connecting back it open the database back
> again and take some time
> 2. This can be slow if you have more backup history. So delete the history
> using:-
> sp_delete_database_backuphistoXry (see books online)
> Thanks
> Hari
> SQL Server MVP
>
>
> "Giacomo" <gdagostino@.vision2000.ca> wrote in message
> news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
>
>
Enterprise manger hangs when we try loading it? anyone have any ideas?
___________________________
Giacomo
Hi,
2 reasons may be the cause:-
1. See if Autoclose option is enabled for the database. If it is enabled
then disable the database option. This option will close the database once
the last user logs off. So while connecting back it open the database back
again and take some time
2. This can be slow if you have more backup history. So delete the history
using:-
sp_delete_database_backuphistoXry (see books online)
Thanks
Hari
SQL Server MVP
"Giacomo" <gdagostino@.vision2000.ca> wrote in message
news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
> For some strange reason we cannot connect to both our databases and
> Enterprise manger hangs when we try loading it? anyone have any ideas?
> --
>
> ___________________________
> Giacomo
|||Giacomo
There was a problem like this with the early version of SQL Server 2000.
What service pack are you on? Have a look at this article, it may be your
problem.
http://support.microsoft.com/default...b;en-us;282416
Hope this helps
John
"Hari Prasad" wrote:
> Hi,
> 2 reasons may be the cause:-
> 1. See if Autoclose option is enabled for the database. If it is enabled
> then disable the database option. This option will close the database once
> the last user logs off. So while connecting back it open the database back
> again and take some time
> 2. This can be slow if you have more backup history. So delete the history
> using:-
> sp_delete_database_backuphistoXry (see books online)
> Thanks
> Hari
> SQL Server MVP
>
>
> "Giacomo" <gdagostino@.vision2000.ca> wrote in message
> news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
>
>
Enterprise Manager HANGS
For some strange reason we cannot connect to both our databases and
Enterprise manger hangs when we try loading it? anyone have any ideas?
--
___________________________
GiacomoHi,
2 reasons may be the cause:-
1. See if Autoclose option is enabled for the database. If it is enabled
then disable the database option. This option will close the database once
the last user logs off. So while connecting back it open the database back
again and take some time
2. This can be slow if you have more backup history. So delete the history
using:-
sp_delete_database_backuphisto_ry (see books online)
Thanks
Hari
SQL Server MVP
"Giacomo" <gdagostino@.vision2000.ca> wrote in message
news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
> For some strange reason we cannot connect to both our databases and
> Enterprise manger hangs when we try loading it? anyone have any ideas?
> --
>
> ___________________________
> Giacomo|||Giacomo
There was a problem like this with the early version of SQL Server 2000.
What service pack are you on? Have a look at this article, it may be your
problem.
http://support.microsoft.com/defaul...kb;en-us;282416
Hope this helps
John
"Hari Prasad" wrote:
> Hi,
> 2 reasons may be the cause:-
> 1. See if Autoclose option is enabled for the database. If it is enabled
> then disable the database option. This option will close the database once
> the last user logs off. So while connecting back it open the database back
> again and take some time
> 2. This can be slow if you have more backup history. So delete the history
> using:-
> sp_delete_database_backuphisto_ry (see books online)
> Thanks
> Hari
> SQL Server MVP
>
>
> "Giacomo" <gdagostino@.vision2000.ca> wrote in message
> news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
>
>
Enterprise manger hangs when we try loading it? anyone have any ideas?
--
___________________________
GiacomoHi,
2 reasons may be the cause:-
1. See if Autoclose option is enabled for the database. If it is enabled
then disable the database option. This option will close the database once
the last user logs off. So while connecting back it open the database back
again and take some time
2. This can be slow if you have more backup history. So delete the history
using:-
sp_delete_database_backuphisto_ry (see books online)
Thanks
Hari
SQL Server MVP
"Giacomo" <gdagostino@.vision2000.ca> wrote in message
news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
> For some strange reason we cannot connect to both our databases and
> Enterprise manger hangs when we try loading it? anyone have any ideas?
> --
>
> ___________________________
> Giacomo|||Giacomo
There was a problem like this with the early version of SQL Server 2000.
What service pack are you on? Have a look at this article, it may be your
problem.
http://support.microsoft.com/defaul...kb;en-us;282416
Hope this helps
John
"Hari Prasad" wrote:
> Hi,
> 2 reasons may be the cause:-
> 1. See if Autoclose option is enabled for the database. If it is enabled
> then disable the database option. This option will close the database once
> the last user logs off. So while connecting back it open the database back
> again and take some time
> 2. This can be slow if you have more backup history. So delete the history
> using:-
> sp_delete_database_backuphisto_ry (see books online)
> Thanks
> Hari
> SQL Server MVP
>
>
> "Giacomo" <gdagostino@.vision2000.ca> wrote in message
> news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
>
>
Enterprise Manager HANGS
For some strange reason we cannot connect to both our databases and
Enterprise manger hangs when we try loading it? anyone have any ideas?
--
___________________________
GiacomoHi,
2 reasons may be the cause:-
1. See if Autoclose option is enabled for the database. If it is enabled
then disable the database option. This option will close the database once
the last user logs off. So while connecting back it open the database back
again and take some time
2. This can be slow if you have more backup history. So delete the history
using:-
sp_delete_database_backuphistory (see books online)
Thanks
Hari
SQL Server MVP
"Giacomo" <gdagostino@.vision2000.ca> wrote in message
news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
> For some strange reason we cannot connect to both our databases and
> Enterprise manger hangs when we try loading it? anyone have any ideas?
> --
>
> ___________________________
> Giacomo|||Giacomo
There was a problem like this with the early version of SQL Server 2000.
What service pack are you on? Have a look at this article, it may be your
problem.
http://support.microsoft.com/default.aspx?scid=kb;en-us;282416
Hope this helps
John
"Hari Prasad" wrote:
> Hi,
> 2 reasons may be the cause:-
> 1. See if Autoclose option is enabled for the database. If it is enabled
> then disable the database option. This option will close the database once
> the last user logs off. So while connecting back it open the database back
> again and take some time
> 2. This can be slow if you have more backup history. So delete the history
> using:-
> sp_delete_database_backuphistoÂry (see books online)
> Thanks
> Hari
> SQL Server MVP
>
>
> "Giacomo" <gdagostino@.vision2000.ca> wrote in message
> news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
> > For some strange reason we cannot connect to both our databases and
> > Enterprise manger hangs when we try loading it? anyone have any ideas?
> > --
> >
> >
> >
> > ___________________________
> > Giacomo
>
>
Enterprise manger hangs when we try loading it? anyone have any ideas?
--
___________________________
GiacomoHi,
2 reasons may be the cause:-
1. See if Autoclose option is enabled for the database. If it is enabled
then disable the database option. This option will close the database once
the last user logs off. So while connecting back it open the database back
again and take some time
2. This can be slow if you have more backup history. So delete the history
using:-
sp_delete_database_backuphistory (see books online)
Thanks
Hari
SQL Server MVP
"Giacomo" <gdagostino@.vision2000.ca> wrote in message
news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
> For some strange reason we cannot connect to both our databases and
> Enterprise manger hangs when we try loading it? anyone have any ideas?
> --
>
> ___________________________
> Giacomo|||Giacomo
There was a problem like this with the early version of SQL Server 2000.
What service pack are you on? Have a look at this article, it may be your
problem.
http://support.microsoft.com/default.aspx?scid=kb;en-us;282416
Hope this helps
John
"Hari Prasad" wrote:
> Hi,
> 2 reasons may be the cause:-
> 1. See if Autoclose option is enabled for the database. If it is enabled
> then disable the database option. This option will close the database once
> the last user logs off. So while connecting back it open the database back
> again and take some time
> 2. This can be slow if you have more backup history. So delete the history
> using:-
> sp_delete_database_backuphistoÂry (see books online)
> Thanks
> Hari
> SQL Server MVP
>
>
> "Giacomo" <gdagostino@.vision2000.ca> wrote in message
> news:13AAF4E3-DF25-4839-B241-A573BA966E34@.microsoft.com...
> > For some strange reason we cannot connect to both our databases and
> > Enterprise manger hangs when we try loading it? anyone have any ideas?
> > --
> >
> >
> >
> > ___________________________
> > Giacomo
>
>
Subscribe to:
Posts (Atom)