EnumAvailableSqlServers() fails to detect LOCAL installed instance when disconnected from networ

I am using EnumAvailableSqlServer to build the standard select Sql Server dialog with controls to select the server, instance and database. This all works fine - other than the well reported problem of detected multiple instances - however I have noticed that when disconnected from the network the call fails to even detect the locally installed sql servers.

What is the recommended method of determine whether an instance of sql server is installed locally. I can call Server->Databases, but this leads to a timeout / excpetion if no instances are detected which is slow. Is there a recommended registry key I can check that won't change between versions or another API I can try.

hx, Nick

Checking registry seems the simplest ...

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

with InstalledInstances value.

Thx, Nick

EnumAvailableSqlServers() fails to detect LOCAL installed instance when disconnected from ne

I am using EnumAvailableSqlServer to build the standard select Sql Server dialog with controls to select the server, instance and database. This all works fine - other than the well reported problem of detected multiple instances - however I have noticed that when disconnected from the network the call fails to even detect the locally installed sql servers.

What is the recommended method of determine whether an instance of sql server is installed locally. I can call Server->Databases, but this leads to a timeout / excpetion if no instances are detected which is slow. Is there a recommended registry key I can check that won't change between versions or another API I can try.

hx, Nick

Checking registry seems the simplest ...

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server

with InstalledInstances value.

Thx, Nick

Entry point not found...mdt2fw.dll

I am having an SQL Server problem. I installed the Standard Edition of SQL Server 7 on a new server (Windows 2000 Server). When I open the SQL Server Enterprise Manager, I get errors when trying to open a database table.
The first error: The procedure entry point ? DaVinciVShowSQLVersionWarning@.@.YXGPAUHWND_@.@.@.Z could not be located in the dynamic link library mdt2fw.dll
The second error:An unexpected error happened during this operation. [MS Design Tools] - The specified procedure could not be found.
Any assistance in this matter would be greatly appreciated.
it could be a problem with a dll not being registered proplery. Try
registering that dll again using regsrv. However, you also might want to
read your sqlstp.log to check for any error messages duirng the install.
You'll find this in your WinNT folder.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
|||Thanks!
I will give it a try on Monday. Hopefully this will fix the problem.
Ray
"Ray" wrote:

> I am having an SQL Server problem. I installed the Standard Edition of SQL Server 7 on a new server (Windows 2000 Server). When I open the SQL Server Enterprise Manager, I get errors when trying to open a database table.
> The first error: The procedure entry point ? DaVinciVShowSQLVersionWarning@.@.YXGPAUHWND_@.@.@.Z could not be located in the dynamic link library mdt2fw.dll
> The second error:An unexpected error happened during this operation. [MS Design Tools] - The specified procedure could not be found.
> Any assistance in this matter would be greatly appreciated.
sql

Entry point not found...mdt2fw.dll

I am having an SQL Server problem. I installed the Standard Edition of SQL
Server 7 on a new server (Windows 2000 Server). When I open the SQL Server
Enterprise Manager, I get errors when trying to open a database table.
The first error: The procedure entry point ? DaVinciVShowSQLVersionWarning@.@.
YXGPAUHWND_@.@.@.Z could not be located in the dynamic link library mdt2fw.dll
The second error:An unexpected error happened during this operation. [MS
Design Tools] - The specified procedure could not be found.
Any assistance in this matter would be greatly appreciated.it could be a problem with a dll not being registered proplery. Try
registering that dll again using regsrv. However, you also might want to
read your sqlstp.log to check for any error messages duirng the install.
You'll find this in your WinNT folder.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||Thanks!
I will give it a try on Monday. Hopefully this will fix the problem.
Ray
"Ray" wrote:

> I am having an SQL Server problem. I installed the Standard Edition of SQ
L Server 7 on a new server (Windows 2000 Server). When I open the SQL Serve
r Enterprise Manager, I get errors when trying to open a database table.
> The first error: The procedure entry point ? DaVinciVShowSQLVersionWarning
@.@.YXGPAUHWND_@.@.@.Z could not be located in the dynamic link library mdt2fw.dl
l
> The second error:An unexpected error happened during this operation. [
MS Design Tools] - The specified procedure could not be found.
> Any assistance in this matter would be greatly appreciated.

Entry point not found...mdt2fw.dll

I am having an SQL Server problem. I installed the Standard Edition of SQL Server 7 on a new server (Windows 2000 Server). When I open the SQL Server Enterprise Manager, I get errors when trying to open a database table.
The first error: The procedure entry point ? DaVinciVShowSQLVersionWarning@.@.YXGPAUHWND_@.@.@.Z could not be located in the dynamic link library mdt2fw.dll
The second error:An unexpected error happened during this operation. [MS Design Tools] - The specified procedure could not be found.
Any assistance in this matter would be greatly appreciated.it could be a problem with a dll not being registered proplery. Try
registering that dll again using regsrv. However, you also might want to
read your sqlstp.log to check for any error messages duirng the install.
You'll find this in your WinNT folder.
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.|||Thanks!
I will give it a try on Monday. Hopefully this will fix the problem.
Ray
"Ray" wrote:
> I am having an SQL Server problem. I installed the Standard Edition of SQL Server 7 on a new server (Windows 2000 Server). When I open the SQL Server Enterprise Manager, I get errors when trying to open a database table.
> The first error: The procedure entry point ? DaVinciVShowSQLVersionWarning@.@.YXGPAUHWND_@.@.@.Z could not be located in the dynamic link library mdt2fw.dll
> The second error:An unexpected error happened during this operation. [MS Design Tools] - The specified procedure could not be found.
> Any assistance in this matter would be greatly appreciated.

