@@FETCH_STATUS

Hi there..
I have this problem: I run my stored proc alot of times for testing, but one
time it want work.
It just give me back this message: The command(s) completed successfully.
I checked the @.@.FETCH_STATUS and it became -1, why is that when it worked
before..
Can any body help me'
THX@.@.FETCH_STATUS is for cursors, you want to use @.@.ERROR instead if it's 0
then there is no error
http://sqlservercode.blogspot.com/
"Hussain Al-Mousawi" <hal_mousawi@.hotmail.com> wrote in message
news:uv6dVVTRGHA.2532@.TK2MSFTNGP10.phx.gbl...
> Hi there..
> I have this problem: I run my stored proc alot of times for testing, but
> one time it want work.
> It just give me back this message: The command(s) completed successfully.
> I checked the @.@.FETCH_STATUS and it became -1, why is that when it worked
> before..
> Can any body help me'
> THX
>

@@Error not catching error.

Hi all,

I want to catch error in stored procedure and return error message.
I want to catch error 'Syntax error converting the varchar value 'a'
to a column of data type int.' Means error occuring if i enter wrong
value.

Say suppose i have statment like

select * from emp where rowid = 'a'
PRINT @.@.ERROR
print 'reach'

here rowid is integer value so i am getting above mention error.

So what i am expecting is it should print error and then print 'reach'
which is not happening.
can anyone tell me reason behind this and how to overcome this
problem.

thanks in advance.(trialproduct2004@.yahoo.com) writes:

Quote:

Originally Posted by

I want to catch error in stored procedure and return error message.
I want to catch error 'Syntax error converting the varchar value 'a'
to a column of data type int.' Means error occuring if i enter wrong
value.
>
Say suppose i have statment like
>
select * from emp where rowid = 'a'
PRINT @.@.ERROR
print 'reach'
>
here rowid is integer value so i am getting above mention error.
>
So what i am expecting is it should print error and then print 'reach'
which is not happening.
can anyone tell me reason behind this and how to overcome this
problem.

If you are on SQL 2005, you need to use TRY-CATCH. If you are using SQL
2000, you first need to upgrade to SQL 2005. In SQL 2000 you cannot detect
this error, because the entire batch is aborted because of the error.
If you want to know more about error handling in SQL 2000, I have an
article on my web site: http://www.sommarskog.se/error-handling-I.html.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||(trialproduct2004@.yahoo.com) writes:

Quote:

Originally Posted by

I want to catch error in stored procedure and return error message.
I want to catch error 'Syntax error converting the varchar value 'a'
to a column of data type int.' Means error occuring if i enter wrong
value.
>
Say suppose i have statment like
>
select * from emp where rowid = 'a'
PRINT @.@.ERROR
print 'reach'
>
here rowid is integer value so i am getting above mention error.
>
So what i am expecting is it should print error and then print 'reach'
which is not happening.
can anyone tell me reason behind this and how to overcome this
problem.

If you are on SQL 2005, you need to use TRY-CATCH. If you are using SQL
2000, you first need to upgrade to SQL 2005. In SQL 2000 you cannot detect
this error, because the entire batch is aborted because of the error.
If you want to know more about error handling in SQL 2000, I have an
article on my web site: http://www.sommarskog.se/error-handling-I.html.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

about error message - lost file header

I made a mistake in copying my database and somehow lost my file header. How do I recreate my file header without losing all the data in my database? Is there a way to undo my mistake?

Thanks

Debbie

I don't know what you mean by a file header. Is this a SQL Server database? How does this relate to SSIS?

Is the file header part of the database, or are you just talking about a text file with header information in it? Why would this mean you would loose data in a database?

.NET Framwork error when starting SQL Server Profiler

Greetings,

I have been having a problem when I try starting the SQL Profiler. I am running the SQL Server 2005 - Developer edition. I get a message box from Microsoft .NET Framework saying:

Unhandled exception has occurred in a component in your application. If you click Continue, the application will ignore this error and attempt to continue.

Could not load file or assembly 'ConnectionDlg, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its

The details listed under the Details button are:

See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'ConnectionDlg, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot find the file specified.
File name: 'ConnectionDlg, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91'
at Microsoft.SqlServer.Management.UI.Profiler.SplashScreen.OptimizeLoadTime()
at Microsoft.SqlServer.Management.UI.Profiler.SplashScreen.splashTimer_Elapsed(Object sender, EventArgs e)
at System.Windows.Forms.Timer.OnTick(EventArgs e)
at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
-
PROFILER90
Assembly Version: 9.0.242.0
Win32 Version: 2005.090.1399.00
CodeBase: file:///C:/PROGRA~1/MICROS~4/90/Tools/Binn/PROFIL~1.EXE
-
msvcm80
Assembly Version: 8.0.50608.0
Win32 Version: 8.00.50727.91
CodeBase: file:///C:/WINDOWS/WinSxS/x86_Microsoft.VC80.CRT_1fc8b3b9a1e18e3b_8.0.50727.91_x-ww_0de56c07/msvcm80.dll
-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
-
pfui90
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase: file:///C:/PROGRA~1/MICROS~4/90/Tools/Binn/pfui90.DLL
-

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

