Runtime error data provider or other service provided an efail status

Anyone knows what would cause this?When Enterprise Manager is used to open a table
Runtime error data provider or other service provided an efail status"Vincento Harris" <wumutek@.yahoo.com> wrote in message
news:2fa13ee7.0409220419.1d9dc812@.posting.google.c om...
> Anyone knows what would cause this?When Enterprise Manager is used to open
> a table
> Runtime error data provider or other service provided an efail status

It would be useful to know the exact error, however Google suggests that a
corrupt DLL may be one cause:

http://groups.google.com/groups?q=s...f=1&sa=N&tab=wg

Probably the easiest thing to do is uninstall then reinstall the client
tools, then apply the latest servicepack.

Simon

Runtime Error - Taskpad

When I change my view to "Taskpad" in Enterprise Manager,
and then click on each of the databases, I get a "Runtime
Error has occured. Do you want to debug". Has anyone
else encountered this problem and is there a fix?
Thanks,
PatrickIf you change it back to Large icons or another view, then back again, it
should work okay.
Also make sure you're at the latest service pack...
A
"Patrick Thorsell" <patrick_thorsell@.yahoo.com> wrote in message
news:024001c35528$142c82a0$a101280a@.phx.gbl...
> When I change my view to "Taskpad" in Enterprise Manager,
> and then click on each of the databases, I get a "Runtime
> Error has occured. Do you want to debug". Has anyone
> else encountered this problem and is there a fix?
> Thanks,
> Patrick|||Hmm why is there no MS articles about this? Anyone know
of a long term fix for this? the switching views is
surely just a work around.
Regards,
Yussuf Khan
>--Original Message--
>If you change it back to Large icons or another view,
then back again, it
>should work okay.
>Also make sure you're at the latest service pack...
>A
>
>"Patrick Thorsell" <patrick_thorsell@.yahoo.com> wrote in
message
>news:024001c35528$142c82a0$a101280a@.phx.gbl...
>> When I change my view to "Taskpad" in Enterprise
Manager,
>> and then click on each of the databases, I get
a "Runtime
>> Error has occured. Do you want to debug". Has anyone
>> else encountered this problem and is there a fix?
>> Thanks,
>> Patrick
>
>.
>|||This error still can occur in SP3, it happened to me about 2 minutes ago.
--
----
The views expressed here are my own
and not of my employer.
----
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:uKn6lJQXDHA.1680@.tk2msftngp13.phx.gbl...
> Since moving to SP3, I have never experienced the error. So if you're not
> at SP3, get there.
>
>
> "Yussuf Khan" <fearnan@.excite.com> wrote in message
> news:173301c35cfb$f3fc70e0$7d02280a@.phx.gbl...
> > Hmm why is there no MS articles about this? Anyone know
> > of a long term fix for this? the switching views is
> > surely just a work around.
> >
> > Regards,
> >
> > Yussuf Khan
>

Running under 64-bit OS

In configuration manager, the parameter "running under 64-bit os" is grayed out on my sql services.

How can you change this? Where does it get set? At install?

This can't be changed...it is set depending on the OS version and SQL Server bits you've installed. In order for it to be set, you'd need to be running a 64bit OS (IA64 or x64) and have the appropriate SQL server bits installed (IA64 SQL version or x64 SQL version)...

|||

I checked...the server is an Itanium 2 and the SQL Server software is definitely the IA64 version (select @.@.version output), but how can you tell if the OS is 64 bit?

According to the My Computer properties, I'm running Windows Server 2003 Enterprise Edition Version 5.2 SP1. No mention of 64 bit. Anywhere else I should look?

|||Looks like you are running the 32-bit OS version...if you had the Itanium or 64bit edition, it would specifically say so...|||I have SQL Server 2005 EE 64 bit installed on a 64 bit Server with Windows Server 2003 R2 Enterprise x64 Edition. However, the SQL Configuration Manager still shows No for the Running under 64 bit OS property. Any suggestions on what is going on? Thanks.|||I am also having this problem. We have Server 2003 Enterprise x64 Edition, and the SQL Server 2005 version is as follows:

Microsoft SQL Server 2005 - 9.00.2047.00 (X64) Apr 14 2006 01:11:53 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)

What gives?
|||

It turns out that the label is very confusing. There is a bug filed on it in the SQL bug database and it will hopefully get fixed in the future to make this clearer. It turns out that this field shows if you are running a 32-bit version of SQL under a 64-bit OS (as in WoW). I had an X64 machine here with a 64-bit instance of SQL and a 32-bit instance of SQL. The field shows "No" for the 64-bit version of SQL and "Yes" for the 32-bit version of SQL. A bit misleading, but "correct" if you look at it in this way. :)

Thanks,
Sam Lester (MSFT)

