I've installed SQL express, now what?

This may be a stupid question, but I've installed SQL Express and I don't know what to do next. I went to my program files/Microsft SQL... and the only folder present is a configuration folder.

Next I went to my control panel/admin tools/ODBC and succussfully created a user data source. (With the help of the forum!)

Obviously, I've never used SQL before, but I've read a couple of books and other stuff online, and I want to teach myself. So I decided to install this. Basically, I'm looking for answers on how to access the database. I know it's installed, it's in the Add/Remove programs list. I just don't know how to connect/access it.

Sorry for the dumb question.

Stacey

I think I figured it out. You have to access the DB using another program, and connect using the ODBC that I previously created. Am I correct?

I thought it was an independent DB, meaning I could directly access it. Thanks!

|||

Hi

You'll need to download SQL Management Studio Express (here). It will allow you to create databases, run queries etc. That way you won't have to work "in the dark".

HTH

|||

Thank you so much for helping me. Now I just have to figure out how to use it, and what to do!!!

Stacey

|||Update - Thank you so much Andre! I am off and running thanks to you. I figured out how to use it, and now I'm learning SQL thanks to you!!

IUSR Web Access to DB - Separate Servers

I have NT SQL 7 and Web Server on same box. I have a new server with W2K and SQL 2000 installed (no IIS). I am migrating the databases over and when done I will install W2K on the old box and it will remain the IIS Web server front end to the new SQL 2000 Server.

On the old configuration, IIS and SQL 7 on the same box, I added the IUSER to the database from the local computer users list when needed for web access. How do I add that user now that the boxes are seperate? The acccout is not a local account on the new machine and the account is a loca account on the other machine so it does not authenticate to the domain so I can't pull it in from there.

Thanks for any help.

--Steve

ssantos@.csuchico.eduSimple answer is to use SQL Authentication.

Create a SQL user on your SQL box, then use a non-SSPI connection in your ASP/ASPX.

More complicated, but ultimately better answer:
Create a new domain user, give it the same permissions on the IIS machine as the IUSER, restrict it's permissions elsewhere on the domain, then add them as a database user in the SQL box.

It must have been a corruption

I cannot take this anymore...

I have installed sql server service pack 1 which is the same as a colleague of mine has and his package works...

How in name of goodness are we supposed to set a connectionstring that actually works...I have tried recreating the project and deleting a recreating the components but the message is still: Login failed for user 'sa'

This is absolutely pathetic from Microsoft to release such a bug-ridden system.
Have you setup correct login information on the connections?

What is the ProtectionLevel property of the package set to?|||

mj van den berg wrote:

I cannot take this anymore...

I have installed sql server service pack 1 which is the same as a colleague of mine has and his package works...

How in name of goodness are we supposed to set a connectionstring that actually works...I have tried recreating the project and deleting a recreating the components but the message is still: Login failed for user 'sa'

This is absolutely pathetic from Microsoft to release such a bug-ridden system.

Many many other people have managed it (including your colleague) thus proving that the product is not bug-ridden. Perhaps you might want to look a bit closer to home before blaming anyone else.

Exactly where are you trying to apply the connection string? You are aware that under some circumstances SSIS will not store the password for you, right? That's is why Phil asked about ProtectionLevel

-Jamie

|||

Check if you have the same user profile of your collegues!

Regards,

Pedro

|||

PedroCGD wrote:

Check if you have the same user profile of your collegues!

Regards,

Pedro

He won't likely.|||

If your problem is in your company, check in active directory if you have the same groups of your collegues...

|||

PedroCGD wrote:

Check if you have the same user profile of your collegues!

Regards,

Pedro

I have checked that. We are using the same user profiles. Both packages are set to EncryptSensitiveWithUserKey.

The thing is: I have both projects on my pc and my colleague and I are both trying to fix this and even though his works, none of us can explain why the thing fails since there are 2 of us who have confirmed it being the same. I am sorry if I sound like I am passing the blame to microsoft and will admit that I am new in SSIS (obviously) but the reason I'm so frustrated is that this is the first software package i have worked on in a long time where one fixes things by recreating the component or even the package from scratch and things will start to work.

I mean, every time I, for instance, delete a connection manager, the environment does not remove the component's ID from the dtsx file and I have to manually do it otherwise I get the message of the project being corrupt. This is an ongoing thing that I am experiencing and it's getting frustrating.

I have now recreated the package from scratch and all of a sudden some things are starting to work such as directory variables that point the 'for each loop' to a folder where flat files are to be processed....and I did not change anything compared to the previous package.

About the connection string, I have created an oledb connection manager and set the connection information there. It was tested and it connected. Then I defined it in a script's connection manager which i use in the script to execute a simple query which never fire's since I cant get the connectionstring to work...again, this is the same as the colleagues package.

I am sorry for sounding a tad over-frustrated yesterday...today will be better since my aircon is working again

Regards
|||You may have already tested this, but if you are using EncryptSensitiveWithUserKey, only the user account that created the package will be able to decrypt passwords in it. So unless you and your colleague are logging on to the network with the same user ID, you shouldn't expect to run his packages or vice versa.|||Hi,

Thanks for the reply. We have created a user for this and both use that user.

I have spent a great number of hours recreating the project on a different machine, that I stole from our store room, using the same methods etc and it works!

It must be something that had gone corrupt on my machine which is strange since it is a brand new laptop. Our internal it guys set it up though including the development software so I'm going to do it myself now.

Thanks for the support.|||And you both log into the machine with the same user account on the same machine? If not the same machine, I believe the user key will be different and hence, your problem.|||

mj van den berg wrote:

We have created a user for this and both use that user.

Hi Mj Van Den Berg,

I'm curious about this. What type of user did you create? Is this a SQL Server login or an Active Directory account?

Thanks,

Andy

|||I'm thinking the same as Andy here (I think ).
The "userkey" points to the user you use to log in to windows, not the user to log in on the DB. So if your colleague made a package and you used it, this would mean you, on your system, would not be able to decrypt the connection info for the datasource.
|||Hi there,

The user account is a sql server account, which is why we could log on again after recreating it on the other machine.

