connecting from dreamweaver(i'm a newbie pls. be gentle)

when i try to connect to sql server on my lan using dreamweaver with
javascript it connects(DSN) but when i try C# it says something about the
account (even with the sa account)it won't connect.
Omar,
please can you post up your dreamweaver and C# connectionstrings so we can
narrow down the problem.
TIA,
Paul Ibison

connecting from dreamweaver(i'm a newbie pls. be gentle)

when i try to connect to sql server on my lan using dreamweaver with
javascript it connects(DSN) but when i try C# it says something about the
account (even with the sa account)it won't connect.Omar,
please can you post up your dreamweaver and C# connectionstrings so we can
narrow down the problem.
TIA,
Paul Ibison

connecting from dreamweaver(i'm a newbie pls. be gentle)

when i try to connect to sql server on my lan using dreamweaver with
javascript it connects(DSN) but when i try C# it says something about the
account (even with the sa account)it won't connect.Omar,
please can you post up your dreamweaver and C# connectionstrings so we can
narrow down the problem.
TIA,
Paul Ibison

COnnect VB6 to Sql Server

Hi! can anybody pls. help me. How Can i connect my VB6 Application to Sql server? is it posible to connect my VB6 application directly to sql server without any requirements in the client? thanks in advance!!!Declarative stuff:

'DSNless stuff
Private mobjConnect 'The object containing the connection.. declare it at whatever level you need.
' or you could specifically type it so you can see all the properties and
' methods assciated with in VBPrivate mobjConnect As ADODB.Connection

'These are the variables you'll need for connection or if you're a savage
' you can hard code them in to the method.
Private DB_NAME As String
Private SERVER_NAME As String
Private DB_USER As String
Private DB_PASS As String

Then as a property in the db class or just create it as a standard function:

Friend Property Get dbConnect() As Variant
'Private function GetdbConnect as variant
'Attempt to get a connection object.
If mobjConnect = Empty Or Not IsObject(mobjConnect) Then
'---------
' Don't check if there was an error
'Let the error permeate back to the calling object to report the error.
'---------
Set mobjConnect = CreateObject("ADODB.Connection")
'or use Dim objTmpConnect As New ADODB.Connection
mobjConnect.ConnectionTimeout = 90

If mbolWinAuth Then
'Use trusted
mobjConnect.ConnectionString = "Provider=SQLOLEDB" + ";SERVER=" + SERVER_NAME + ";DATABASE=" + DB_NAME + _
";Trusted_Connection=Yes;APP=MyApp" & App.Major & "." & App.Major & "." & App.Revision
Else
'Use application or client defined
mobjConnect.ConnectionString = "Provider=SQLOLEDB" & ";SERVER=" & SERVER_NAME & ";DATABASE=" & _
DB_NAME & ";User ID=" & DB_USER & ";Password=" & DB_PASS
End If

' open connection
mobjConnect.Open
End If

Set dbConnect= mobjConnect 'Return ref to connection object
End Property

So you then have this dbConnect object (or a reference to it) that you can use to execute SQL/sp's:

Dim objRS
Set objRS = CreateObject("ADODB.Recordset")
Set objRS = dbConnect.Execute("Select blah from blah")

If Not objRS.EOF Then
? = objRS.GetRows
'or
? = objRS.Fields("column_Name").Value
objRS.movenext
'..etc

Thats basically it...

Cheers
Phil
--
Some days you're the bug, some days you're the windscreen.

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

|||

I'm getting the same problem and they only solution I've found is to add the user to the local admin group of hte remote server which is obviously not the desired approach.

Did you every manage to resolve this?

thanks

|||

TSZ wrote:

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

Is it timing out? It may be a firewall issue, where you would have to have port 135 open between your server and you. Also, you'll want to make sure that your user is in a trusted domain to SSIS.

Brian

|||

Per J wrote:

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

I know it's a bit OT, but I have the same scenario, but was not able to install SSIS on a failover cluster.
Can you point me to the "Guide" that you used for installation?

Thanks|||

Re: Clustering SSIS, there's a great whitepaper on TechNet or I have a video that can be seen here on how to cluster SSIS (about 10 mins in length): http://www.jumpstarttv.com/Media.aspx?vid=36

Brian

|||I ran into the exact same problem. I found, however, that its not really a SSIS issue, but actually a problem with a DLL, or a registry value from the client tools that was either erased or overwritten with a different version. With that in mind I removed the client tools and reinstalled them and that solved the problem

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

|||

I'm getting the same problem and they only solution I've found is to add the user to the local admin group of hte remote server which is obviously not the desired approach.

Did you every manage to resolve this?

thanks

|||

TSZ wrote:

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

Is it timing out? It may be a firewall issue, where you would have to have port 135 open between your server and you. Also, you'll want to make sure that your user is in a trusted domain to SSIS.

Brian

|||

Per J wrote:

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

I know it's a bit OT, but I have the same scenario, but was not able to install SSIS on a failover cluster.
Can you point me to the "Guide" that you used for installation?

Thanks|||

Re: Clustering SSIS, there's a great whitepaper on TechNet or I have a video that can be seen here on how to cluster SSIS (about 10 mins in length): http://www.jumpstarttv.com/Media.aspx?vid=36

Brian

|||I ran into the exact same problem. I found, however, that its not really a SSIS issue, but actually a problem with a DLL, or a registry value from the client tools that was either erased or overwritten with a different version. With that in mind I removed the client tools and reinstalled them and that solved the problem