|||Thank you! I actually have only one 64-bit instance of SQL 2005 and several 32-bit instances of SQL 2000 on the server. No 32-bit instances of SQL 2005 are installed. I'll trust that it's running in 64-bit mode.

Running under 64-bit OS

In configuration manager, the parameter "running under 64-bit os" is grayed out on my sql services.

How can you change this? Where does it get set? At install?

This can't be changed...it is set depending on the OS version and SQL Server bits you've installed. In order for it to be set, you'd need to be running a 64bit OS (IA64 or x64) and have the appropriate SQL server bits installed (IA64 SQL version or x64 SQL version)...

|||

I checked...the server is an Itanium 2 and the SQL Server software is definitely the IA64 version (select @.@.version output), but how can you tell if the OS is 64 bit?

According to the My Computer properties, I'm running Windows Server 2003 Enterprise Edition Version 5.2 SP1. No mention of 64 bit. Anywhere else I should look?

|||Looks like you are running the 32-bit OS version...if you had the Itanium or 64bit edition, it would specifically say so...|||I have SQL Server 2005 EE 64 bit installed on a 64 bit Server with Windows Server 2003 R2 Enterprise x64 Edition. However, the SQL Configuration Manager still shows No for the Running under 64 bit OS property. Any suggestions on what is going on? Thanks.|||I am also having this problem. We have Server 2003 Enterprise x64 Edition, and the SQL Server 2005 version is as follows:

Microsoft SQL Server 2005 - 9.00.2047.00 (X64) Apr 14 2006 01:11:53 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 1)

What gives?|||

It turns out that the label is very confusing. There is a bug filed on it in the SQL bug database and it will hopefully get fixed in the future to make this clearer. It turns out that this field shows if you are running a 32-bit version of SQL under a 64-bit OS (as in WoW). I had an X64 machine here with a 64-bit instance of SQL and a 32-bit instance of SQL. The field shows "No" for the 64-bit version of SQL and "Yes" for the 32-bit version of SQL. A bit misleading, but "correct" if you look at it in this way. :)

Thanks,
Sam Lester (MSFT)

|||Thank you! I actually have only one 64-bit instance of SQL 2005 and several 32-bit instances of SQL 2000 on the server. No 32-bit instances of SQL 2005 are installed. I'll trust that it's running in 64-bit mode.

Running SQL Server at Home

Hi All,

I'm trying to run a copy of Enterprise Manager at home. I have a small wireless network and would like to install it on either one machine (stand-alone) or run it on my network.

The machine it is installed on is running Windows 2000 and the remote machine is running Windows XP Home <<< not sure if SQL Server will run on this.

I tried installing it previously as stand-alone on the Win2K machine, but kept getting a "Server not found or access denied" message whenever I tried to register or connect.

Any ideas on how best to set it up at home would be greatly appreciated.

Thanks,
TimCreate an entry for your sqlserver in hosts (or lmhosts) file. This should help with name/ip resolution. Also, it might be better to setup sqlserver in mixed mode (i.e. allow sql authentication).|||I hope you installed the SQL Server and not the client components alone. Probably, you accepted default values. When you register you can use one of the following: a dot (.), or (local) - including parenthesis - or your workstation computer name. All these are valid in a standalone computer.

Please check your registry under HKEY_LOCAL_MACHINE\Microsoft\MSSQLSERVER\SUPERSOCK ETNETLIB\NP and if the value is like \\.\pipe\sql\query then probably you accepted default value for Named Pipe as well as the instance. If you have decided to install this as an instance then you may see like \\.\pipe\<instance_name>\sql\query then probably you installed as a server.
Also under HKEY_LOCAL_MACHINE\Microsoft\MSSQLSERVER\SUPERSOCK ETNETLIB\TCP, you can determine the port number. If it is 1433 then you used default port.

Please make sure that MSSQLServer Service is running. You can check this through the Services.msc. If you do not see MSSQLServer Service then you have installed the client components only and install the server components. Start SQL Query Analyzer and enter any of the following:

Assumption: Your computer name is PRECAMBRIAN

1) .
2) (local)
3) PRECAMBRIAN
4) PRECAMBRIAN,1433 (or whatever port number is)
5) PRECAMBRIAN\InstanceName

Enter your SA account's password and you should be able to connect.

running sql on a different port

