Loss of Server

I'm not sure if this is a Windows issue or a SQL Server in a cluster issue,
but it's strange.
We have a Windows 2003 Server Enterprise w/SP2 Running in a cluster. The
only thing on these servers is SQL Server. It's behind a firewall with only
the SQL ports open.
The problem we are running into is that from time to time, the primary node
in the SQL Cluster become unresponsive to the public NIC and the heartbeat
NIC and it doesn't failover. You can't RDP to it and the Cluster
administrator doesn't pick it up. You can't even ping the primary or
heartbeat from the passive node. It's like it is just not there.
There is a monitor NIC on this server as well, and they are throwing NO
alarms.
After about 20 minutes, it comes back.
Should this go to the Cluster group? Any suggestions?I would suggest taking it to the Windows Cluster group. I believe SQL runs
on top of the Cluster service, so.
"Kevin A" <kevina@.cqlcorp.com> wrote in message
news:Oo9HQ5FiIHA.4468@.TK2MSFTNGP03.phx.gbl...
> I'm not sure if this is a Windows issue or a SQL Server in a cluster
> issue, but it's strange.
> We have a Windows 2003 Server Enterprise w/SP2 Running in a cluster. The
> only thing on these servers is SQL Server. It's behind a firewall with
> only the SQL ports open.
> The problem we are running into is that from time to time, the primary
> node in the SQL Cluster become unresponsive to the public NIC and the
> heartbeat NIC and it doesn't failover. You can't RDP to it and the
> Cluster administrator doesn't pick it up. You can't even ping the primary
> or heartbeat from the passive node. It's like it is just not there.
> There is a monitor NIC on this server as well, and they are throwing NO
> alarms.
> After about 20 minutes, it comes back.
> Should this go to the Cluster group? Any suggestions?
>

Lookup Component Feature

Has anyone seen this strange behaviour?

I have a package which loads the fact data from Stage into Warehouse database. This packages normally handles early arriving facts. In that package I use lookup to check the dims which exists, and where they don't I populate the dimension and use the surrogate key to load the facts. This works fine.

I had a request to load 7 years worth of historical data. Instead of re-writing the package I took the package which handles early arriving facts and deleted the section which handles early arriving facts. I knew all the dimensions already exists and I don’t want to hinder the performance when I load millions of rows. During testing I found something very interesting.