entity relationship diagram

I have VS 2005 and SQL Server 2005 Express installed and I created 4 tables and setup the primary and foreign keys and can view the individual foreign key relationships by right clicking on the foreign key.

Is there a way to view a table relationship diagram (fields with primary and foreign keys), such as Access provides. Does VS 2005 or SQL Server 2005 have that capability?

Thanks

If you right-click on the folder named Database Diagrams, you can create a databse diagram. You can create a diagram here. To view the folder, click the plus sign next to the database that you want to create the diagram for.

Enterprise vs Standard edition

Hello,
I installed sql server 2000 Enterprise edition on one of
my servers. It is currently being used. I found out today
that I was supposed to use Standard edition due to
licensing.
Is there any way to back down to Standard edition without
uninstalling and reinstalling?
Thanks
SteveHi,
No , you cant. Only way is to remove Enterprise edition and install Standard
edition. But the other way is possible.
THanks
Hari
MCDBA
"Steve" <ee07@.yahoo.com> wrote in message
news:cfcb01c48aa7$f19e4730$a401280a@.phx.gbl...
> Hello,
> I installed sql server 2000 Enterprise edition on one of
> my servers. It is currently being used. I found out today
> that I was supposed to use Standard edition due to
> licensing.
> Is there any way to back down to Standard edition without
> uninstalling and reinstalling?
> Thanks
> Steve|||Nope. You can upgrade from Standard to Enterprise, but you can't downgrade.
Uninstall and reinstall is the only way unfortunately. You can backup your
databases from Enterprise and restore them on Standard though.
--
Jacco Schalkwijk
SQL Server MVP
"Steve" <ee07@.yahoo.com> wrote in message
news:cfcb01c48aa7$f19e4730$a401280a@.phx.gbl...
> Hello,
> I installed sql server 2000 Enterprise edition on one of
> my servers. It is currently being used. I found out today
> that I was supposed to use Standard edition due to
> licensing.
> Is there any way to back down to Standard edition without
> uninstalling and reinstalling?
> Thanks
> Steve

Enterprise vs Standard edition

Hello,
I installed sql server 2000 Enterprise edition on one of
my servers. It is currently being used. I found out today
that I was supposed to use Standard edition due to
licensing.
Is there any way to back down to Standard edition without
uninstalling and reinstalling?
Thanks
Steve
Hi,
No , you cant. Only way is to remove Enterprise edition and install Standard
edition. But the other way is possible.
THanks
Hari
MCDBA
"Steve" <ee07@.yahoo.com> wrote in message
news:cfcb01c48aa7$f19e4730$a401280a@.phx.gbl...
> Hello,
> I installed sql server 2000 Enterprise edition on one of
> my servers. It is currently being used. I found out today
> that I was supposed to use Standard edition due to
> licensing.
> Is there any way to back down to Standard edition without
> uninstalling and reinstalling?
> Thanks
> Steve
|||Nope. You can upgrade from Standard to Enterprise, but you can't downgrade.
Uninstall and reinstall is the only way unfortunately. You can backup your
databases from Enterprise and restore them on Standard though.
Jacco Schalkwijk
SQL Server MVP
"Steve" <ee07@.yahoo.com> wrote in message
news:cfcb01c48aa7$f19e4730$a401280a@.phx.gbl...
> Hello,
> I installed sql server 2000 Enterprise edition on one of
> my servers. It is currently being used. I found out today
> that I was supposed to use Standard edition due to
> licensing.
> Is there any way to back down to Standard edition without
> uninstalling and reinstalling?
> Thanks
> Steve
sql

Enterprise vs Standard edition

Hello,
I installed sql server 2000 Enterprise edition on one of
my servers. It is currently being used. I found out today
that I was supposed to use Standard edition due to
licensing.
Is there any way to back down to Standard edition without
uninstalling and reinstalling?
Thanks
SteveHi,
No , you cant. Only way is to remove Enterprise edition and install Standard
edition. But the other way is possible.
THanks
Hari
MCDBA
"Steve" <ee07@.yahoo.com> wrote in message
news:cfcb01c48aa7$f19e4730$a401280a@.phx.gbl...
> Hello,
> I installed sql server 2000 Enterprise edition on one of
> my servers. It is currently being used. I found out today
> that I was supposed to use Standard edition due to
> licensing.
> Is there any way to back down to Standard edition without
> uninstalling and reinstalling?
> Thanks
> Steve|||Nope. You can upgrade from Standard to Enterprise, but you can't downgrade.
Uninstall and reinstall is the only way unfortunately. You can backup your
databases from Enterprise and restore them on Standard though.
Jacco Schalkwijk
SQL Server MVP
"Steve" <ee07@.yahoo.com> wrote in message
news:cfcb01c48aa7$f19e4730$a401280a@.phx.gbl...
> Hello,
> I installed sql server 2000 Enterprise edition on one of
> my servers. It is currently being used. I found out today
> that I was supposed to use Standard edition due to
> licensing.
> Is there any way to back down to Standard edition without
> uninstalling and reinstalling?
> Thanks
> Steve