I have played around setting the package security to almost every option (even those I knew wouldn't work) but it went bad.

I finally decided to rebuild my machine when my colleague told me that his environment wouldn't go corrupt when he, for instance deletes an existing data connection-manager and that he rarely had to manually edit the dtsx file and another non SSIS project of mine started to act up with it's designer not functioning properly as well.

Regards
|||

Hi Mj Van Den Berg,

Rebuilding your laptop may or may not correct the issue. I hope it works for you.

To be sure I'm understanding the scenario:

1. You and your colleague both build SSIS packages.

2. Your colleague's SSIS packages execute - even when you log into the domain as yourself from your laptop and execute your colleague's SSIS packages manually.

3. SSIS packages you author execute partially (you can get some connections to work now but cannot connect from a script task).

Please clarify.

Here's some of my thinking:

1. Connectivity in SSIS is no simple matter. Understanding connectivity is one of the steeper ledges on the SSIS learning curve. There are multiple moving parts: Data Connections are stored on the development workstation; Connection Managers are managed at either the solution or package level, depending on how they're defined; Source and Destination Adapters can be stand-alone objects in a Data Flow or integrated into Data Flow components or Control Flow Tasks.

2. SSIS Security is an equally steep ledge on the SSIS learning curve. Information considered "Sensitive" is never maintained as clear text. This means if you:

a. define an OLE DB Connection Manager using the sa account and proper password,

b. check the "Save my password" checkbox,

c. test the connection (and the test is successful),

d. close the Connection Manager editor,

e. browse to the Connection Manager Properties,

f. highlight and copy the ConnectionString value, and

g. paste this value into the ConnectionString property of an ADO.Net connection you are establishing from a Script Task;

the ADO.Net connection inside the Script Task will always fail because it is missing the password property - while the Source and Destination Adapters that reference the OLE DB Connection Manager will successfully connect. This is all by design. I'm not saying this is what you did but if you did, all you have to do to make this ADO.Net connection work inside the Script Task is simply append text like "Password=[MySaAccountPassword];" to the ADO.Net ConnectionString property inside the Script Task.

3. SSIS connectivity and security interact. The behavior is controlled largely by the ProtectionLevel property of the package but it's important to realize that, in an Active Directory domain, your Active Directory user profile can play an important role in package execution - depending on how you define connectivity and security in your SSIS solution and package. The default ProtectionLevel property setting is EncryptSensitiveWithUserKey. This setting means your Active Directory credentials are used to determine your rights to connect to any data source (SQL Server, directory, file) outside the package - unless you explicitly provide security information (username \ password). If your Active Directory user profile is identical (all SQL Server, directory, file permissions are the same) to that of your colleague, it's likely your laptop rebuild will correct some of the issues you're experiencing. If your user profiles differ, rebuilding the laptop may not correct the issues.

From your three posts above, I understand you don't like the fact you cannot delete connection managers completely from your SSIS package by simply clicking on them and pressing the Delete key. This issue can be the result of:

1. Corrupt package metadata,

2. A less-than-up-to-date installation of SSIS (SP2 is current),

3. An incorrect or corrupt installation of SSIS.

It's important to consider all of these scenarios when troubleshooting these types of issues. I advise considering them in the order listed.

In my opinion, it's better to encounter and address these issues now. Most folks learn about them on deployment day which is far more painful than during development.

Andy

|||Hi Andy,

Thank you very much for the in-depth and helpful post.

I have rebuilt my laptop and updated every software package that I could think of and, thank goodness, it works!

I'm sure that I must have had a corrupted installation of SSIS or even SQL server 2005 otherwise the problem would have persisted. For informative purposes, I want to elaborate that we did use a password variable which is passed through to the script which is used to take care of the problem of it failing due to the password property.

I am still new to the SSIS package and I should have known better to assume that because it is fairly new that it does behave as strangely as it did on my pc. There was also some strange behavior in SQL server's management studio bombing out frequently but I only picked this up after my issues with SSIS.

Thanks for all the help
Regards
Marcel

It must have been a corruption

I cannot take this anymore...

I have installed sql server service pack 1 which is the same as a colleague of mine has and his package works...

How in name of goodness are we supposed to set a connectionstring that actually works...I have tried recreating the project and deleting a recreating the components but the message is still: Login failed for user 'sa'

This is absolutely pathetic from Microsoft to release such a bug-ridden system.
Have you setup correct login information on the connections?

What is the ProtectionLevel property of the package set to?|||

mj van den berg wrote:

I cannot take this anymore...

I have installed sql server service pack 1 which is the same as a colleague of mine has and his package works...

How in name of goodness are we supposed to set a connectionstring that actually works...I have tried recreating the project and deleting a recreating the components but the message is still: Login failed for user 'sa'

This is absolutely pathetic from Microsoft to release such a bug-ridden system.

Many many other people have managed it (including your colleague) thus proving that the product is not bug-ridden. Perhaps you might want to look a bit closer to home before blaming anyone else.

Exactly where are you trying to apply the connection string? You are aware that under some circumstances SSIS will not store the password for you, right? That's is why Phil asked about ProtectionLevel

-Jamie

|||

Check if you have the same user profile of your collegues!

Regards,

Pedro

|||

PedroCGD wrote:

Check if you have the same user profile of your collegues!

Regards,

Pedro

He won't likely.|||

If your problem is in your company, check in active directory if you have the same groups of your collegues...

|||

PedroCGD wrote:

Check if you have the same user profile of your collegues!

Regards,

Pedro

I have checked that. We are using the same user profiles. Both packages are set to EncryptSensitiveWithUserKey.

The thing is: I have both projects on my pc and my colleague and I are both trying to fix this and even though his works, none of us can explain why the thing fails since there are 2 of us who have confirmed it being the same. I am sorry if I sound like I am passing the blame to microsoft and will admit that I am new in SSIS (obviously) but the reason I'm so frustrated is that this is the first software package i have worked on in a long time where one fixes things by recreating the component or even the package from scratch and things will start to work.

I mean, every time I, for instance, delete a connection manager, the environment does not remove the component's ID from the dtsx file and I have to manually do it otherwise I get the message of the project being corrupt. This is an ongoing thing that I am experiencing and it's getting frustrating.

I have now recreated the package from scratch and all of a sudden some things are starting to work such as directory variables that point the 'for each loop' to a folder where flat files are to be processed....and I did not change anything compared to the previous package.

About the connection string, I have created an oledb connection manager and set the connection information there. It was tested and it connected. Then I defined it in a script's connection manager which i use in the script to execute a simple query which never fire's since I cant get the connectionstring to work...again, this is the same as the colleagues package.

I am sorry for sounding a tad over-frustrated yesterday...today will be better since my aircon is working again

Regards
|||You may have already tested this, but if you are using EncryptSensitiveWithUserKey, only the user account that created the package will be able to decrypt passwords in it. So unless you and your colleague are logging on to the network with the same user ID, you shouldn't expect to run his packages or vice versa.|||Hi,

Thanks for the reply. We have created a user for this and both use that user.

I have spent a great number of hours recreating the project on a different machine, that I stole from our store room, using the same methods etc and it works!

It must be something that had gone corrupt on my machine which is strange since it is a brand new laptop. Our internal it guys set it up though including the development software so I'm going to do it myself now.

Thanks for the support.|||And you both log into the machine with the same user account on the same machine? If not the same machine, I believe the user key will be different and hence, your problem.|||

mj van den berg wrote:

We have created a user for this and both use that user.

Hi Mj Van Den Berg,

I'm curious about this. What type of user did you create? Is this a SQL Server login or an Active Directory account?

Thanks,

Andy

|||I'm thinking the same as Andy here (I think ).
The "userkey" points to the user you use to log in to windows, not the user to log in on the DB. So if your colleague made a package and you used it, this would mean you, on your system, would not be able to decrypt the connection info for the datasource.
|||Hi there,

The user account is a sql server account, which is why we could log on again after recreating it on the other machine.

I have played around setting the package security to almost every option (even those I knew wouldn't work) but it went bad.

I finally decided to rebuild my machine when my colleague told me that his environment wouldn't go corrupt when he, for instance deletes an existing data connection-manager and that he rarely had to manually edit the dtsx file and another non SSIS project of mine started to act up with it's designer not functioning properly as well.

Regards
|||

Hi Mj Van Den Berg,

Rebuilding your laptop may or may not correct the issue. I hope it works for you.

To be sure I'm understanding the scenario:

1. You and your colleague both build SSIS packages.

2. Your colleague's SSIS packages execute - even when you log into the domain as yourself from your laptop and execute your colleague's SSIS packages manually.

3. SSIS packages you author execute partially (you can get some connections to work now but cannot connect from a script task).

Please clarify.

Here's some of my thinking:

1. Connectivity in SSIS is no simple matter. Understanding connectivity is one of the steeper ledges on the SSIS learning curve. There are multiple moving parts: Data Connections are stored on the development workstation; Connection Managers are managed at either the solution or package level, depending on how they're defined; Source and Destination Adapters can be stand-alone objects in a Data Flow or integrated into Data Flow components or Control Flow Tasks.

2. SSIS Security is an equally steep ledge on the SSIS learning curve. Information considered "Sensitive" is never maintained as clear text. This means if you:

a. define an OLE DB Connection Manager using the sa account and proper password,

b. check the "Save my password" checkbox,

c. test the connection (and the test is successful),

d. close the Connection Manager editor,

e. browse to the Connection Manager Properties,

f. highlight and copy the ConnectionString value, and

g. paste this value into the ConnectionString property of an ADO.Net connection you are establishing from a Script Task;

the ADO.Net connection inside the Script Task will always fail because it is missing the password property - while the Source and Destination Adapters that reference the OLE DB Connection Manager will successfully connect. This is all by design. I'm not saying this is what you did but if you did, all you have to do to make this ADO.Net connection work inside the Script Task is simply append text like "Password=[MySaAccountPassword];" to the ADO.Net ConnectionString property inside the Script Task.

3. SSIS connectivity and security interact. The behavior is controlled largely by the ProtectionLevel property of the package but it's important to realize that, in an Active Directory domain, your Active Directory user profile can play an important role in package execution - depending on how you define connectivity and security in your SSIS solution and package. The default ProtectionLevel property setting is EncryptSensitiveWithUserKey. This setting means your Active Directory credentials are used to determine your rights to connect to any data source (SQL Server, directory, file) outside the package - unless you explicitly provide security information (username \ password). If your Active Directory user profile is identical (all SQL Server, directory, file permissions are the same) to that of your colleague, it's likely your laptop rebuild will correct some of the issues you're experiencing. If your user profiles differ, rebuilding the laptop may not correct the issues.

From your three posts above, I understand you don't like the fact you cannot delete connection managers completely from your SSIS package by simply clicking on them and pressing the Delete key. This issue can be the result of:

1. Corrupt package metadata,

2. A less-than-up-to-date installation of SSIS (SP2 is current),

3. An incorrect or corrupt installation of SSIS.

It's important to consider all of these scenarios when troubleshooting these types of issues. I advise considering them in the order listed.

In my opinion, it's better to encounter and address these issues now. Most folks learn about them on deployment day which is far more painful than during development.

Andy

|||Hi Andy,

Thank you very much for the in-depth and helpful post.

I have rebuilt my laptop and updated every software package that I could think of and, thank goodness, it works!

I'm sure that I must have had a corrupted installation of SSIS or even SQL server 2005 otherwise the problem would have persisted. For informative purposes, I want to elaborate that we did use a password variable which is passed through to the script which is used to take care of the problem of it failing due to the password property.

I am still new to the SSIS package and I should have known better to assume that because it is fairly new that it does behave as strangely as it did on my pc. There was also some strange behavior in SQL server's management studio bombing out frequently but I only picked this up after my issues with SSIS.

Thanks for all the help
Regards
Marcel

Issues with Un-Installng and Re-Installing SQL Server 2005

Are there any issues with un-installing and re-installing sql server 2005
dev edition? I think it installed SSRS. I know that un-installing and
re-installing sql server 2000 is pretty painless as I've done it many times
with no problems, however, un-installing and re-installing SSRS 2000 is a
MAJOR pain as it leaves many splinters behind that are difficult to deal
with prioer to re-installing SSRS.
My main concern is that I thought I specified the Data files to reside on
the D drive, however, sql server 2005 installed the data files in:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
Would it be be painless and trouble free to move the databases to
D:\MSSQL05\Data, and then from SQL Server Management
Studio/Properties/Database Settings/Database Default locations, set it to:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
Thanks.
moondaddy@.nospam.nospamBasially I don't see any issues, besides for the fact that you need to make
sure you have a copy of the database master key.
See Books online on how to export it.If you want to move you would be able
to do a database attach / detach.
I didn't really test it myself on RTM but on September CTP I had quite some
issues with it
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
"moondaddy" <moondaddy@.nospam.nospam> wrote in message
news:Oq9jG006FHA.2384@.TK2MSFTNGP12.phx.gbl...
> Are there any issues with un-installing and re-installing sql server 2005
> dev edition? I think it installed SSRS. I know that un-installing and
> re-installing sql server 2000 is pretty painless as I've done it many
> times with no problems, however, un-installing and re-installing SSRS 2000
> is a MAJOR pain as it leaves many splinters behind that are difficult to
> deal with prioer to re-installing SSRS.
> My main concern is that I thought I specified the Data files to reside on
> the D drive, however, sql server 2005 installed the data files in:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
> Would it be be painless and trouble free to move the databases to
> D:\MSSQL05\Data, and then from SQL Server Management
> Studio/Properties/Database Settings/Database Default locations, set it to:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
> Thanks.
> --
> moondaddy@.nospam.nospam
>sql

Issues with Un-Installng and Re-Installing SQL Server 2005

Are there any issues with un-installing and re-installing sql server 2005
dev edition? I think it installed SSRS. I know that un-installing and
re-installing sql server 2000 is pretty painless as I've done it many times
with no problems, however, un-installing and re-installing SSRS 2000 is a
MAJOR pain as it leaves many splinters behind that are difficult to deal
with prioer to re-installing SSRS.
My main concern is that I thought I specified the Data files to reside on
the D drive, however, sql server 2005 installed the data files in:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
Would it be be painless and trouble free to move the databases to
D:\MSSQL05\Data, and then from SQL Server Management
Studio/Properties/Database Settings/Database Default locations, set it to:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
Thanks.
moondaddy@.nospam.nospam
Basially I don't see any issues, besides for the fact that you need to make
sure you have a copy of the database master key.
See Books online on how to export it.If you want to move you would be able
to do a database attach / detach.
I didn't really test it myself on RTM but on September CTP I had quite some
issues with it
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
"moondaddy" <moondaddy@.nospam.nospam> wrote in message
news:Oq9jG006FHA.2384@.TK2MSFTNGP12.phx.gbl...
> Are there any issues with un-installing and re-installing sql server 2005
> dev edition? I think it installed SSRS. I know that un-installing and
> re-installing sql server 2000 is pretty painless as I've done it many
> times with no problems, however, un-installing and re-installing SSRS 2000
> is a MAJOR pain as it leaves many splinters behind that are difficult to
> deal with prioer to re-installing SSRS.
> My main concern is that I thought I specified the Data files to reside on
> the D drive, however, sql server 2005 installed the data files in:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
> Would it be be painless and trouble free to move the databases to
> D:\MSSQL05\Data, and then from SQL Server Management
> Studio/Properties/Database Settings/Database Default locations, set it to:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
> Thanks.
> --
> moondaddy@.nospam.nospam
>

Issues with Un-Installng and Re-Installing SQL Server 2005

Are there any issues with un-installing and re-installing sql server 2005
dev edition? I think it installed SSRS. I know that un-installing and
re-installing sql server 2000 is pretty painless as I've done it many times
with no problems, however, un-installing and re-installing SSRS 2000 is a
MAJOR pain as it leaves many splinters behind that are difficult to deal
with prioer to re-installing SSRS.
My main concern is that I thought I specified the Data files to reside on
the D drive, however, sql server 2005 installed the data files in:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
Would it be be painless and trouble free to move the databases to
D:\MSSQL05\Data, and then from SQL Server Management
Studio/Properties/Database Settings/Database Default locations, set it to:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
Thanks.
--
moondaddy@.nospam.nospamBasially I don't see any issues, besides for the fact that you need to make
sure you have a copy of the database master key.
See Books online on how to export it.If you want to move you would be able
to do a database attach / detach.
I didn't really test it myself on RTM but on September CTP I had quite some
issues with it
--
Dandy Weyn
[MCSE-MCSA-MCDBA-MCDST-MCT]
http://www.dandyman.net
Check my SQL Server Resource Pages at http://www.dandyman.net/sql
"moondaddy" <moondaddy@.nospam.nospam> wrote in message
news:Oq9jG006FHA.2384@.TK2MSFTNGP12.phx.gbl...
> Are there any issues with un-installing and re-installing sql server 2005
> dev edition? I think it installed SSRS. I know that un-installing and
> re-installing sql server 2000 is pretty painless as I've done it many
> times with no problems, however, un-installing and re-installing SSRS 2000
> is a MAJOR pain as it leaves many splinters behind that are difficult to
> deal with prioer to re-installing SSRS.
> My main concern is that I thought I specified the Data files to reside on
> the D drive, however, sql server 2005 installed the data files in:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
> Would it be be painless and trouble free to move the databases to
> D:\MSSQL05\Data, and then from SQL Server Management
> Studio/Properties/Database Settings/Database Default locations, set it to:
> C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data?
> Thanks.
> --
> moondaddy@.nospam.nospam
>

Issues with MSDE after installing WMSDE, WSUS

I have a stable 3rd party application which has been running on MSDE Sp3 (ver
2000.80.760.0) as the default instance. I installed WSUS, which apparently
uses WMSDE (version 2000.80.884.0), as a named instance. After this
installation I noticed that the original SQL server has a memory leak,
consuming the resources of the server over a few hours.
I upgraded (replaced) the Sp3 default instance with Sp4 (version
2000.80.2039.0). Howeveer the problem seems to be continuing. Is it wise to
have these 2 different database versions running on the same machine or
should I separate/amalgamate them?
TIA
hi,
Lance wrote:
> I have a stable 3rd party application which has been running on MSDE
> Sp3 (ver 2000.80.760.0) as the default instance. I installed WSUS,
> which apparently uses WMSDE (version 2000.80.884.0), as a named
> instance. After this installation I noticed that the original SQL
> server has a memory leak, consuming the resources of the server over
> a few hours.
> I upgraded (replaced) the Sp3 default instance with Sp4 (version
> 2000.80.2039.0). Howeveer the problem seems to be continuing. Is it
> wise to have these 2 different database versions running on the same
> machine or should I separate/amalgamate them?
> TIA
WMSDE is a modified version of MSDE that enables db size larger then 2gb per
database, that is one of the constraints/limitations of "standard" MSDE, and
is provided for SharePoint, AFAIK..
unfortunately no sp4 for this edition has still been provided, even if it
has been promised...
Andrea Montanari
http://www.asql.biz/DbaMgr.shtm
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

Issues with Microsoft SQL Serever 2005 Express Edition and other versions of SQL Express

I have uninstalled the SQL Server Express Edition that I have installed from the CDs that were given to me during a Chicago Conference when READY TO LAUNCH Visual Studio 2005, SQL SERVER 2005, and Biz Talk 2005.

Then I went to microsoft website: http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx and downloaded and installed the so called Microsoft SQL Server 2005 Express Edition and I got the messages Error that you read below. Then I Uninstalled Microsoft SQL Server 2005 Express Edition and went again to msdn website and downloaded Microsoft SQL Server 2005 Express Edition Advanced Services SP1 and installed it. I got again the same message as below.

MESSAGE:

1. First comes a window with the title: “setup.exe – Unable to Locate Component”
And it displays a message:

This application has failed to start because MSTDCPRX.dll was not found.

Re-installing the application may fix this problem.

2. After I click the OK button of this window it comes another window with the title: “Microsoft SQL Server 2005 Server Setup”

And it displays a message: Failed to load SqlSpars.dll

Does anybody can tell what is going on with the 3 times I tried to installed different SQL Server 2005 Express Edition and I get the same message?

Thanks for your help and support when you have time to respond.

Sincerely,

TonyC

MORE INFORMATION ON THE:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

1. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.txt

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 87

Aborting queue processing as nested installer has completed

Message pump returning: 87

2. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).txt Running: InvokeSqlSetupDllAction at: 2007/1/20 1:22:8

Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.

Unable to load setup helper module : 87

Message displayed to user

Failed to load SqlSpars.dll

Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0001.cab" Error Code : 2

Running: UploadDrWatsonLogAction at: 2007/1/20 1:22:17

Message pump returning: 87

3. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Datastore.xml

<

<S,<Scope Type="SetupStateScope" Id="">

<Property Id="machineName">B3-XP</Property>

<Property Id="logDirectory">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\</Property>

<Property Id="logSummaryFilename">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt</Property>

<Property Id="logSequenceNumber">1</Property>

<Property Id="primaryLogFiles">{ ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Support.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).log"] }</Property>

<Property Id="watsonFailedAction">InvokeSqlSetupDllAction</Property>

<Property Id="watsonFailedActionErrorCode">87</Property>

<Property Id="watsonFailedFunction">sqls::InvokeSqlSetupDllAction::perform</Property>

<Property Id="watsonFailedFunctionErrorCode">87</Property>

<Property Id="watsonSourceFileAndLineNo">setup\sqlsetupactions.cpp@.1709</Property>

<Property Id="watsonModuleAndVersion">setup.exe@.2005.90.3042.0</Property>

<Property Id="watsonMsi">None</Property>

<Property Id="watsonMsiAndVersion">None</Property>

<Property Id="watsonSourceFile">setup\sqlsetupactions.cpp</Property>

</<Scope>

This application has failed to start because MSTDCPRX.dll was not found.

It seems that DTS is corrupted on your computer. Would you reinstall DTC (Distributed Transaction Coordinator) and try setup.exe again?

|||

Can you be more specific because I am not familiar with what you just said.
1. Can you tell me where to find the DTC or where I can download it so I can reinstal or instal?
Does anybody else also has a different suggestion.
Thanks again

|||

I need more help with the SQL Server Express or more other responses, please.
Is anymore people out there who can tell me what to do?
I am still waiting to here from anybody, I check this forum almost twice a day and I see no answers.
I really would appreciate any of your advice if you look through my LOG files?
If you need me to look for some more code in the Log files like the one named something like log_support.txt which is a very long file I will do that as long as you tell me for what specific line or value or string to look.

Please help and thanks for your time if you try to help me.

Sincerely,
TonyCorrona

|||

Hello there,

PLEASE DELETE THIS THREAD.

Thanks and Regards,
TonyC

|||

Thanks to everybody's time reading my thread and trying to help me maybe.
Anyways, I have fixed the problem on my own without having to reinstall Microsoft Distributed Transaction Coordinator and do all the steps that Microsoft People say in their document they provide in msdn.microsoft site.

My problem above I have fixed using some logics of my head and fixed in less then 10 seconds and then tried to install SQL Server Express and it did install it without problem and generated successfull message without any errors and is working fine so far.

Now you can Delete this thread the Microsoft Admin People.
P.S. I like this TechNet forum site but the only lack of this site is that it does not allow us users to delete our own threads.
Maybe I might be misaken but I don't see anywhere a delete button besides the three or sometimes four buttons which
are: Mark as Answer, Reply, Quote and Edit.

Sincerely,
T C

|||

Tony, can you please supply your solution so that it may help others in the future? Congrats on getting it solved. :)