If you have configured error path in the lookup component and removed the error path later, the package will NOT fail (won't produce error) even if the lookup can't find matching values.

Correct Behaviour Example 1:
[1] Stage fact table has 2 records, with product code 1 and 2.
[2] Warehouse Product table has only product code 1.
[3] Source - Lookup - Destination in the data flow task. Error port on lookup is not configured.
[4] From source we read 2 records, and the package will fail at lookup as it can't find Product Code 2.

Correct Behaviour Example 2:
[1] Stage fact table has 2 records, with product code 1 and 2.
[2] Warehouse Product table has only product code 1.
[3] Source - Lookup - Destination in the data flow task. Error port on lookup is configured to go to RowCount.
[4] From source we read 2 records, and the package will run successfully. It will put one record into warehouse table and send the invalid record into RowCount.

Incorrect Behaviour Example 3:
[1] Stage fact table has 2 records, with product code 1 and 2.
[2] Warehouse Product table has only product code 1.
[3] Source - Lookup - Destination in the data flow task. Delete the configured error port from lookup.
[4] From source we read 2 records, and the package will run successfully. It will put one record into warehouse table and discard the other.

My understanding if the error port is NOT configured as shown in example 2, it should fail as shown in example 1.

Am I missing a point or is this suppose to be a correct behaviour or is it a bug?

Thanks

Sutha

If you want Lookup to fail, set error disposition to Fail Component, instead of redirecting the row to error output - the error disposition controls the component fail/not-fail behavior.

If nothing is connected to error path, the redirected rows are lost, but this is not signalled as failure - there are legitimate reasons to have packages where you don't care about such rows, and want to continue package without signalling an error.

Looking for sqlrun_tools.msi

Today my computer started doing something strange when trying to compile a setup&deployment project. This project doesn't contain anything related to sql server whatsoever.

When i compile, it pops up a windows installer dialog that starts doing something. Eventually it asks me for my Sql Server 2005 Tools disc, specifically looking for sqlrun_tools.msi.

I tried putting in the disc that i'm pretty sure it was installed from (my MSDN disc) but it told me that the sqlrun_tools.msi on that disc wasn't the right one.

I have no idea why its asking me for this at this time, nor do i know to do to get it to stop.

Thanks in advance for any help.

Are you familiar with using the event viewer (Start->Run->eventvwr.msc). There should be some events around the time that you saw the popup where the source is "MsiInstaller" (I believe). The content of the event should mention that a component was missing and that a feature is being installed to repair it.

If you can locate these events, could you post the details to the forum? I suspect the missing component could be related to mergemod.dll, but that is just a guess.

|||

I am having the same problem.

Whenever I try and build a setup project I see a dialogue saying "Please wait while Windows configures SQL Server 2005 Tools", with a cancel button.

If I do wait then I am eventually told that "An installation package for the product Microsoft SQL Server 2005 Tools cannot be found. Try the installation again using a valid copy of the installation package 'SQLRun_Tools.msi'"

If I just cancel that dialogue my setup project runs just fine.

Any ideas on how to fix this?

Here are the 2 events:

Detection of product '{7085A287-2F7E-420C-B0D9-53AFA8341154}', feature 'SQL_Tools90' failed during request for component '{FD153241-37EC-11D2-8892-00A0C981B015}'

Detection of product '{7085A287-2F7E-420C-B0D9-53AFA8341154}', feature 'SQL_Tools90', component '{7A4BD8A8-24AE-492A-84F5-9A4DEB2DD0AB}' failed. The resource 'C:\Program Files\Microsoft SQL Server\90\DTS\LogProviders\' does not exist.

|||

Do you still have the SQL Server 2005 Tools installed? This error might be related to a missing "LogProviders" folder underneath %PROGRAMFILES%\Microsoft Sql Server\90\DTS. Could you confirm if that folder is there?

We have some options here. The first is to try and repair your tools install. The second is to try and defeat the resiliency checks Windows Installer is invoking when you build a setup project, which can be done via installing an updated version of Orca or by fiddling in the registry. Based on your reply we can proceed with the next steps.

|||

Thanks for your reply.

The folder was not there. I created the following folders and it seems to have solved the problem, at least for the project I am currently building.

C:\Program Files\Microsoft SQL Server\90\DTS\LogProviders

C:\Program Files\Microsoft SQL Server\90\DTS\Packages

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\SDK\v2.0\Bin

C:\Program Files\Microsoft SQL Server\90\Shared\ErrorDumps

Not sure if this is relevant to anyone else who is having this problem but when I checked to see if SQL Server 2005 Management Studio was still installed I got a message telling me my Evaluation period has expired. I haven't used it since installing it a while back so hadn't noticed.

Thanks again for your help.

|||

I too am having the same issue. I found that the LogProviders directory was missing, so I created that folder but to no avail. however, instead of running three times, I only get the MSI installer once now.

I'm not sure that this has anything to do with anything, but I have the Express ver installed of 2005, not the full ver or even the eval edition.

Any ideas or registry fixes would be much appreceated.

Thanks.

|||

Hi,

TimMulholland wrote:

I tried putting in the disc that i'm pretty sure it was installed from (my MSDN disc) but it told me that the sqlrun_tools.msi on that disc wasn't the right one.

You would find that in your SQL Server Setup CD and not in MSDN CD, try with it. Have you tried creating a package with SQL Server Installer / Setup stripped with the Application ?! if yes it would ask you the same.

Hemantgiri S. Goswami

|||

I had a similar problem and i solved it by uninstalling de workstation components from SQL Server 2005 (more exactly the management studio) and then installing it again. The problem disappeared.

The problem occured when using Guidance packages and setup projects.

greetz,

beloega

Looking for sqlrun_tools.msi

Today my computer started doing something strange when trying to compile a setup&deployment project. This project doesn't contain anything related to sql server whatsoever.

When i compile, it pops up a windows installer dialog that starts doing something. Eventually it asks me for my Sql Server 2005 Tools disc, specifically looking for sqlrun_tools.msi.

I tried putting in the disc that i'm pretty sure it was installed from (my MSDN disc) but it told me that the sqlrun_tools.msi on that disc wasn't the right one.

I have no idea why its asking me for this at this time, nor do i know to do to get it to stop.

Thanks in advance for any help.

Are you familiar with using the event viewer (Start->Run->eventvwr.msc). There should be some events around the time that you saw the popup where the source is "MsiInstaller" (I believe). The content of the event should mention that a component was missing and that a feature is being installed to repair it.

If you can locate these events, could you post the details to the forum? I suspect the missing component could be related to mergemod.dll, but that is just a guess.

|||

I am having the same problem.

Whenever I try and build a setup project I see a dialogue saying "Please wait while Windows configures SQL Server 2005 Tools", with a cancel button.

If I do wait then I am eventually told that "An installation package for the product Microsoft SQL Server 2005 Tools cannot be found. Try the installation again using a valid copy of the installation package 'SQLRun_Tools.msi'"

If I just cancel that dialogue my setup project runs just fine.

Any ideas on how to fix this?

Here are the 2 events:

Detection of product '{7085A287-2F7E-420C-B0D9-53AFA8341154}', feature 'SQL_Tools90' failed during request for component '{FD153241-37EC-11D2-8892-00A0C981B015}'

Detection of product '{7085A287-2F7E-420C-B0D9-53AFA8341154}', feature 'SQL_Tools90', component '{7A4BD8A8-24AE-492A-84F5-9A4DEB2DD0AB}' failed. The resource 'C:\Program Files\Microsoft SQL Server\90\DTS\LogProviders\' does not exist.

|||

Do you still have the SQL Server 2005 Tools installed? This error might be related to a missing "LogProviders" folder underneath %PROGRAMFILES%\Microsoft Sql Server\90\DTS. Could you confirm if that folder is there?

We have some options here. The first is to try and repair your tools install. The second is to try and defeat the resiliency checks Windows Installer is invoking when you build a setup project, which can be done via installing an updated version of Orca or by fiddling in the registry. Based on your reply we can proceed with the next steps.

|||

Thanks for your reply.

The folder was not there. I created the following folders and it seems to have solved the problem, at least for the project I am currently building.

C:\Program Files\Microsoft SQL Server\90\DTS\LogProviders

C:\Program Files\Microsoft SQL Server\90\DTS\Packages

C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\SDK\v2.0\Bin

C:\Program Files\Microsoft SQL Server\90\Shared\ErrorDumps

Not sure if this is relevant to anyone else who is having this problem but when I checked to see if SQL Server 2005 Management Studio was still installed I got a message telling me my Evaluation period has expired. I haven't used it since installing it a while back so hadn't noticed.

Thanks again for your help.

|||

I too am having the same issue. I found that the LogProviders directory was missing, so I created that folder but to no avail. however, instead of running three times, I only get the MSI installer once now.

I'm not sure that this has anything to do with anything, but I have the Express ver installed of 2005, not the full ver or even the eval edition.

Any ideas or registry fixes would be much appreceated.

Thanks.

|||

Hi,

TimMulholland wrote:

I tried putting in the disc that i'm pretty sure it was installed from (my MSDN disc) but it told me that the sqlrun_tools.msi on that disc wasn't the right one.

You would find that in your SQL Server Setup CD and not in MSDN CD, try with it. Have you tried creating a package with SQL Server Installer / Setup stripped with the Application ?! if yes it would ask you the same.

Hemantgiri S. Goswami

|||

I had a similar problem and i solved it by uninstalling de workstation components from SQL Server 2005 (more exactly the management studio) and then installing it again. The problem disappeared.

The problem occured when using Guidance packages and setup projects.

greetz,

beloega