******

I have tried uninstalling SQL Server completely as well as .NET2 and then reinstalling them. There is still no change. The rest of the program appears to function fine. Only the Profiler is affected.

Any help would be greatly appreciated.

Thank you for your time.

Terry.

verify this file exists...

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\ConnectionDlg.dll

The namespace of this assembly is Microsoft.SqlServer.Management.UI.ConnectionDlg and I do NOT see this assembly in my GAC, so just ensure its there.

|||Greetings,

I have checked and yes, the file does exist. It is version 9.0.1399.0 (Assembly Version: 9.0.242.0) and file size is: 981,720 bytes.|||then I am assuming that onLoad of Profiler it is looking in the wrong binn directory for the assemblies it uses. No clue at this point dude.|||

No problem. At least you did try so for that I do thank you. Besides, for most problems, it's the simple or obvious answer that solves it. This one so far has been the rarity.

|||Greetings,

I had found out the problem with the Profiler. It turned out that the problem was a bad link file. I would click on the link to start the Profiler, but it would not set the path environment correctly. So, the Profiler was not able to find the needed files. I had deleted the link and made a new one and it worked fine after that. Definitely a strange cause to the problem.

Thanks for the help.

.Net Framework error message when starting SQL 2005 Management Studio

Has anyone ever recieved an error when starting the Management Studio?

"Unhandled excpetion has occurred in a component in your application.

"Input String was not in a correct format"

I click continue and I can still use the manager;however, it gets annoying. The details of the error are very long and too much to add to this thread.

Any ideas?

never had that but I would probably start by repairing the .NET Framework and see how that goes?

would be nice if you could post the error message, even if it is long

|||

I did repair the .NET Framework and same issue. I also reinstalled the SQL 05 components. Here is the error message.

Thank you for your help.

See the end of this message for details on invoking

just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************

System.FormatException: Input string was not in a correct format.

at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)

at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)

at Microsoft.SqlServer.Management.UI.ConnectionDlg.LoginControl.InitFromLastUsedServerType()

at Microsoft.SqlServer.Management.UI.ConnectionDlg.ConnectionDialog.DoOneTimeInitialization()

at Microsoft.SqlServer.Management.UI.ConnectionDlg.ConnectionDialog.OnVisibleChanged(EventArgs e)

at Microsoft.SqlServer.Management.UI.VSIntegration.ShellConnectionDialog.OnVisibleChanged(EventArgs e)

at System.Windows.Forms.Control.WmShowWindow(Message& m)

at System.Windows.Forms.Control.WndProc(Message& m)

at System.Windows.Forms.ScrollableControl.WndProc(Message& m)

at System.Windows.Forms.ContainerControl.WndProc(Message& m)

at System.Windows.Forms.Form.WmShowWindow(Message& m)

at System.Windows.Forms.Form.WndProc(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)

at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)

at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

************** Loaded Assemblies **************

mscorlib

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll

-

AppIDPackage

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/AppIDPackage.DLL

-

System

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll

-

Microsoft.SqlServer.SqlTools.VSIntegration

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.SqlTools.VSIntegration.DLL

-

Microsoft.VisualStudio.Shell.Interop

Assembly Version: 7.1.40304.0

Win32 Version: 7.0.4054

CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll

-

Microsoft.VisualStudio.OLE.Interop

Assembly Version: 7.1.40304.0

Win32 Version: 7.0.4054

CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll

-

System.Windows.Forms

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll

-

System.Drawing

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll

-

Microsoft.SqlServer.SqlTDiagM

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.SqlTDiagM/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.SqlTDiagM.dll

-

Microsoft.DataWarehouse.SQM

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL

-

Microsoft.SqlServer.Instapi

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll

-

ObjectExplorer

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ObjectExplorer.DLL

-

ConnectionDlg

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/ConnectionDlg.DLL

-

Microsoft.SqlServer.CustomControls

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.CustomControls/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.CustomControls.dll

-

SqlWorkbench.Interfaces

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlWorkbench.Interfaces.DLL

-

Accessibility

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll

-

SqlMgmt

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/SqlMgmt.DLL

-

Microsoft.SqlServer.RegSvrEnum

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.RegSvrEnum/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.RegSvrEnum.dll

-

EnvDTE

Assembly Version: 8.0.0.0