Sam

|||

I am replying to this only on behalf of the users which are struggling with SQL 2005.
If it would be to helping the Programmers or Administrator of MSFT, I would never reply to this blog because they got the job and should try to help people because they get paid for it.
I don't get paid for this to help Microsoft Employee to resolve thier issues.
Myself I am unemployed since last year when I got laid off from a company. Today nobody is helping me with anything, nor to get a job or any interview just because I have only 2 years of work experience.

Anyways let get to the job helping you kindly users.

Since MSFT personnnel could not help me I thought would try to resolve the issue on my own without thier help.

After instaling SQL SERVER 2005, I was missing the MSTDCPRX.dll in the computer that I was installed the SQL 2005 and one thing that I remeber I have done was this.

So I went in another computer that I had Windows XP and searched for the DLL file MSTDCPRX.dll and copy the file and then pasted to the computer that I was missing the file. For those people who do not know where to paste the file, it should be in the directory C:\WINDOWS\system32.

After I copied this file and pasted I did not have any problems anymore with SQL Spars.DLL or any other issues instaling the SQL SERVER 2005.

Hope this will help to all of you who is having problems with SQL SERVER 2005.

Wish you a good day.

Sincerely,

T

Issues with Microsoft SQL Serever 2005 Express Edition and other versions of SQL Express

