Microsoft iSCSI Initiator & SQL Server services

Hello all,
I have Microsoft iSCSI Initiator (SAN) installed on a SQL Server machine and has this drive acting as a local drive. All the database's data files are residing on this drive, attached with SAN.
It runs as a service "Microsoft iSCSI Initiator" on the SQL Server machine.

Now the question is, when we restart the SQL Server all the databases change their status to "Suspect" and we have to stop all the sqlserver services (all the SQL instances) and start them all up. This is the only temporary solution we came up with.
Could any one has any real solution or had encounter such a problem before?

Any help is appreciated.

Thanks bunch!
imransi.Looks like your SQL Service starts before your SAN is available.|||Originally posted by rdjabarov
Looks like your SQL Service starts before your SAN is available.

You are 100% right. So thats why we are restarting SQL services.
We can manually start sql services but thats not what we wnat and really thsi should not be the solutuion ;)|||See if you can "impose" a dependency on MSSQLSERVER service in regards to this SAN service.

Mgmt Studio and Sql 2000

I have a local server I just upgraded to 2005. Everything went well. But,
I
also have a remote sql 2000 server I still need to connect to. Can't seem
to get the tcp/ip connection to old server to work. Go back to old 2000 too
l
and it works fine, but I'd prefer to stay in one environment and migrate to
the new tool. Any ideas?What errors do you get?
-Sue
On Tue, 25 Jul 2006 06:47:02 -0700, Janet
<Janet@.discussions.microsoft.com> wrote:

>I have a local server I just upgraded to 2005. Everything went well. But,
I
>also have a remote sql 2000 server I still need to connect to. Can't seem
>to get the tcp/ip connection to old server to work. Go back to old 2000 to
ol
>and it works fine, but I'd prefer to stay in one environment and migrate to
>the new tool. Any ideas?|||As background - in SSMS, I checked the sql native client connectivity and
tcpip is enabled, alias is listed with correct ip and port. Error is:
===================================
Cannot connect to CASCE.
===================================
This version of Microsoft SQL Server Management Studio can only be used to
connect to SQL Server 2000 and SQL Server 2005 servers. (ConnectionDlg)
Program Location:
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.SqlServerType.Microsoft.SqlS
erver.Management.UI.ConnectionDlg.IConnectionValidator.CheckConnection(IDbCo
nnection conn)
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.CheckConnection()
at
Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectorThread()
"Sue Hoegemeier" wrote:

> What errors do you get?
> -Sue
> On Tue, 25 Jul 2006 06:47:02 -0700, Janet
> <Janet@.discussions.microsoft.com> wrote:
>
>|||That's the error you get when you try to connect to SQL
Server 7 or earlier with SSMS. Double check the version on
the other remote server when you connect with Query Analyzer
using select @.@.version.
-Sue
On Wed, 26 Jul 2006 10:28:02 -0700, Janet
<Janet@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>As background - in SSMS, I checked the sql native client connectivity and
>tcpip is enabled, alias is listed with correct ip and port. Error is:
>===================================
>Cannot connect to CASCE.
>===================================
>This version of Microsoft SQL Server Management Studio can only be used to
>connect to SQL Server 2000 and SQL Server 2005 servers. (ConnectionDlg)
>--
>Program Location:
> at
>Microsoft.SqlServer.Management.UI.ConnectionDlg.SqlServerType.Microsoft.Sql
Server.Management.UI.ConnectionDlg.IConnectionValidator.CheckConnection(IDbC
onnection conn)
> at
>Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.CheckConnection()
> at
>Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectorThread()
>
>"Sue Hoegemeier" wrote:
>|||Sue, holy toledo! You're right! My contact TOLD me they were running sql
2000, but they're running sql 7. I know that the new SSMS won't work with
that - read that in the documentation. Ah, well. Have to keep the old tool
s
around, I guess. Thanks so much for forcing me to double-check.
"Sue Hoegemeier" wrote:

> That's the error you get when you try to connect to SQL
> Server 7 or earlier with SSMS. Double check the version on
> the other remote server when you connect with Query Analyzer
> using select @.@.version.
> -Sue
> On Wed, 26 Jul 2006 10:28:02 -0700, Janet
> <Janet@.discussions.microsoft.com> wrote:
>
>

Message Queue Task 64 bit Cluster issue

Hello,

I'm using the Message Queuing task to create a local private queue message. Everything works great on a 32 bit machine. When I try this on a 64 bit Itanium Cluster I keep getting the message "Message queue service is not available" in my SSIS log. I've using this string as my path "ClusterName\private$\QueueName". Does anyone know of any issues with the Message Queue task on 64 bit or a cluster? The Message Queue service is up and running, it doesn't make sense.

Thanks,

Andy

I found out that you must install MSMS on each node of the cluster separately. Then set up your Message Queue using the Cluster Administrator. See this document for help.

http://download.microsoft.com/download/4/f/5/4f518f76-c1ce-431b-b79f-71caf9e27578/MSMQ3incluster.doc

Also, it's easier if you use the utility mmcv.exe to set up the cluster:

http://support.microsoft.com/?kbid=898701&SD=tech

Andy