Enterprise vs Standard

After performing an Audit we discovered that my
predicessor inadvertantly installed a SQL 2000 Enterprise
Edition instead of Standard.
This weekend I will be upgrading to a new Server and wish
to use this window to convert to the proper version of
SQL 2000.
It is my understanding that you can upgrade Standard to
Enterprise but cannot perform the reverse.
My question is, are the System databases the same between
versions.
I realize that master.spt_server_info.attribute_id Value
2 would need to be changed (DBMS_VER) as well as
attribute 500 (SYS_SPROC_VERSION)
Other than that does any body know why I cannot do the
following.
1. Backup all Databases on Original Server.
2. Modify the DBMS_VER. and SYS_SPROC_VERSION.
2. Stop All SQL Services on Original Services.
3. Copy All mdf and ldf to a network storage local.
4. Shut down the Original Server.
5. Remove the Original Server from Active Directory.
6. Boot up the New Server with the original IP Address
and Computer name.
7. Install SQL 2000 Standard.
8. Install SP 3a.
9. Stop All SQL Services.
10. Copy all mdfs and ldfs from the network storage to
the proper folder on the new Server.
11. Restart the SQL services.
Does anyone see any major problems with this?
I know I could just attach the the Database but then I
would have to re-write all jobs and create all users in
the master DB providing the SID and Password. SID are not
a problem, but some of the Passwords may be difficult to
come by. (Damn my predisesor!).Your scheme should work, from an architectural standpoint. And it most
probably will. But it is not supported, so give yourself time to verify that
everything seems OK after the switch. You need to make sure that you have
the same directory structure for the SQL Server database files.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
"A Dubey" <adubey@.winstead.com> wrote in message
news:de1d01c40ae6$121701b0$a101280a@.phx.gbl...
> After performing an Audit we discovered that my
> predicessor inadvertantly installed a SQL 2000 Enterprise
> Edition instead of Standard.
> This weekend I will be upgrading to a new Server and wish
> to use this window to convert to the proper version of
> SQL 2000.
> It is my understanding that you can upgrade Standard to
> Enterprise but cannot perform the reverse.
> My question is, are the System databases the same between
> versions.
> I realize that master.spt_server_info.attribute_id Value
> 2 would need to be changed (DBMS_VER) as well as
> attribute 500 (SYS_SPROC_VERSION)
> Other than that does any body know why I cannot do the
> following.
> 1. Backup all Databases on Original Server.
> 2. Modify the DBMS_VER. and SYS_SPROC_VERSION.
> 2. Stop All SQL Services on Original Services.
> 3. Copy All mdf and ldf to a network storage local.
> 4. Shut down the Original Server.
> 5. Remove the Original Server from Active Directory.
> 6. Boot up the New Server with the original IP Address
> and Computer name.
> 7. Install SQL 2000 Standard.
> 8. Install SP 3a.
> 9. Stop All SQL Services.
> 10. Copy all mdfs and ldfs from the network storage to
> the proper folder on the new Server.
> 11. Restart the SQL services.
> Does anyone see any major problems with this?
> I know I could just attach the the Database but then I
> would have to re-write all jobs and create all users in
> the master DB providing the SID and Password. SID are not
> a problem, but some of the Passwords may be difficult to
> come by. (Damn my predisesor!).|||Thanks,
I felt like it would, Just wanted to get a little feed
back incase I was missing something.
AD
>--Original Message--
>Your scheme should work, from an architectural
standpoint. And it most
>probably will. But it is not supported, so give yourself
time to verify that
>everything seems OK after the switch. You need to make
sure that you have
>the same directory structure for the SQL Server database
files.
>--
>Tibor Karaszi, SQL Server MVP
>http://www.karaszi.com/sqlserver/default.asp
>
>"A Dubey" <adubey@.winstead.com> wrote in message
>news:de1d01c40ae6$121701b0$a101280a@.phx.gbl...
Enterprise
wish
between
Value
not
to
>
>.
>

Enterprise Publisher to Express Subscribers (2005)

I implemented a merge replication publication on a SQL Server 2005
Enterprise instance on a test server. On my laptop I have VS.NET 2005
installed with SQL Server 2005 Express.

It's my understanding that I can subscribe to a publication with
Express. I also have SQL Server Workgroup installed on my laptop so I'm
able to use Management Studio to control the Express instance.