I have uninstalled the SQL Server Express Edition that I have installed from the CDs that were given to me during a Chicago Conference when READY TO LAUNCH Visual Studio 2005, SQL SERVER 2005, and Biz Talk 2005.

Then I went to microsoft website: http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx and downloaded and installed the so called Microsoft SQL Server 2005 Express Edition and I got the messages Error that you read below. Then I Uninstalled Microsoft SQL Server 2005 Express Edition and went again to msdn website and downloaded Microsoft SQL Server 2005 Express Edition Advanced Services SP1 and installed it. I got again the same message as below.

MESSAGE:

1. First comes a window with the title: “setup.exe – Unable to Locate Component”
And it displays a message:

This application has failed to start because MSTDCPRX.dll was not found.

Re-installing the application may fix this problem.

2. After I click the OK button of this window it comes another window with the title: “Microsoft SQL Server 2005 Server Setup”

And it displays a message: Failed to load SqlSpars.dll

Does anybody can tell what is going on with the 3 times I tried to installed different SQL Server 2005 Express Edition and I get the same message?

Thanks for your help and support when you have time to respond.

Sincerely,

TonyC

MORE INFORMATION ON THE:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

1. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.txt

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 87

Aborting queue processing as nested installer has completed

Message pump returning: 87

2. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).txt Running: InvokeSqlSetupDllAction at: 2007/1/20 1:22:8

Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.

Unable to load setup helper module : 87

Message displayed to user

Failed to load SqlSpars.dll

Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0001.cab" Error Code : 2

Running: UploadDrWatsonLogAction at: 2007/1/20 1:22:17

Message pump returning: 87

3. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Datastore.xml

<

<S,<Scope Type="SetupStateScope" Id="">

<Property Id="machineName">B3-XP</Property>

<Property Id="logDirectory">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\</Property>

<Property Id="logSummaryFilename">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt</Property>

<Property Id="logSequenceNumber">1</Property>

<Property Id="primaryLogFiles">{ ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Support.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).log"] }</Property>

<Property Id="watsonFailedAction">InvokeSqlSetupDllAction</Property>

<Property Id="watsonFailedActionErrorCode">87</Property>

<Property Id="watsonFailedFunction">sqls::InvokeSqlSetupDllAction::perform</Property>

<Property Id="watsonFailedFunctionErrorCode">87</Property>

<Property Id="watsonSourceFileAndLineNo">setup\sqlsetupactions.cpp@.1709</Property>

<Property Id="watsonModuleAndVersion">setup.exe@.2005.90.3042.0</Property>

<Property Id="watsonMsi">None</Property>

<Property Id="watsonMsiAndVersion">None</Property>

<Property Id="watsonSourceFile">setup\sqlsetupactions.cpp</Property>

</<Scope>

This application has failed to start because MSTDCPRX.dll was not found.

It seems that DTS is corrupted on your computer. Would you reinstall DTC (Distributed Transaction Coordinator) and try setup.exe again?

|||

Can you be more specific because I am not familiar with what you just said.
1. Can you tell me where to find the DTC or where I can download it so I can reinstal or instal?
Does anybody else also has a different suggestion.
Thanks again