Win32 Version: 8.0.50727.42 (RTM.050727-4200)

CodeBase: file:///C:/WINDOWS/assembly/GAC/EnvDTE/8.0.0.0__b03f5f7f11d50a3a/EnvDTE.dll

-

Microsoft.NetEnterpriseServers.ExceptionMessageBox

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.ExceptionMessageBox/9.0.242.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.ExceptionMessageBox.dll

-

System.Data

Assembly Version: 2.0.0.0

Win32 Version: 2.0.50727.42 (RTM.050727-4200)

CodeBase: file:///C:/WINDOWS/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll

-

Microsoft.SqlServer.ConnectionInfo

Assembly Version: 9.0.242.0

Win32 Version: 9.00.1399.00

CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.ConnectionInfo/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.ConnectionInfo.dll

-

************** JIT Debugging **************

To enable just-in-time (JIT) debugging, the .config file for this

application or computer (machine.config) must have the

jitDebugging value set in the system.windows.forms section.

The application must also be compiled with debugging

enabled.

For example:

<configuration>

<system.windows.forms jitDebugging="true" />

</configuration>

When JIT debugging is enabled, any unhandled exception

will be sent to the JIT debugger registered on the computer

rather than be handled by this dialog box.

(urgent)help needed with this error message

Hi i am trying to transfer the contents of a dbf file to sql server 2005 and this is my error message

'C:\Documents and Settings\Karen\My Documents\Visual Studio 2005\WebSites\ASC1\pdf\client\AS.DBF' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

This is my code

If (FlAS.PostedFile.FileName.ToLower.EndsWith(".dbf"))Then FlAS.PostedFile.SaveAs(location) Try'Connection string to a dbase file Dim dbfConnectionString As String = String.Format("Provider=Microsoft.Jet.OLEDB.4.0;Data Source ={0};Extended Properties= dBase IV", location) 'create connectionto the DBFfile Using connectionAs Data.OleDb.OleDbConnection = New Data.OleDb.OleDbConnection(dbfConnectionString) Dim commandAs Data.OleDb.OleDbCommand = New Data.OleDb.OleDbCommand("Select *from AS.DBF", connection) connection.Open()'Create a dbDatareader to the dbf file Using dr As Data.Common.DbDataReader = command.ExecuteReader() Dim sqlConnectionString As String = System.Configuration.ConfigurationManager.AppSettings(APPSETTINGS_CONNECTION) Dim myConnection As New SqlConnection(System.Configuration.ConfigurationManager.AppSettings(APPSETTINGS_CONNECTION)) Dim query As String = "Truncate table ASDBF" myConnection.Open() Dim cmd As New SqlCommand(query, myConnection) cmd.CommandType = CommandType.Text cmd.ExecuteScalar() myConnection.Close() 'bulk copyof sql server Using BulkCopyAs SqlBulkCopy = New SqlBulkCopy(sqlConnectionString) BulkCopy.DestinationTableName = "ASDBF" BulkCopy.WriteToServer(dr)End UsingEnd Using connection.Close()End Using Catch exAs Exception Throw exEnd TryEnd If

Any help will be appreciated.

Regards

Karen

What is the "location" variable? What is it's value? Where is it set?

|||

location is set before the if Statement and its a string

location = Server.MapPath("pdf/client/" + Session("ClientName") + strAS)

|||

Debug your code and verify that the string "location" looks as you would expect

|||

yeah it does... but how would i know if i have to use a foxpro connection string or a dbase connection string and which version?

Regards

Karen

|||

Where is your code failing? On file.saveas(...)?

|||no its failing at

connection.Open() ... cause i can see the file name in the location that i am saving it to.

|||

Using 'Tools' --> 'Connect to Database', try to create a connection to the .DBF file. I think that there is a problem with the connection string. Once you successfully connect from Visual Studio, you should be able to copy that connection string into your code.

|||

I found this article.. Hopefully this will help you. Looks like you may need to leave the filename off of the Data Source (only include the folder name).. Take a look

http://www.msdner.com/forum/thread51916.html

|||

thanks should i use this provider?

Microsoft Jet 4.0 OLE DB Provider or which one?

|||

Just a quick glance through the article, it looked like your connection string was ok, except for the filename on the end of the datasource.

|||

i used the same connection string to a excel file but specified the extended properties as excel 8.0 and it works fine... but not sure why isnt it working for a dbf file

|||

Thanks SSWanner for your answer... I got it working... I downloaded the fox pro oledb provider... and it kinda worked good it failed at the sql insertion (sql exception) and i am familiar with that error. The error i got is

Received an invalid column length from the bcp client for colid 1

I just need to change the column length in sql server..

Again Thanks a lot.

Regards

Karen