The first issue I encountered was that you cannot subscribe to a
publication if you are not on the same network as the publishing
instance (it requires the actual server name). And in lieu of this I
tried to implement Web synchronization, but had problems with SSL
(which is my problem since I'm not entirely familiar with how to
implement SSL certs so they don't show the security warning on the
client without purchasing a certificate).

So then I decided to go ahead and create an account on my laptop and
add it to the domain of the test publishing server. I was then able to
subscribe to the published replication.

So then I look at my Express instance and the synchronization never
runs. In the documentation it says that you're supposed to be able to
right-click on the subscription and "View Synchronization" and force it
to run. This is not available in the Express instance, but it is
available in the Workgroup instance.

So I'm looking at cleaning up my web synchronization issues to make
that work, but I see two issues here.

1) Why do I have to specify the "real name" of the publishing database?
Why can't I access it like any other sql server via an IP address? This
seems like a highly restrictive implementation of replication to me.

2) Why do I have to implement SSL for replication? I understand the
need for security, but that should be left to me to implement. I
shouldn't be forced to use SSL as my security layer.

3) Why doesn't Express have "View Synchronization"?

Any help here is greatly appreciated.

David Cornelson

Hi David,
You should be able to use Web synchronization in your case.

Regarding your questions:
1) Not sure what you mean here. You need to have the actual and real publishing database name. Without it, we cannot know which database the subscription is referring to.

2) SSL is required for Web Synchronization. It is for Security Purposes. A security feature cannot be optional.

3) SQL Server Express does not have SQL Server Agent. Hence you do not have 'View Synchronization' (Workgroup has it and hence you see the option). You need to either use RMO or ActiveX sync components or use the Window Sync Manager to synchronizing.|||

re 1) So why can't I direct a subscriber to ipaddress\instanceName? Why does it have to be serverName\instanceName?

2) If all of my replication is done within my own company, say I have Smart Clients that are on different segments of my network, so they can't actually "see" the publishing database, I might want to use web synchronization and _not_ use SSL. You're making a security decision that I don't need. I understand that this should be default behaviour, but I should be able to turn it off. You're actually making my architecture more complex by forcing SSL into my replication strategy.

3) Where can I find information on Windows Sync Manager?

Thanks,

David C.

|||1) Not sure, but looks like there is no option for you to provide an ipaddress of the publisher to connect to. Servername/instance may be the only way.

2) Security is always a big concern and that is the reason for mandating the SSL. If you wish, you could workaround with a test certificate. MSDN has a tool for installing a test certificate.
For IIS6.0: http://www.microsoft.com/downloads/details.aspx?FamilyID=56fc92ee-a71a-4c73-b628-ade629c89499&displaylang=en
For IIS5.0: http://support.microsoft.com/default.aspx?scid=kb;en-us;228984

3) Windows Sync manager comes with Standard windows installation. Books online has more information about synchronizing using Sync Manager. To open Sync Manager follow either of the steps:
a) Windows Explorer-->Tools-->Synchronize
b) Start-->AllPrograms-->Accessories-->Synchronize|||1) Okay

2) Alright

3) It only has a Sql Server 2000 and an IE sync listed. Where's 2005?

Thanks for the help.

David C.|||3) I dont understand what you are saying. Where do you see SQL Server 2000 listed?
Windows sync manager is a windows mechanism for synchronization which can be launched using the 2 methods I described in my previous post. You have to enable the subscription on the Subscriber to be using the Windows Sync Manager. Once you have done that, you will start seeing the subscription in the Sync Manager and you can synchronize the subscription with the publication at the Publisher.

Enterprise Or Express Edition?

Hello. Through something called the MSDN Academic Alliance (MSDNAA), I installed what what they told me was going to be SQL Server 2005 Developer Edition. However, using the shared directory on their server, the installation program read "Enterprise Edition." Using a method found at KB article 321185, "How to identify your SQL Server version and edition," I finally figured out that I was using 9.00.1399.06/RTM/Express Edition.

Express Edition? The downloadable file at Microsoft is 55MB. My installation is over 500MB. Is there any way I can quickly check whether I have the Enterprise Edition? I have a feeling something in the installation was warped.

Example: How can I quickly do something that requires FULL-TEXT SEARCH?

Thanks.

Alex

If you do a select @.@. version it will tell your the SKU that you have installed.

Michelle

|||

Hello. Where would you do this? I did the following,

SELECT SERVERPROPERTY('productversion'), SERVERPROPERTY ('productlevel'), SERVERPROPERTY ('edition')

...under New Query and ran it. It gives me EXPRESS EDITION. Where would you type in your line -- and what exactly is it you want me to type?

Thanks!

Alex

|||

Can someone answer my question precisely, please? I really need this to get started. If it is the Express Edition I am working with, I have to uninstall and return the product; if the 500+ MB sitting in the directory are in fact the Enterprise Edition, then I can get to work.

|||

Yes the query you ran works fine. The alternative method is In a tsql window when you are connected to the server you would exectue "select @.@.version" which also gives you all the properties back in one string.

Yes you have Express Edition installed.

sql

Enterprise Mgr. Won't Open