|||

I need more help with the SQL Server Express or more other responses, please.
Is anymore people out there who can tell me what to do?
I am still waiting to here from anybody, I check this forum almost twice a day and I see no answers.
I really would appreciate any of your advice if you look through my LOG files?
If you need me to look for some more code in the Log files like the one named something like log_support.txt which is a very long file I will do that as long as you tell me for what specific line or value or string to look.

Please help and thanks for your time if you try to help me.

Sincerely,
TonyCorrona

|||

Hello there,

PLEASE DELETE THIS THREAD.

Thanks and Regards,
TonyC

|||

Thanks to everybody's time reading my thread and trying to help me maybe.
Anyways, I have fixed the problem on my own without having to reinstall Microsoft Distributed Transaction Coordinator and do all the steps that Microsoft People say in their document they provide in msdn.microsoft site.

My problem above I have fixed using some logics of my head and fixed in less then 10 seconds and then tried to install SQL Server Express and it did install it without problem and generated successfull message without any errors and is working fine so far.

Now you can Delete this thread the Microsoft Admin People.
P.S. I like this TechNet forum site but the only lack of this site is that it does not allow us users to delete our own threads.
Maybe I might be misaken but I don't see anywhere a delete button besides the three or sometimes four buttons which
are: Mark as Answer, Reply, Quote and Edit.

Sincerely,
T C

|||

Tony, can you please supply your solution so that it may help others in the future? Congrats on getting it solved. :)

Sam

|||

I am replying to this only on behalf of the users which are struggling with SQL 2005.
If it would be to helping the Programmers or Administrator of MSFT, I would never reply to this blog because they got the job and should try to help people because they get paid for it.
I don't get paid for this to help Microsoft Employee to resolve thier issues.
Myself I am unemployed since last year when I got laid off from a company. Today nobody is helping me with anything, nor to get a job or any interview just because I have only 2 years of work experience.

Anyways let get to the job helping you kindly users.

Since MSFT personnnel could not help me I thought would try to resolve the issue on my own without thier help.

After instaling SQL SERVER 2005, I was missing the MSTDCPRX.dll in the computer that I was installed the SQL 2005 and one thing that I remeber I have done was this.

So I went in another computer that I had Windows XP and searched for the DLL file MSTDCPRX.dll and copy the file and then pasted to the computer that I was missing the file. For those people who do not know where to paste the file, it should be in the directory C:\WINDOWS\system32.

After I copied this file and pasted I did not have any problems anymore with SQL Spars.DLL or any other issues instaling the SQL SERVER 2005.

Hope this will help to all of you who is having problems with SQL SERVER 2005.

Wish you a good day.

Sincerely,

T

sql

Issues with Microsoft SQL Serever 2005 Express Edition and other versions of SQL Express

I have uninstalled the SQL Server Express Edition that I have installed from the CDs that were given to me during a Chicago Conference when READY TO LAUNCH Visual Studio 2005, SQL SERVER 2005, and Biz Talk 2005.

Then I went to microsoft website: http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx and downloaded and installed the so called Microsoft SQL Server 2005 Express Edition and I got the messages Error that you read below. Then I Uninstalled Microsoft SQL Server 2005 Express Edition and went again to msdn website and downloaded Microsoft SQL Server 2005 Express Edition Advanced Services SP1 and installed it. I got again the same message as below.

MESSAGE:

1. First comes a window with the title: “setup.exe – Unable to Locate Component”
And it displays a message:

This application has failed to start because MSTDCPRX.dll was not found.

Re-installing the application may fix this problem.

2. After I click the OK button of this window it comes another window with the title: “Microsoft SQL Server 2005 Server Setup”

And it displays a message: Failed to load SqlSpars.dll

Does anybody can tell what is going on with the 3 times I tried to installed different SQL Server 2005 Express Edition and I get the same message?

Thanks for your help and support when you have time to respond.

Sincerely,

TonyC

MORE INFORMATION ON THE:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

1. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.txt

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 87

Aborting queue processing as nested installer has completed

Message pump returning: 87

2. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).txt Running: InvokeSqlSetupDllAction at: 2007/1/20 1:22:8

Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.

Unable to load setup helper module : 87

Message displayed to user

Failed to load SqlSpars.dll

Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0001.cab" Error Code : 2

Running: UploadDrWatsonLogAction at: 2007/1/20 1:22:17

Message pump returning: 87

3. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Datastore.xml

<

<S,<Scope Type="SetupStateScope" Id="">

<Property Id="machineName">B3-XP</Property>

<Property Id="logDirectory">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\</Property>

<Property Id="logSummaryFilename">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt</Property>

<Property Id="logSequenceNumber">1</Property>

<Property Id="primaryLogFiles">{ ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Support.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).log"] }</Property>

<Property Id="watsonFailedAction">InvokeSqlSetupDllAction</Property>

<Property Id="watsonFailedActionErrorCode">87</Property>

<Property Id="watsonFailedFunction">sqls::InvokeSqlSetupDllAction::perform</Property>

<Property Id="watsonFailedFunctionErrorCode">87</Property>

<Property Id="watsonSourceFileAndLineNo">setup\sqlsetupactions.cpp@.1709</Property>

<Property Id="watsonModuleAndVersion">setup.exe@.2005.90.3042.0</Property>

<Property Id="watsonMsi">None</Property>

<Property Id="watsonMsiAndVersion">None</Property>

<Property Id="watsonSourceFile">setup\sqlsetupactions.cpp</Property>

</<Scope>

This application has failed to start because MSTDCPRX.dll was not found.

It seems that DTS is corrupted on your computer. Would you reinstall DTC (Distributed Transaction Coordinator) and try setup.exe again?

|||

Can you be more specific because I am not familiar with what you just said.
1. Can you tell me where to find the DTC or where I can download it so I can reinstal or instal?
Does anybody else also has a different suggestion.
Thanks again

|||

I need more help with the SQL Server Express or more other responses, please.
Is anymore people out there who can tell me what to do?
I am still waiting to here from anybody, I check this forum almost twice a day and I see no answers.
I really would appreciate any of your advice if you look through my LOG files?
If you need me to look for some more code in the Log files like the one named something like log_support.txt which is a very long file I will do that as long as you tell me for what specific line or value or string to look.

Please help and thanks for your time if you try to help me.

Sincerely,
TonyCorrona

|||

Hello there,

PLEASE DELETE THIS THREAD.

Thanks and Regards,
TonyC

|||

Thanks to everybody's time reading my thread and trying to help me maybe.
Anyways, I have fixed the problem on my own without having to reinstall Microsoft Distributed Transaction Coordinator and do all the steps that Microsoft People say in their document they provide in msdn.microsoft site.

My problem above I have fixed using some logics of my head and fixed in less then 10 seconds and then tried to install SQL Server Express and it did install it without problem and generated successfull message without any errors and is working fine so far.

Now you can Delete this thread the Microsoft Admin People.
P.S. I like this TechNet forum site but the only lack of this site is that it does not allow us users to delete our own threads.
Maybe I might be misaken but I don't see anywhere a delete button besides the three or sometimes four buttons which
are: Mark as Answer, Reply, Quote and Edit.

Sincerely,
T C

|||

Tony, can you please supply your solution so that it may help others in the future? Congrats on getting it solved. :)

Sam

|||

I am replying to this only on behalf of the users which are struggling with SQL 2005.
If it would be to helping the Programmers or Administrator of MSFT, I would never reply to this blog because they got the job and should try to help people because they get paid for it.
I don't get paid for this to help Microsoft Employee to resolve thier issues.
Myself I am unemployed since last year when I got laid off from a company. Today nobody is helping me with anything, nor to get a job or any interview just because I have only 2 years of work experience.

Anyways let get to the job helping you kindly users.

Since MSFT personnnel could not help me I thought would try to resolve the issue on my own without thier help.

After instaling SQL SERVER 2005, I was missing the MSTDCPRX.dll in the computer that I was installed the SQL 2005 and one thing that I remeber I have done was this.

So I went in another computer that I had Windows XP and searched for the DLL file MSTDCPRX.dll and copy the file and then pasted to the computer that I was missing the file. For those people who do not know where to paste the file, it should be in the directory C:\WINDOWS\system32.

After I copied this file and pasted I did not have any problems anymore with SQL Spars.DLL or any other issues instaling the SQL SERVER 2005.

Hope this will help to all of you who is having problems with SQL SERVER 2005.

Wish you a good day.

Sincerely,

T

Issues with Microsoft SQL Serever 2005 Express Edition and other versions of SQL Express