(Repost) Problems installing SQL 2005 Express after trying VS.NET 2005 Beta 2

Repost: This message had moved into another thread. Not sure why so I thought I'd repost as a new thread just to make sure it gets read ok :)
-
Hi Everyone,
I recently installed Visual Studio .NET 2005 Beta 2 which included SQL 2005 Community Technology Preview. After installing it all, I was no longer able to connect to my SQL 2000 instance in Enterprise Manager. The application opened ok but whenever I tried to browse the server or register it again, it was giving me an error relating to named pipes which really confused me since I was trying to connect to a SQL 2000 database through the SQL 2000 application. I was able to use the 2005 equivalent application (the name eludes me right now) to connect to the \SQLEXPRESS instance. All this time I could still connect to the default instance through Query Analyser and my .NET Web Applications that used SQL databases.
I later had to uninstall the betas because I needed a newer version of the .NET Framework to work with DotNetNuke 4.0. (A whole other story there...)
After uninstalling everything relating to the betas (which I had to do carefully in a prescribed order) I found that I couldn't even open Enterprise Manager properly. It had a big error message in the main display window. I discovered from a forum somewhere that I had to re-register a dll file to fix it. I did this and everything was back to normal.
(pause for breath)
OK, so then I downloaded Visual Web Developer 2005 Express Edition and installed it. Everything was great until the end of the SQL Server 2005 Express Edition setup when I was told it had failed to install. I haven't looked through ALL the log files but in the summary log file, the following message is reported for all three errors:
"[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe."
I am running Windows XP, SP2 with everything up to date in Windows Update. The Beta 2 of VS.NET was the only beta software I've installed. I'm not trying to connect to a different machine or anything either. VS and SQL are both on the same machine. The only other thing that may be relevant is that the SQL 2000 I have is an evaulation version. I don't think that affects it but you never know. It's often the most overlooked variable that trips you.
Does anyone have any suggestions about how to remedy this?
Thanks for taking the time to read about my problem :)Update:
I solved the problem by backing up my data and re-installing Windows. I now have Visual Web Developer and SQL 2005 Express running alongside Visual Studio 2003 Enterprise Developer, MSDE and SQL 2000.
I don't know if there was a simpler solution but I had spent too much time on it already. Hurrah for my new Maxtor OneTouch II external 300GB beast that carried the burden of my data during these difficult hours!

(Repost) Problems installing SQL 2005 Express after trying VS.NET 2005 Beta 2

Repost: This message had moved into another thread. Not sure why so I thought I'd repost as a new thread just to make sure it gets read ok :)
-
Hi Everyone,
I recently installed Visual Studio .NET 2005 Beta 2 which included SQL 2005 Community Technology Preview. After installing it all, I was no longer able to connect to my SQL 2000 instance in Enterprise Manager. The application opened ok but whenever I tried to browse the server or register it again, it was giving me an error relating to named pipes which really confused me since I was trying to connect to a SQL 2000 database through the SQL 2000 application. I was able to use the 2005 equivalent application (the name eludes me right now) to connect to the \SQLEXPRESS instance. All this time I could still connect to the default instance through Query Analyser and my .NET Web Applications that used SQL databases.
I later had to uninstall the betas because I needed a newer version of the .NET Framework to work with DotNetNuke 4.0. (A whole other story there...)
After uninstalling everything relating to the betas (which I had to do carefully in a prescribed order) I found that I couldn't even open Enterprise Manager properly. It had a big error message in the main display window. I discovered from a forum somewhere that I had to re-register a dll file to fix it. I did this and everything was back to normal.
(pause for breath)
OK, so then I downloaded Visual Web Developer 2005 Express Edition and installed it. Everything was great until the end of the SQL Server 2005 Express Edition setup when I was told it had failed to install. I haven't looked through ALL the log files but in the summary log file, the following message is reported for all three errors:
"[Microsoft][SQL Native Client]Shared Memory Provider: No process is on the other end of the pipe."
I am running Windows XP, SP2 with everything up to date in Windows Update. The Beta 2 of VS.NET was the only beta software I've installed. I'm not trying to connect to a different machine or anything either. VS and SQL are both on the same machine. The only other thing that may be relevant is that the SQL 2000 I have is an evaulation version. I don't think that affects it but you never know. It's often the most overlooked variable that trips you.
Does anyone have any suggestions about how to remedy this?
Thanks for taking the time to read about my problem :)Update:

I solved the problem by backing up my data and re-installing Windows. I

now have Visual Web Developer and SQL 2005 Express running alongside

Visual Studio 2003 Enterprise Developer, MSDE and SQL 2000.

I don't know if there was a simpler solution but I had spent too much

time on it already. Hurrah for my new Maxtor OneTouch II external 300GB

beast that carried the burden of my data during these difficult hours!