Here's a strange thing: I've had this installed for years, and it was working fine up until last night, after I installed the latest MS security updates.
After re-booting from that installation, I have not been able to open Enterprise Manager. I get an error titled Microsoft Management Console, then it tells me it has encountered a problem and needs to close.
I've uninstalled and re-installed the SQL Server 2000 client tools, but still get the same error. I've worked around it by running mmc.exe and adding the SQL Server snap-in, but would really like to fix this problem.
I can run mmc.exe, but as soon as I try to open SQL Server Enterprise Manager.msc, mmc crashes.
My OS is WinXP pro, sp 1. Anyone have any idea what's going on?
Thanks for any assistance,
Tom
This is getting stranger. I tried renaming the SQL Server Enterprise Manager.MSC to SQLServerEnterpriseManager.MSC, and it opens without any problem.
What's that all about?
tom
|||Hi Tom,
From your description, I understand that you would like to know why your
SQL Server Enterprise Manager crashes after your updating some Windows
Security Updates. Have I understood the issue correctly and completely? If
there is anything I misunderstood, please feel free to let me know.
I would like to collect some information about it
1. Do you use Windows Updates to do some updates and what updates have you
installed?
2. You could find SQLEM.msc from your SQL Server Install Disk and please
copy it to your SQL Client installed disk
(from CDROM\Enterprise\x86\binn\SQLEM.msc to SQLInstalledDisk\80\Tools\Binn
as SQL Server Enterprise Manager.msc)
Try to do this and see whethere it could solve your problems
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Support
************************************************** *********
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.
|||Michael,
I responded several days ago to your last post, however for some
reason my response was not posted. Here is the gist of it: (I posted
again tonight in the web based group, and the message did not post,
I'm using another newsgroup reader for this post).
I used Windows Update to install the latest security patches (WinXP
Pro).
I did several things, including following your suggestions, however
the only way to open EM was to rename the file. I first accidentally
found this out when I copied the file SQL Server Enterprise
Manager.MSC as test.msc to another directory.
Double clicking that file opened it with no problems. I then renamed
it to SQLServerEnterpriseManager.MSC, and it opened fine. However, if
I try to open it as SQL Server Enterprise Manager.MSC (with the
spaces), I get the error: Microsoft Management Console has encountered
a problem and needs to close.
I can open the file from the installation media (SQLEM.MSC), but as
soon as I rename it to SQL Server Enterprise Manager.MSC I get the
error.
I have no idea why this might be happening.
Tom
On Thu, 15 Apr 2004 08:07:11 GMT, v-mingqc@.online.microsoft.com
("Michael, Cheng [MST]") wrote:

>Hi Tom,
>From your description, I understand that you would like to know why your
>SQL Server Enterprise Manager crashes after your updating some Windows
>Security Updates. Have I understood the issue correctly and completely? If
>there is anything I misunderstood, please feel free to let me know.
>I would like to collect some information about it
>1. Do you use Windows Updates to do some updates and what updates have you
>installed?
>2. You could find SQLEM.msc from your SQL Server Install Disk and please
>copy it to your SQL Client installed disk
>(from CDROM\Enterprise\x86\binn\SQLEM.msc to SQLInstalledDisk\80\Tools\Binn
>as SQL Server Enterprise Manager.msc)
>Try to do this and see whethere it could solve your problems
>Thank you for your patience and cooperation. If you have any questions or
>concerns, don't hesitate to let me know. We are here to be of assistance!
>Sincerely yours,
>Michael Cheng
>Microsoft Online Support
>************************************************* **********
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and confers no rights.
>Please reply to newsgroups only, many thanks.
>
|||Hi Tom,
Would you please try following steps:
1. When opening SQL Server Enterprise Manager.MSC in mmc.exe, trying to
give a quotation marks like "SQL Server Enterprise Manager.MSC" and see
whether it will work fine.
2. Would you please check your SQL Server and MDAC versions to ensure they
are the latest ones?
3. Deleting the C:\Documents and Settings\<user-id>\Application
Data\Microsoft\MMC\SQL Server Enterprise Manager
try to see whethere it will work fine?
4. If you rename the file with blanks, such as "SQL SEM.msc" will it still
work fine?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Support
************************************************** *********
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.
|||Michael,
Step #3 did the trick. Can you tell me what the problem was (i.e. why did it "break")?
Also, I'm hoping this posts on the newsgroup, as my posts lately don't seem to be "taking"...
Thanks for your help,
Tom
|||Hi Tom,
I am glad to hear that step #3 did the trick.
Based on my knowledge, on a Windows XP machine, the initial launch of SQL
Enterprise Manager creates a file (SQL Server Enterprise Manager) in
C:\Documents and Settings\<user-id>\Application Data\Microsoft\MMC.
Subsequent launches of Enterprise Manager use this file instead of the
original .msc file
Your Windows Security Updates or some other operations may make this file
corrupted. So you could not launch it unless you make it renamed. Renamed
file is recognized as new one, so it could be launched correctly.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Support
************************************************** *********
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.

Enterprise Mgr. Won't Open

Here's a strange thing: I've had this installed for years, and it was workin
g fine up until last night, after I installed the latest MS security updates
.
After re-booting from that installation, I have not been able to open Enterp
rise Manager. I get an error titled Microsoft Management Console, then it te
lls me it has encountered a problem and needs to close.
I've uninstalled and re-installed the SQL Server 2000 client tools, but stil
l get the same error. I've worked around it by running mmc.exe and adding th
e SQL Server snap-in, but would really like to fix this problem.
I can run mmc.exe, but as soon as I try to open SQL Server Enterprise Manage
r.msc, mmc crashes.
My OS is WinXP pro, sp 1. Anyone have any idea what's going on?
Thanks for any assistance,
TomThis is getting stranger. I tried renaming the SQL Server Enterprise Manager
.MSC to SQLServerEnterpriseManager.MSC, and it opens without any problem.
What's that all about?
tom|||Hi Tom,
From your description, I understand that you would like to know why your
SQL Server Enterprise Manager crashes after your updating some Windows
Security Updates. Have I understood the issue correctly and completely? If
there is anything I misunderstood, please feel free to let me know.
I would like to collect some information about it
1. Do you use Windows Updates to do some updates and what updates have you
installed?
2. You could find SQLEM.msc from your SQL Server Install Disk and please
copy it to your SQL Client installed disk
(from CDROM\Enterprise\x86\binn\SQLEM.msc to SQLInstalledDisk\80\Tools\Binn
as SQL Server Enterprise Manager.msc)
Try to do this and see whethere it could solve your problems
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Support
****************************************
*******************
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.|||Michael,
I responded several days ago to your last post, however for some
reason my response was not posted. Here is the gist of it: (I posted
again tonight in the web based group, and the message did not post,
I'm using another newsgroup reader for this post).
I used Windows Update to install the latest security patches (WinXP
Pro).
I did several things, including following your suggestions, however
the only way to open EM was to rename the file. I first accidentally
found this out when I copied the file SQL Server Enterprise
Manager.MSC as test.msc to another directory.
Double clicking that file opened it with no problems. I then renamed
it to SQLServerEnterpriseManager.MSC, and it opened fine. However, if
I try to open it as SQL Server Enterprise Manager.MSC (with the
spaces), I get the error: Microsoft Management Console has encountered
a problem and needs to close.
I can open the file from the installation media (SQLEM.MSC), but as
soon as I rename it to SQL Server Enterprise Manager.MSC I get the
error.
I have no idea why this might be happening.
Tom
On Thu, 15 Apr 2004 08:07:11 GMT, v-mingqc@.online.microsoft.com
("Michael, Cheng [MST]") wrote:

>Hi Tom,
>From your description, I understand that you would like to know why your
>SQL Server Enterprise Manager crashes after your updating some Windows
>Security Updates. Have I understood the issue correctly and completely? If
>there is anything I misunderstood, please feel free to let me know.
>I would like to collect some information about it
>1. Do you use Windows Updates to do some updates and what updates have you
>installed?
>2. You could find SQLEM.msc from your SQL Server Install Disk and please
>copy it to your SQL Client installed disk
>(from CDROM\Enterprise\x86\binn\SQLEM.msc to SQLInstalledDisk\80\Tools\Binn
>as SQL Server Enterprise Manager.msc)
>Try to do this and see whethere it could solve your problems
>Thank you for your patience and cooperation. If you have any questions or
>concerns, don't hesitate to let me know. We are here to be of assistance!
>Sincerely yours,
>Michael Cheng
>Microsoft Online Support
> ****************************************
*******************
>Get Secure! - www.microsoft.com/security
>This posting is provided "as is" with no warranties and confers no rights.
>Please reply to newsgroups only, many thanks.
>|||Hi Tom,
Would you please try following steps:
1. When opening SQL Server Enterprise Manager.MSC in mmc.exe, trying to
give a quotation marks like "SQL Server Enterprise Manager.MSC" and see
whether it will work fine.
2. Would you please check your SQL Server and MDAC versions to ensure they
are the latest ones?
3. Deleting the C:\Documents and Settings\<user-id>\Application
Data\Microsoft\MMC\SQL Server Enterprise Manager
try to see whethere it will work fine?
4. If you rename the file with blanks, such as "SQL SEM.msc" will it still
work fine?
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Support
****************************************
*******************
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.|||Michael,
Step #3 did the trick. Can you tell me what the problem was (i.e. why did it
"break")?
Also, I'm hoping this posts on the newsgroup, as my posts lately don't seem
to be "taking"...
Thanks for your help,
Tom|||Hi Tom,
I am glad to hear that step #3 did the trick.
Based on my knowledge, on a Windows XP machine, the initial launch of SQL
Enterprise Manager creates a file (SQL Server Enterprise Manager) in
C:\Documents and Settings\<user-id>\Application Data\Microsoft\MMC.
Subsequent launches of Enterprise Manager use this file instead of the
original .msc file
Your Windows Security Updates or some other operations may make this file
corrupted. So you could not launch it unless you make it renamed. Renamed
file is recognized as new one, so it could be launched correctly.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are here to be of assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Support
****************************************
*******************
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only, many thanks.sql

Enterprise Mgr Snap-In Issue

I have been running SQL Server 2000, client tools only.
i installed SQL Server Express (and associated .NET
framework upgrade) to take a look.
I then uninstalled sql server express and went back to
version 1.1 of .NET framework.
My query analyzer works fine, however when i try to load
Enterprise Manager, it says:
Snap-in failed to initialize.
Name: Microsoft SQL Enterprise Manager
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I have looked through the knowledge base articles and
have not found one specific to my situation.
I have uninstalled/reinstalled sql server 2000 (and
therefore, MDAC as well) and I am running into the same
issues.
Any help is appreciated.
Did you try regsvr32 c:\...\...\sqldmo.dll
http://www.aspfaq.com/
(Reverse address to reply.)
"RR" <anonymous@.discussions.microsoft.com> wrote in message
news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
> I have been running SQL Server 2000, client tools only.
> i installed SQL Server Express (and associated .NET
> framework upgrade) to take a look.
> I then uninstalled sql server express and went back to
> version 1.1 of .NET framework.
> My query analyzer works fine, however when i try to load
> Enterprise Manager, it says:
> Snap-in failed to initialize.
> Name: Microsoft SQL Enterprise Manager
> CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
> I have looked through the knowledge base articles and
> have not found one specific to my situation.
> I have uninstalled/reinstalled sql server 2000 (and
> therefore, MDAC as well) and I am running into the same
> issues.
> Any help is appreciated.
|||I just tried it with the same result.

>--Original Message--
>Did you try regsvr32 c:\...\...\sqldmo.dll
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"RR" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
load
>
>.
>
|||> I just tried it with the same result.
Did you find the actual sqldmo.dll file that corresponds to the SQL Server
2000 install? Or did you run exactly what I posted? Did you get a dialog
that told you the registration was successful?
http://www.aspfaq.com/
(Reverse address to reply.)
|||Yes - the file came from the sql 2000 install and
received a message that is was successful.

>--Original Message--
>Did you find the actual sqldmo.dll file that corresponds
to the SQL Server
>2000 install? Or did you run exactly what I posted?
Did you get a dialog
>that told you the registration was successful?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>
|||You might want to post your issue and any relevant log files from the
install/uninstall to the SQL Server 2005 newsgroups. I'm sure they are
dealing with a lot of similar issues.
For information on access to those groups:
http://communities.microsoft.com/new...elcomePage.htm
http://www.aspfaq.com/
(Reverse address to reply.)
<anonymous@.discussions.microsoft.com> wrote in message
news:508f01c489e1$cf7b55b0$a301280a@.phx.gbl...[vbcol=seagreen]
> Yes - the file came from the sql 2000 install and
> received a message that is was successful.
>
> to the SQL Server
> Did you get a dialog
sql

Enterprise Mgr Snap-In Issue

I have been running SQL Server 2000, client tools only.
i installed SQL Server Express (and associated .NET
framework upgrade) to take a look.
I then uninstalled sql server express and went back to
version 1.1 of .NET framework.
My query analyzer works fine, however when i try to load
Enterprise Manager, it says:
Snap-in failed to initialize.
Name: Microsoft SQL Enterprise Manager
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I have looked through the knowledge base articles and
have not found one specific to my situation.
I have uninstalled/reinstalled sql server 2000 (and
therefore, MDAC as well) and I am running into the same
issues.
Any help is appreciated.Did you try regsvr32 c:\...\...\sqldmo.dll
http://www.aspfaq.com/
(Reverse address to reply.)
"RR" <anonymous@.discussions.microsoft.com> wrote in message
news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
> I have been running SQL Server 2000, client tools only.
> i installed SQL Server Express (and associated .NET
> framework upgrade) to take a look.
> I then uninstalled sql server express and went back to
> version 1.1 of .NET framework.
> My query analyzer works fine, however when i try to load
> Enterprise Manager, it says:
> Snap-in failed to initialize.
> Name: Microsoft SQL Enterprise Manager
> CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
> I have looked through the knowledge base articles and
> have not found one specific to my situation.
> I have uninstalled/reinstalled sql server 2000 (and
> therefore, MDAC as well) and I am running into the same
> issues.
> Any help is appreciated.|||I just tried it with the same result.

>--Original Message--
>Did you try regsvr32 c:\...\...\sqldmo.dll
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"RR" <anonymous@.discussions.microsoft.com> wrote in
message
>news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
load[vbcol=seagreen]
>
>.
>|||> I just tried it with the same result.
Did you find the actual sqldmo.dll file that corresponds to the SQL Server
2000 install? Or did you run exactly what I posted? Did you get a dialog
that told you the registration was successful?
http://www.aspfaq.com/
(Reverse address to reply.)|||Yes - the file came from the sql 2000 install and
received a message that is was successful.

>--Original Message--
>Did you find the actual sqldmo.dll file that corresponds
to the SQL Server
>2000 install? Or did you run exactly what I posted?
Did you get a dialog
>that told you the registration was successful?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||You might want to post your issue and any relevant log files from the
install/uninstall to the SQL Server 2005 newsgroups. I'm sure they are
dealing with a lot of similar issues.
For information on access to those groups:
url]
[url]http://www.aspfaq.com/" target="_blank">http://communities.microsoft.com/ne...www.aspfaq.com/
(Reverse address to reply.)
<anonymous@.discussions.microsoft.com> wrote in message
news:508f01c489e1$cf7b55b0$a301280a@.phx.gbl...[vbcol=seagreen]
> Yes - the file came from the sql 2000 install and
> received a message that is was successful.
>
> to the SQL Server
> Did you get a dialog