I have uninstalled the SQL Server Express Edition that I have installed from the CDs that were given to me during a Chicago Conference when READY TO LAUNCH Visual Studio 2005, SQL SERVER 2005, and Biz Talk 2005.

Then I went to microsoft website: http://msdn.microsoft.com/vstudio/express/sql/register/default.aspx and downloaded and installed the so called Microsoft SQL Server 2005 Express Edition and I got the messages Error that you read below. Then I Uninstalled Microsoft SQL Server 2005 Express Edition and went again to msdn website and downloaded Microsoft SQL Server 2005 Express Edition Advanced Services SP1 and installed it. I got again the same message as below.

MESSAGE:

1. First comes a window with the title: “setup.exe – Unable to Locate Component”
And it displays a message:

This application has failed to start because MSTDCPRX.dll was not found.

Re-installing the application may fix this problem.

2. After I click the OK button of this window it comes another window with the title: “Microsoft SQL Server 2005 Server Setup”

And it displays a message: Failed to load SqlSpars.dll

Does anybody can tell what is going on with the 3 times I tried to installed different SQL Server 2005 Express Edition and I get the same message?

Thanks for your help and support when you have time to respond.

Sincerely,

TonyC

MORE INFORMATION ON THE:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files

1. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.txt

Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run:

"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe" finished and returned: 87

Aborting queue processing as nested installer has completed

Message pump returning: 87

2. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).txt Running: InvokeSqlSetupDllAction at: 2007/1/20 1:22:8

Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.

Unable to load setup helper module : 87

Message displayed to user

Failed to load SqlSpars.dll

Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0001.cab" Error Code : 2

Running: UploadDrWatsonLogAction at: 2007/1/20 1:22:17

Message pump returning: 87

3. C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Datastore.xml

<

<S,<Scope Type="SetupStateScope" Id="">

<Property Id="machineName">B3-XP</Property>

<Property Id="logDirectory">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\</Property>

<Property Id="logSummaryFilename">C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt</Property>

<Property Id="logSequenceNumber">1</Property>

<Property Id="primaryLogFiles">{ ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_.NET Framework 2.0.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Support.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core.log"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt"], ["C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0001_B3-XP_Core(Local).log"] }</Property>

<Property Id="watsonFailedAction">InvokeSqlSetupDllAction</Property>

<Property Id="watsonFailedActionErrorCode">87</Property>

<Property Id="watsonFailedFunction">sqls::InvokeSqlSetupDllAction::perform</Property>

<Property Id="watsonFailedFunctionErrorCode">87</Property>

<Property Id="watsonSourceFileAndLineNo">setup\sqlsetupactions.cpp@.1709</Property>

<Property Id="watsonModuleAndVersion">setup.exe@.2005.90.3042.0</Property>

<Property Id="watsonMsi">None</Property>

<Property Id="watsonMsiAndVersion">None</Property>

<Property Id="watsonSourceFile">setup\sqlsetupactions.cpp</Property>

</<Scope>

This application has failed to start because MSTDCPRX.dll was not found.

It seems that DTS is corrupted on your computer. Would you reinstall DTC (Distributed Transaction Coordinator) and try setup.exe again?

|||

Can you be more specific because I am not familiar with what you just said.
1. Can you tell me where to find the DTC or where I can download it so I can reinstal or instal?
Does anybody else also has a different suggestion.
Thanks again

|||

I need more help with the SQL Server Express or more other responses, please.
Is anymore people out there who can tell me what to do?
I am still waiting to here from anybody, I check this forum almost twice a day and I see no answers.
I really would appreciate any of your advice if you look through my LOG files?
If you need me to look for some more code in the Log files like the one named something like log_support.txt which is a very long file I will do that as long as you tell me for what specific line or value or string to look.

Please help and thanks for your time if you try to help me.

Sincerely,
TonyCorrona

|||

Hello there,

PLEASE DELETE THIS THREAD.

Thanks and Regards,
TonyC

|||

Thanks to everybody's time reading my thread and trying to help me maybe.
Anyways, I have fixed the problem on my own without having to reinstall Microsoft Distributed Transaction Coordinator and do all the steps that Microsoft People say in their document they provide in msdn.microsoft site.

My problem above I have fixed using some logics of my head and fixed in less then 10 seconds and then tried to install SQL Server Express and it did install it without problem and generated successfull message without any errors and is working fine so far.

Now you can Delete this thread the Microsoft Admin People.
P.S. I like this TechNet forum site but the only lack of this site is that it does not allow us users to delete our own threads.
Maybe I might be misaken but I don't see anywhere a delete button besides the three or sometimes four buttons which
are: Mark as Answer, Reply, Quote and Edit.

Sincerely,
T C

|||

Tony, can you please supply your solution so that it may help others in the future? Congrats on getting it solved. :)

Sam

|||

I am replying to this only on behalf of the users which are struggling with SQL 2005.
If it would be to helping the Programmers or Administrator of MSFT, I would never reply to this blog because they got the job and should try to help people because they get paid for it.
I don't get paid for this to help Microsoft Employee to resolve thier issues.
Myself I am unemployed since last year when I got laid off from a company. Today nobody is helping me with anything, nor to get a job or any interview just because I have only 2 years of work experience.

Anyways let get to the job helping you kindly users.

Since MSFT personnnel could not help me I thought would try to resolve the issue on my own without thier help.

After instaling SQL SERVER 2005, I was missing the MSTDCPRX.dll in the computer that I was installed the SQL 2005 and one thing that I remeber I have done was this.

So I went in another computer that I had Windows XP and searched for the DLL file MSTDCPRX.dll and copy the file and then pasted to the computer that I was missing the file. For those people who do not know where to paste the file, it should be in the directory C:\WINDOWS\system32.

After I copied this file and pasted I did not have any problems anymore with SQL Spars.DLL or any other issues instaling the SQL SERVER 2005.

Hope this will help to all of you who is having problems with SQL SERVER 2005.

Wish you a good day.

Sincerely,

T

Issues Renaming Analysis Server Instance

Hi Friends

I want to rename My Analysis Services Instance installed on E: Drive. I read an article how to rename the Analysis Service Instance . Then I followed 64-bit path to rename, but it gives the following error rolling back to the original Instance Name:

Registering the new performance counters file:

LoadPerfCounterTextStrings for file C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\bin\msmdctr.ini failed with error code 2

The System cannot find the file Specified

Has anybody came across this issue. Any workarounds ?

Thanks

Subhash Subramanyam.

Hi Subash,

I need few more info from you before I troubleshoot the issue.

1) What was the intial folder your Analysis Service resides? ex: E:\program files\mssql.1\olap\bin

2) What was the original instance name and what did you rename to?

3) Do you get this error from asinstancerename tool?

Thanks,

Deva

|||

1) What was the intial folder your Analysis Service resides? ex: E:\program files\mssql.1\olap\bin

C:\Program Files\Microsoft SQL Server\MSSQL.1\OLAP\bin

2) What was the original instance name and what did you rename to?

original instance name: ss2005

rename to: as2005

3) Do you get this error from asinstancerename tool?

Yes

Hope this helps.

Thanks

Subhash Subramanyam

Issues creating a new failover cluster on the same server

We have a sans and a server box that currently has a SQL 2005 Failover
cluster installed, we are attempting to install a new SQL 2005 Failover
cluster but ran into an issue. After setting up the new cluster group and
installing the instance to this group the installer modified the SQL browser
to use a log file located in my second cluster group (chnsql04). This caused
the CHSSQL04 to fail and not allow logins from remote connections even though
the surface area configuration was set to allow remote and local logons. Once
I changed the path back to g:\ drive my chssql04 cluster works but my
chnsql04 cluster does not.
How can resolve this issue?
We have a second group of users wanting to use our server and we don’t want
them to see the data in the chssql04 cluster which is why we created a new
cluster and instance.
Would it be better to setup the server so that the server program files
“program files\SQL 2005\” are located on one drive that is seen by both
clusters and then create a data drive for each of the cluster groups to store
the db on?
If so how can I share a resource between two clusters?
We have the following setup for our SQL Fail over cluster:
CHSSQL04 Cluster Group
Drives: E, G, K, S, Z
Two file shares
SQL IP address (10.0.50.48)
SQL Network Name (vssql04)
SQL Server (instance name)
SQL server agent (instance name)
SQL Server Fulltext (instance name)
The sql server data and program files are installed on G:
New cluster group setup:
CHNSQL04 Cluster Group
Drives: H and F
The setup then created the following:
SQL IP address (10.0.50.68)
SQL Network name (chnvssql04)
SQL Server (instance name)
SQL server agent (instance name)
SQL Server Fulltext (instance name)
The sql server data and program files are installed on H:
Thanks in advanced,
Daniel
First of all, the Browser service is not cluster-aware and only runs on the
local nodes.
Second, the program files must reside on all participating nodes, for each
instance, in dedicated folders for that instance, sequentially numbered, on
local drives only; they can't reside on the shared drives. So, like on each
node's D: drive, \MSSQL.01, \MSSQL.02, etc.
Each virtual instance will require a separate resource group with dedicated
IP, Network Name, Disk(s), and SQL Server Instance names. You have
indicated some, but not all, of this information. They must be unique.
Lastly, either allow dynamic port generation, or follow the best practice
and select unique dedicated ports.
Here are the links to the documents. Both are relevant, although not
entirely.
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/failclus.mspx
http://www.microsoft.com/downloads/details.aspx?FamilyID=818234dc-a17b-4f09-b282-c6830fead499&DisplayLang=en
Sincerely,
Anthony Thomas