sql 2k, sp3a
For security reasons, I changed sql to run on a different port. I'm able to
get into Enterprise Manager and Query Analyzer just fine. However, when I
try to go into Object Manager in QA, I get a message that the connection has
been broken. It never allows me to see the objects. Is this a bug? Is
there a workaround?
As long as sql is running on port 1433 I can get into the object manager
just fine.
Thanks, Andrehave you tried creating an alias in client network utility and using the
alias to connect to the server?
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 programming by Example
"Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
news:eY8FrbtAEHA.1700@.TK2MSFTNGP12.phx.gbl...
> sql 2k, sp3a
> For security reasons, I changed sql to run on a different port. I'm able
to
> get into Enterprise Manager and Query Analyzer just fine. However, when I
> try to go into Object Manager in QA, I get a message that the connection
has
> been broken. It never allows me to see the objects. Is this a bug? Is
> there a workaround?
> As long as sql is running on port 1433 I can get into the object manager
> just fine.
> Thanks, Andre
>|||I have that in place.
"Carlos Eduardo Rojas" <carloser@.mindspring.com> wrote in message
news:uL07F9tAEHA.2112@.tk2msftngp13.phx.gbl...
> have you tried creating an alias in client network utility and using the
> alias to connect to the server?
> --
> Carlos E. Rojas
> SQL Server MVP
> Co-Author SQL Server 2000 programming by Example
>
> "Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
> news:eY8FrbtAEHA.1700@.TK2MSFTNGP12.phx.gbl...
able
> to
I
> has
>|||Actually, that worked. I'd created the alias but was still connecting to
'.'. Connecting to the alias was the trick. Thanks!
Andre
"Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
news:OcKVNbuAEHA.1964@.TK2MSFTNGP11.phx.gbl...
> I have that in place.
> "Carlos Eduardo Rojas" <carloser@.mindspring.com> wrote in message
> news:uL07F9tAEHA.2112@.tk2msftngp13.phx.gbl...
> able
when
> I
connection
Is
manager
>

running sql on a different port

sql 2k, sp3a
For security reasons, I changed sql to run on a different port. I'm able to
get into Enterprise Manager and Query Analyzer just fine. However, when I
try to go into Object Manager in QA, I get a message that the connection has
been broken. It never allows me to see the objects. Is this a bug? Is
there a workaround?
As long as sql is running on port 1433 I can get into the object manager
just fine.
Thanks, Andrehave you tried creating an alias in client network utility and using the
alias to connect to the server?
--
Carlos E. Rojas
SQL Server MVP
Co-Author SQL Server 2000 Programming by Example
"Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
news:eY8FrbtAEHA.1700@.TK2MSFTNGP12.phx.gbl...
> sql 2k, sp3a
> For security reasons, I changed sql to run on a different port. I'm able
to
> get into Enterprise Manager and Query Analyzer just fine. However, when I
> try to go into Object Manager in QA, I get a message that the connection
has
> been broken. It never allows me to see the objects. Is this a bug? Is
> there a workaround?
> As long as sql is running on port 1433 I can get into the object manager
> just fine.
> Thanks, Andre
>|||I have that in place.
"Carlos Eduardo Rojas" <carloser@.mindspring.com> wrote in message
news:uL07F9tAEHA.2112@.tk2msftngp13.phx.gbl...
> have you tried creating an alias in client network utility and using the
> alias to connect to the server?
> --
> Carlos E. Rojas
> SQL Server MVP
> Co-Author SQL Server 2000 Programming by Example
>
> "Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
> news:eY8FrbtAEHA.1700@.TK2MSFTNGP12.phx.gbl...
> > sql 2k, sp3a
> >
> > For security reasons, I changed sql to run on a different port. I'm
able
> to
> > get into Enterprise Manager and Query Analyzer just fine. However, when
I
> > try to go into Object Manager in QA, I get a message that the connection
> has
> > been broken. It never allows me to see the objects. Is this a bug? Is
> > there a workaround?
> >
> > As long as sql is running on port 1433 I can get into the object manager
> > just fine.
> >
> > Thanks, Andre
> >
> >
>|||Actually, that worked. I'd created the alias but was still connecting to
'.'. Connecting to the alias was the trick. Thanks!
Andre
"Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
news:OcKVNbuAEHA.1964@.TK2MSFTNGP11.phx.gbl...
> I have that in place.
> "Carlos Eduardo Rojas" <carloser@.mindspring.com> wrote in message
> news:uL07F9tAEHA.2112@.tk2msftngp13.phx.gbl...
> > have you tried creating an alias in client network utility and using the
> > alias to connect to the server?
> >
> > --
> > Carlos E. Rojas
> > SQL Server MVP
> > Co-Author SQL Server 2000 Programming by Example
> >
> >
> > "Andre" <AndreGetsEnoughSPAM@.nospam.com> wrote in message
> > news:eY8FrbtAEHA.1700@.TK2MSFTNGP12.phx.gbl...
> > > sql 2k, sp3a
> > >
> > > For security reasons, I changed sql to run on a different port. I'm
> able
> > to
> > > get into Enterprise Manager and Query Analyzer just fine. However,
when
> I
> > > try to go into Object Manager in QA, I get a message that the
connection
> > has
> > > been broken. It never allows me to see the objects. Is this a bug?
Is
> > > there a workaround?
> > >
> > > As long as sql is running on port 1433 I can get into the object
manager
> > > just fine.
> > >
> > > Thanks, Andre
> > >
> > >
> >
> >
>