Enterprise Mgr Snap-In Issue

I have been running SQL Server 2000, client tools only.
i installed SQL Server Express (and associated .NET
framework upgrade) to take a look.
I then uninstalled sql server express and went back to
version 1.1 of .NET framework.
My query analyzer works fine, however when i try to load
Enterprise Manager, it says:
Snap-in failed to initialize.
Name: Microsoft SQL Enterprise Manager
CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
I have looked through the knowledge base articles and
have not found one specific to my situation.
I have uninstalled/reinstalled sql server 2000 (and
therefore, MDAC as well) and I am running into the same
issues.
Any help is appreciated.Did you try regsvr32 c:\...\...\sqldmo.dll
--
http://www.aspfaq.com/
(Reverse address to reply.)
"RR" <anonymous@.discussions.microsoft.com> wrote in message
news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
> I have been running SQL Server 2000, client tools only.
> i installed SQL Server Express (and associated .NET
> framework upgrade) to take a look.
> I then uninstalled sql server express and went back to
> version 1.1 of .NET framework.
> My query analyzer works fine, however when i try to load
> Enterprise Manager, it says:
> Snap-in failed to initialize.
> Name: Microsoft SQL Enterprise Manager
> CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
> I have looked through the knowledge base articles and
> have not found one specific to my situation.
> I have uninstalled/reinstalled sql server 2000 (and
> therefore, MDAC as well) and I am running into the same
> issues.
> Any help is appreciated.|||I just tried it with the same result.
>--Original Message--
>Did you try regsvr32 c:\...\...\sqldmo.dll
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"RR" <anonymous@.discussions.microsoft.com> wrote in
message
>news:bf9001c489db$bebd80f0$a501280a@.phx.gbl...
>> I have been running SQL Server 2000, client tools only.
>> i installed SQL Server Express (and associated .NET
>> framework upgrade) to take a look.
>> I then uninstalled sql server express and went back to
>> version 1.1 of .NET framework.
>> My query analyzer works fine, however when i try to
load
>> Enterprise Manager, it says:
>> Snap-in failed to initialize.
>> Name: Microsoft SQL Enterprise Manager
>> CLSID:{00100100-1816-11D0-8EF5-00AA0062C58F}
>> I have looked through the knowledge base articles and
>> have not found one specific to my situation.
>> I have uninstalled/reinstalled sql server 2000 (and
>> therefore, MDAC as well) and I am running into the same
>> issues.
>> Any help is appreciated.
>
>.
>|||> I just tried it with the same result.
Did you find the actual sqldmo.dll file that corresponds to the SQL Server
2000 install? Or did you run exactly what I posted? Did you get a dialog
that told you the registration was successful?
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Yes - the file came from the sql 2000 install and
received a message that is was successful.
>--Original Message--
>> I just tried it with the same result.
>Did you find the actual sqldmo.dll file that corresponds
to the SQL Server
>2000 install? Or did you run exactly what I posted?
Did you get a dialog
>that told you the registration was successful?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>.
>|||You might want to post your issue and any relevant log files from the
install/uninstall to the SQL Server 2005 newsgroups. I'm sure they are
dealing with a lot of similar issues.
For information on access to those groups:
http://communities.microsoft.com/newsgroups/ICP/sqlserver2005/us/welcomePage.htm
--
http://www.aspfaq.com/
(Reverse address to reply.)
<anonymous@.discussions.microsoft.com> wrote in message
news:508f01c489e1$cf7b55b0$a301280a@.phx.gbl...
> Yes - the file came from the sql 2000 install and
> received a message that is was successful.
>
> >--Original Message--
> >> I just tried it with the same result.
> >
> >Did you find the actual sqldmo.dll file that corresponds
> to the SQL Server
> >2000 install? Or did you run exactly what I posted?
> Did you get a dialog
> >that told you the registration was successful?
> >
> >--
> >http://www.aspfaq.com/
> >(Reverse address to reply.)
> >
> >
> >.
> >

Enterprise Mgr

I have recently installed MSDE on my computer. Now I need to get a copy of
Enterprise Mgr or equivalent. Does anyone know if I can obtain this from
somewhere without having to purchase anything from M$http://www.aspfaq.com/show.asp?id=2442

--
David Portas
SQL Server MVP
--

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...
> > 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?
> > >
> > >
> >
> >
>

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
>