"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:AAD449C6-D287-44A8-BE1E-1B36B0982A04@.microsoft.com...
> We have a sans and a server box that currently has a SQL 2005 Failover
> cluster installed, we are attempting to install a new SQL 2005 Failover
> cluster but ran into an issue. After setting up the new cluster group and
> installing the instance to this group the installer modified the SQL
browser
> to use a log file located in my second cluster group (chnsql04). This
caused
> the CHSSQL04 to fail and not allow logins from remote connections even
though
> the surface area configuration was set to allow remote and local logons.
Once
> I changed the path back to g:\ drive my chssql04 cluster works but my
> chnsql04 cluster does not.
> How can resolve this issue?
> We have a second group of users wanting to use our server and we don't
want
> them to see the data in the chssql04 cluster which is why we created a new
> cluster and instance.
> Would it be better to setup the server so that the server program files
> "program files\SQL 2005\" are located on one drive that is seen by both
> clusters and then create a data drive for each of the cluster groups to
store
> the db on?
> If so how can I share a resource between two clusters?
>
> We have the following setup for our SQL Fail over cluster:
> CHSSQL04 Cluster Group
> Drives: E, G, K, S, Z
> Two file shares
> SQL IP address (10.0.50.48)
> SQL Network Name (vssql04)
> SQL Server (instance name)
> SQL server agent (instance name)
> SQL Server Fulltext (instance name)
> The sql server data and program files are installed on G:
> New cluster group setup:
> CHNSQL04 Cluster Group
> Drives: H and F
> The setup then created the following:
> SQL IP address (10.0.50.68)
> SQL Network name (chnvssql04)
> SQL Server (instance name)
> SQL server agent (instance name)
> SQL Server Fulltext (instance name)
> The sql server data and program files are installed on H:
>
> Thanks in advanced,
> Daniel
|||Anthony,
To answer some of the items you have pointed out we have the following setup.
We have two nodes
Chssq04a – active
Chssq04p – passive
For clarification: there are two groups with the prefixes: CHS and CHN
We have two cluster groups; chnsq04 group is the new cluster and where the
new sql instance is being installed. Both SQL instances are installed on the
active node, CHSSQ04A.
CHSSQ04 Group
Assigned nodes: Chssq04a and Chssq04p
CHNSQ04 Group
Assigned nodes: Chssq04a and Chssq04p
Each virtual instance is unique with its own disks, ip, network name, and
instance name.
CHSSQ04 Group
Drives: E, G, K, S, Z
Two file shares
SQL IP address (10.0.50.48)
SQL Network Name (vssql04)
SQL Server (CHSNextgen)
SQL server agent (CHSNextgen)
SQL Server Fulltext (CHSNextgen)
SQL 2005 is installed for this instance at
G:\Microsoft SQL Server\MSSQL.1
CHNSQL04 Cluster Group
Drives: H and F
The setup then created the following:
SQL IP address (10.0.50.68)
SQL Network name (chnvssql04)
SQL Server (CHNNextgen)
SQL server agent (CHNNextgen)
SQL Server Fulltext (CHNNextgen)
SQL 2005 is installed for this instance at
H:\Microsoft SQL Server\MSSQL.2
We are not sharing drives for each cluster group and instance, they have
their own drives, and this means that CHNSQL04 can not see drives that are
used by CHSSQL04 and visa versa.
What I think your going to tell me is that I can not have two SQL Cluster
groups on the same node because the SQL Browser is not cluster aware and thus
can not see both clusters running at the same time. This is why I can not
start my second cluster group and instance.
|||Either your system is hoplessly messed up or your terminology is hosed.
First, unless you are running SQL 7.0, all cluster nodes are equivalent.
Active and Passive designations are arbitrary and only reflect the current
state, not the system configuration.
A computer can only belong to a single cluster at a time and is typically
called a node when it is a cluster member.
Instance = group = virtual server. The terms mean exactly the same thing.
Instances are installed to the cluster, not to individual nodes. While it
is possible to set up SQL to not use specific cluster nodes, that is almost
never done on a two node cluster. After the installation is correctly
completed, there is no difference between the nodes. You can install from
one node, shift the group to the other node, and apply a service pack. The
SQL installer handles the situation correctly and updates the binaries on
each node and the database instance on the currently active node.
The first group/virtual server is the cluster group. Later groups map to
specific SQL instances. Nodes host zero or more groups.
The SQL Browser service is not cluster aware and should not use any
resources that come from any cluster group. Each node's browser service
must be configured separately.
Could you rewrite your question using the above terminology? I think the
answer will be fairly easy once we can see what you mean.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:C082F024-7E12-4F4D-A822-4E93503D0DD4@.microsoft.com...
> Anthony,
> To answer some of the items you have pointed out we have the following
> setup.
> We have two nodes
> Chssq04a – active
> Chssq04p – passive
> For clarification: there are two groups with the prefixes: CHS and CHN
> We have two cluster groups; chnsq04 group is the new cluster and where the
> new sql instance is being installed. Both SQL instances are installed on
> the
> active node, CHSSQ04A.
> CHSSQ04 Group
> Assigned nodes: Chssq04a and Chssq04p
> CHNSQ04 Group
> Assigned nodes: Chssq04a and Chssq04p
> Each virtual instance is unique with its own disks, ip, network name, and
> instance name.
> CHSSQ04 Group
> Drives: E, G, K, S, Z
> Two file shares
> SQL IP address (10.0.50.48)
> SQL Network Name (vssql04)
> SQL Server (CHSNextgen)
> SQL server agent (CHSNextgen)
> SQL Server Fulltext (CHSNextgen)
> SQL 2005 is installed for this instance at
> G:\Microsoft SQL Server\MSSQL.1
>
> CHNSQL04 Cluster Group
> Drives: H and F
> The setup then created the following:
> SQL IP address (10.0.50.68)
> SQL Network name (chnvssql04)
> SQL Server (CHNNextgen)
> SQL server agent (CHNNextgen)
> SQL Server Fulltext (CHNNextgen)
> SQL 2005 is installed for this instance at
> H:\Microsoft SQL Server\MSSQL.2
> We are not sharing drives for each cluster group and instance, they have
> their own drives, and this means that CHNSQL04 can not see drives that are
> used by CHSSQL04 and visa versa.
> What I think your going to tell me is that I can not have two SQL Cluster
> groups on the same node because the SQL Browser is not cluster aware and
> thus
> can not see both clusters running at the same time. This is why I can not
> start my second cluster group and instance.
>
|||In addition to Geoff's comments, I do have some remarks regarding your
comments.
CHSSQ04 Group
Drives: E, G, K, S, Z
G:\Microsoft SQL Server\MSSQL.1
and
CHNSQL04 Cluster Group
Drives: H and F
H:\Microsoft SQL Server\MSSQL.2
You host the database files, logs, etc. on a shared drive, but not the
binaries, they are installed on the local node drives for each cluster
member. What drives are the binaries installed on?
Later:
We are not sharing drives for each cluster group and instance, they have
their own drives, and this means that CHNSQL04 can not see drives that
are
used by CHSSQL04 and visa versa.
Whenever resources are running on one of the nodes, then all resources for
each network name are available on that node. So, if you have the Cluster
Group, the MS DTC Group, and each of the SQL Server Instance Groups running
on the same node, then you will see all of the resources if you connect to
the Node name, the Cluster name, the MS DTC name, the SQL Instance 1 name,
and the SQL Instance 2 name, including any network shares.
The point about clustering network shares is that those shares come online
and offline along with the resource group. So, if the group is on node 1,
then so are the shares and not visible from node 2. If you move group
resources to node 2, then the resources go offline on node 1 and come online
on node 2.
This configuration does nothing about securing what each instance will
"see."
Lastly, for the browser service, it runs on each node and translates
Instance Names to Port Numbers to connect to. It is not clustered, and runs
as an individual server service on every node of the cluster, just like the
Cluster service, Event Log, Server and Workstation, IPSec, or whatever other
stand alone application being hosted. So, on each cluster node, the browser
service needs to be installed on a local drive and its associated log file
located there as well. It cannot exist on any of the Cluster Resource Group
drives.
Everyone here is more than happy to help you work through this; however,
please read through the documentation provided in the links from my first
reply. It seems to me that you have a basic misunderstanding about what
clustering is, and it is affecting your installation decisions
inappropriately.
The simplest way I can describe it is thusly. If you installed SS to a
stand-alone server, hopefully, you would install the binaries to one drive,
your data files on a dedicated second drive, transaction logs to a third,
and perhaps dedicate the database backups to a 4th and the tempdb to a 5th.
Now, you want have a cold standby. You would install the binaries to a
second server, hopefully in a similar location, but you would be relying on
the SAN guys to be able to move your volumes for your database files, logs,
backups, tempdb, etc., and present them to this second server in the event
of a disaster. If you imported those drives and then lettered them the same
as they were on the first server, then you should be able to turn the
services on without any problem.
Clustering adds more complexity to this solution, but in essence does
exactly this, but automatically, and unlike the scenario above where the two
server names would be different, the cluster presents a virtual server name
and IP address to the public that does not change when resources run on one
server or the other; so, except for the offline and online sequence, remains
transparent to the end users.
However, what is required is to have the binaries on local drives of each
node. The services have to be installed on each node; it is just that only
one server at a time is actually running that service for those items that
have been added as a cluster resource. All other server service must be
online on all cluster nodes.
I hope this helps.
Sincerely,
Anthony Thomas
"Dan" <Dan@.discussions.microsoft.com> wrote in message
news:C082F024-7E12-4F4D-A822-4E93503D0DD4@.microsoft.com...
> Anthony,
> To answer some of the items you have pointed out we have the following
setup.
> We have two nodes
> Chssq04a - active
> Chssq04p - passive
> For clarification: there are two groups with the prefixes: CHS and CHN
> We have two cluster groups; chnsq04 group is the new cluster and where the
> new sql instance is being installed. Both SQL instances are installed on
the
> active node, CHSSQ04A.
> CHSSQ04 Group
> Assigned nodes: Chssq04a and Chssq04p
> CHNSQ04 Group
> Assigned nodes: Chssq04a and Chssq04p
> Each virtual instance is unique with its own disks, ip, network name, and
> instance name.
> CHSSQ04 Group
> Drives: E, G, K, S, Z
> Two file shares
> SQL IP address (10.0.50.48)
> SQL Network Name (vssql04)
> SQL Server (CHSNextgen)
> SQL server agent (CHSNextgen)
> SQL Server Fulltext (CHSNextgen)
> SQL 2005 is installed for this instance at
> G:\Microsoft SQL Server\MSSQL.1
>
> CHNSQL04 Cluster Group
> Drives: H and F
> The setup then created the following:
> SQL IP address (10.0.50.68)
> SQL Network name (chnvssql04)
> SQL Server (CHNNextgen)
> SQL server agent (CHNNextgen)
> SQL Server Fulltext (CHNNextgen)
> SQL 2005 is installed for this instance at
> H:\Microsoft SQL Server\MSSQL.2
> We are not sharing drives for each cluster group and instance, they have
> their own drives, and this means that CHNSQL04 can not see drives that are
> used by CHSSQL04 and visa versa.
> What I think your going to tell me is that I can not have two SQL Cluster
> groups on the same node because the SQL Browser is not cluster aware and
thus
> can not see both clusters running at the same time. This is why I can not
> start my second cluster group and instance.
>
|||Thanks for all your input so far and I apologize that I have my terminology
wrong. After reading through the documentation and what you have posted let
me try and repost what our current setup is.
We have two nodes in our active passive cluster, sq04a and sq04p, sq04a is
the active node and sq04p is the passive node.
We created a cluster called CHSSQ04 and inside of this cluster we created
several groups; CHSSQ04, Cluster, and MSDTC.
The group Cluster has our Quorum Disk, Cluster IP, and Cluster Name. The
group called MSDTC has our MSDTC disk, MSDTC IP Address, MSDTC Network name,
and MSDTC Resource.
Note: All of the disks are also part of the sans, and the sans has been set
to allow the two nodes to see the disks, but only the node that is active can
be using the disks.
For each of the groups we assigned the two nodes as the preferred owner.
In our sans we created 5 more drives (LUNS) and give both nodes permission
to use the drives, just like the other ones listed above. So when we open up
disk management on both nodes we see the drives, but only the active server
can see drive name and if its been formatted.
We then went to the active node and formatted the drives and assigned drive
letters. The passive node at this point still only sees the drives as
unformatted and with no drive letters assigned. We then created disk
resources for the 5 disks and assigned them to the CHSQ04 group, since this
is where the SQL instance is going to be at.
Note: yes we do have two things in our setup named CHSSQ04, the actual
cluster is called CHSSQ04 and then there is a group called chssq04 group.
By doing so the SQL installer created an instance and setup the SQL IP
Address, SQL Network Name, SQL Server (with the instance name CHSNextgen),
SQL Server Agent (CHSNextgen), and SQL Server Fulltext (CHSNextgen).
So now we have a SQL server with the name vsSQL04 with a public ip address
and an instance called CHSNextgen. We then setup our database and move are
data into and set the clients to use vsSQL04\chsnextgen to connect to the db.
The SQL installer also created binaries for the instance on the c:\ drive of
both nodes. It looks like this;
C:\Program Files\Microsoft SQL Server>dir
Volume in drive C has no label.
Volume Serial Number is 44E8-2F28
Directory of C:\Program Files\Microsoft SQL Server
02/06/2007 10:18 AM <DIR> .
02/06/2007 10:18 AM <DIR> ..
11/10/2006 10:22 AM <DIR> 80
01/16/2007 10:25 PM <DIR> 90
11/10/2006 10:26 AM <DIR> MSSQL.1
11/20/2006 08:49 AM 4,286,976 SQLUASetup.msi
1 File(s) 4,286,976 bytes
6 Dir(s) 109,489,816,576 bytes free
And on G: we have the following,
G:\Microsoft SQL Server\MSSQL.1\MSSQL>dir
Volume in drive G is SQL Data Primary
Volume Serial Number is FE52-BCF2
Directory of G:\Microsoft SQL Server\MSSQL.1\MSSQL
02/04/2007 09:59 AM <DIR> .
02/04/2007 09:59 AM <DIR> ..
02/05/2007 12:58 AM <DIR> Backup
02/04/2007 09:59 AM <DIR> Data
11/10/2006 10:26 AM <DIR> FTData
11/10/2006 10:26 AM <DIR> JOBS
02/12/2007 02:07 PM <DIR> LOG
11/10/2006 10:26 AM <DIR> repldata
0 File(s) 0 bytes
8 Dir(s) 28,332,949,504 bytes free
This works great and fails over the way it should. In our test we turned off
sq04a and the cluster failed over to sq04p with all the drive letters and
instance. So everything worked the way it should.
What we are trying to do is create another SQL fail over instance on the
same active node so that when someone is in the SQL management console for
the new instance they can not see the drives nor the data in the first SQL
instance named vsSQL04. What I did to try and accomplish this was create a
new group in the cluster called chnsq04, then assign more drives to this
group for the new instance. I started the setup and selected SQL fail over
cluster, create a new instance, and then selected the new chnsq04 group. The
setup created the instance and placed the files and folders where they need
to be, but after the install finished the SQL browser stopped and caused our
first instance in the other group to stop accepting and dropped connections.
I have since removed the new instance and group and corrected a few issues
with the admin port and the SQL browser
Now you guys have both noted that there should be a SQL browser for each
instance, well I only have one. If I look at the SQL server browser
properties from the SQL server configuration manager, I notice that the dump
directory is set to use G:\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\. When I
had installed the second instance it changed this value to H:\Microsoft SQL
Server\MSSQL.2\MSSQL\LOG\ which caused my first instance to die. Also my
adminConnection/tcp port was deleted, which I have already resolved.
On a side note, our setup (before we attempted to create another fail over
instance) was done by EMC/Dell according to a MS guide. The only thing I was
trying to do was mimic the same setup for a new group so I could have a new
virtual server name and instance, if this is at all possible.
I hope this clarifies what is going on and what I am trying to accomplish.