Nonstop datasource connection

Does anyone out there have any ideas on the best way to connect in integration services to a nonstop sql database running on a tandem computer? We have some odbc drivers that have proven to be problematic and slow to use. What oledb products I can find apparently come with something that's around $36K per processor to buy. Thanks.

Try the data access forum

https://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=87&SiteID=1

-Jamie

Non-admin Citrix users cannot connect to SQL Server

We have an application that accesses a SQL 2000 server that is running on
several Citrix servers. Recently users started getting a message from the
application that there was a catastrophic failure when connecting to SQL
server. This was only happening if the user was not an administrator on the
Citrix server.
I tried connecting to SQL server from Enterprise Manager and Query Analyzer.
If I was logged on as an admin it worked, but if not, it did not work. In
Query Analyzer if I tried to log on to SQL server using a bad password, I got
back a message about bad user or password. When I put in the correct
password (or if using integrated security) the screen briefly acts like it is
connecting but then the entire isqlw program shuts down. Enterprise manager
shuts down when I try to connect to a server. As a non-admin user I am able
to connect using ISQL.exe.
We've checked on rights to the SQL files and everything looks OK. Is there
anything else to check?
Thanks
LehrSJ
Hello there,
I would like to suggest you applied the SQL 2000 SP4 first.
And please let me know the error log in the SQL Server.
This issue may related with some permission of folder. If you use the SQL
Authentication to connect the SQL server, did this issue occur?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Non Windows App connecting to SQL Server using Windows Auth

How can a non Windows App , say an app that runs on Linux connect to SQL
Server using Windows Auth ?
Has anyone done that ? How does Linux integrate with Windows ? Are there 3rd
party tools ?
We know SQL Auth would work but we want to use Windows Auth only.
Please let me know
ThanksTypically a Linux box uses something like FreeTDS to connect to a SQL
Server machine. FreeTDS supports both forms of authentication:
http://www.freetds.org/faq.html

Non Windows App connecting to SQL Server using Windows Auth

How can a non Windows App , say an app that runs on Linux connect to SQL
Server using Windows Auth ?
Has anyone done that ? How does Linux integrate with Windows ? Are there 3rd
party tools ?
We know SQL Auth would work but we want to use Windows Auth only.
Please let me know
ThanksTypically a Linux box uses something like FreeTDS to connect to a SQL
Server machine. FreeTDS supports both forms of authentication:
http://www.freetds.org/faq.html

non default port - client cannot connect

I have changed the default port away from 1433 on sql server 2005. Now I
cannot connect from pc. What do I need to change on the client pc?
Thanks
Connect by adding a comma and port number after machine name, like:
machinename,1456
Or use cliconfg.exe to add an alias and specify the port number in that alias.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"guest5" <guest5@.discussions.microsoft.com> wrote in message
news:0A38D0A1-E40F-4A97-93D6-5C288E867802@.microsoft.com...
>I have changed the default port away from 1433 on sql server 2005. Now I
> cannot connect from pc. What do I need to change on the client pc?
> Thanks

non default port - client cannot connect

I have changed the default port away from 1433 on sql server 2005. Now I
cannot connect from pc. What do I need to change on the client pc?
ThanksConnect by adding a comma and port number after machine name, like:
machinename,1456
Or use cliconfg.exe to add an alias and specify the port number in that alia
s.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"guest5" <guest5@.discussions.microsoft.com> wrote in message
news:0A38D0A1-E40F-4A97-93D6-5C288E867802@.microsoft.com...
>I have changed the default port away from 1433 on sql server 2005. Now I
> cannot connect from pc. What do I need to change on the client pc?
> Thanks

non default port - client cannot connect

I have changed the default port away from 1433 on sql server 2005. Now I
cannot connect from pc. What do I need to change on the client pc?
ThanksConnect by adding a comma and port number after machine name, like:
machinename,1456
Or use cliconfg.exe to add an alias and specify the port number in that alias.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"guest5" <guest5@.discussions.microsoft.com> wrote in message
news:0A38D0A1-E40F-4A97-93D6-5C288E867802@.microsoft.com...
>I have changed the default port away from 1433 on sql server 2005. Now I
> cannot connect from pc. What do I need to change on the client pc?
> Thanks

Non default port

I am using SQL 2005 and have multiple instances installed on multiple
servers. None are on the default port. When I connect to box 01
without specifying the port in the connection string, it connects.
But on box 02, it will only connect to the instance if I specify the
port name. Is this because it will only connect to the default
instance without specifying a port? or is there something else I need
to have setup on box 02 to make this work?
thanks in advance
> Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
Check to ensure the SQL Browser service is running as Tibor suggested.
Another possible cause is that UDP port 1434 is blocked.
When you connect to the default instance, TCP port 1433 is used by default.
When you connect to a named instance without a specifying a port, the client
requests a list of the named instances and corresponding ports via UDP port
1434 (this is the SQL Browser service). The client then determines the
named instance port.
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Victag" <miketaggart@.gmail.com> wrote in message
news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>I am using SQL 2005 and have multiple instances installed on multiple
> servers. None are on the default port. When I connect to box 01
> without specifying the port in the connection string, it connects.
> But on box 02, it will only connect to the instance if I specify the
> port name. Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
> thanks in advance
|||On Mar 13, 4:26Xam, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> Check to ensure the SQL Browser service is running as Tibor suggested.
> Another possible cause is that UDP port 1434 is blocked.
> When you connect to the default instance, TCP port 1433 is used by default..
> When you connect to a named instance without a specifying a port, the client
> requests a list of the named instances and corresponding ports via UDP port
> 1434 (this is the SQL Browser service). XThe client then determines the
> named instance port.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>
>
> - Show quoted text -
Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?
|||Hi,
You can access named instances (if you know port number) in this way:
tcp:server_name,port_number
Regards,
anxcomp
|||On Mar 13, 11:12Xam, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> <<Thanks folks! XI have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. XI have also confirmed that no ports are blocked at all. XAny
> other suggestions?>>
> We can only explain how things work:
> When you connect to a default instance (no backslash and instance name), the data access components
> will connect to port 1433. The SQL Server service by default listens to 1433 for a default instance
> (well-known port).
> The port number for a named instance is determined dynamically the first time you start the
> instance. SQL Server asks Windows for an available port, uses it and stores the port number in the
> registry (as you can see using SQL Server Configuration Manager). It will try to use the same port
> number on subsequent start-ups.
> If you from the client app only specify machine name/IP backslash instancename, then you need some
> component to translate this instance name to a port number. That componentis SQL Server Browser
> service. The client data access components connects to the SSB service using port 1434 UDP and
> passes the instance name, and the SSB service returns the port number. Youcan also from the client
> app specify machine/IP comma portnumber, so there would now be no use for the SSB service. SQL
> Server 2000 didn't come with an SSB service so for 2000 the database engine did this job (listening
> on port 1434).
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:bee0415f-6523-45e7-9d46-ad9a01846809@.d62g2000hsf.googlegroups.com...
> On Mar 13, 4:26 am, "Dan Guzman" <guzma...@.nospam-
>
>
> online.sbcglobal.net> wrote:
>
>
>
>
>
> Thanks folks! XI have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. XI have also confirmed that no ports are blocked at all. XAny
> other suggestions... Hide quoted text -
> - Show quoted text -
Thanks again. I have made progress and found that the boxes that are
not working have many client aliases created on them, some of which
appear to be invalid. When I deleted the aliases that did not exist
on the server that is working, it fixed them. So now that I know how
to fix it, I am curious to know how these bad aliases got created
since we did not create them manually.
|||"Victag" wrote:

>I am curious to know how these bad aliases got created
> since we did not create them manually.
Did you install Visio? For example Visio installation process create for me
some alias. I have to delete it manually.
Regards,
anxcomp

Non default port

I am using SQL 2005 and have multiple instances installed on multiple
servers. None are on the default port. When I connect to box 01
without specifying the port in the connection string, it connects.
But on box 02, it will only connect to the instance if I specify the
port name. Is this because it will only connect to the default
instance without specifying a port? or is there something else I need
to have setup on box 02 to make this work?
thanks in advance :)See if the SQL Server Browser service is started on box 02.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Victag" <miketaggart@.gmail.com> wrote in message
news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>I am using SQL 2005 and have multiple instances installed on multiple
> servers. None are on the default port. When I connect to box 01
> without specifying the port in the connection string, it connects.
> But on box 02, it will only connect to the instance if I specify the
> port name. Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
> thanks in advance :)|||> Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
Check to ensure the SQL Browser service is running as Tibor suggested.
Another possible cause is that UDP port 1434 is blocked.
When you connect to the default instance, TCP port 1433 is used by default.
When you connect to a named instance without a specifying a port, the client
requests a list of the named instances and corresponding ports via UDP port
1434 (this is the SQL Browser service). The client then determines the
named instance port.
--
Hope this helps.
Dan Guzman
SQL Server MVP
http://weblogs.sqlteam.com/dang/
"Victag" <miketaggart@.gmail.com> wrote in message
news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>I am using SQL 2005 and have multiple instances installed on multiple
> servers. None are on the default port. When I connect to box 01
> without specifying the port in the connection string, it connects.
> But on box 02, it will only connect to the instance if I specify the
> port name. Is this because it will only connect to the default
> instance without specifying a port? or is there something else I need
> to have setup on box 02 to make this work?
> thanks in advance :)|||On Mar 13, 4:26=A0am, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> > Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> Check to ensure the SQL Browser service is running as Tibor suggested.
> Another possible cause is that UDP port 1434 is blocked.
> When you connect to the default instance, TCP port 1433 is used by default=.
> When you connect to a named instance without a specifying a port, the clie=nt
> requests a list of the named instances and corresponding ports via UDP por=t
> 1434 (this is the SQL Browser service). =A0The client then determines the
> named instance port.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>
> >I am using SQL 2005 and have multiple instances installed on multiple
> > servers. =A0None are on the default port. =A0When I connect to box 01
> > without specifying the port in the connection string, it connects.
> > But on box 02, it will only connect to the instance if I specify the
> > port name. =A0Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> > thanks in advance :)- Hide quoted text -
> - Show quoted text -
Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?|||<<Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?>>
We can only explain how things work:
When you connect to a default instance (no backslash and instance name), the data access components
will connect to port 1433. The SQL Server service by default listens to 1433 for a default instance
(well-known port).
The port number for a named instance is determined dynamically the first time you start the
instance. SQL Server asks Windows for an available port, uses it and stores the port number in the
registry (as you can see using SQL Server Configuration Manager). It will try to use the same port
number on subsequent start-ups.
If you from the client app only specify machine name/IP backslash instancename, then you need some
component to translate this instance name to a port number. That component is SQL Server Browser
service. The client data access components connects to the SSB service using port 1434 UDP and
passes the instance name, and the SSB service returns the port number. You can also from the client
app specify machine/IP comma portnumber, so there would now be no use for the SSB service. SQL
Server 2000 didn't come with an SSB service so for 2000 the database engine did this job (listening
on port 1434).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Victag" <miketaggart@.gmail.com> wrote in message
news:bee0415f-6523-45e7-9d46-ad9a01846809@.d62g2000hsf.googlegroups.com...
On Mar 13, 4:26 am, "Dan Guzman" <guzma...@.nospam-
online.sbcglobal.net> wrote:
> > Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> Check to ensure the SQL Browser service is running as Tibor suggested.
> Another possible cause is that UDP port 1434 is blocked.
> When you connect to the default instance, TCP port 1433 is used by default.
> When you connect to a named instance without a specifying a port, the client
> requests a list of the named instances and corresponding ports via UDP port
> 1434 (this is the SQL Browser service). The client then determines the
> named instance port.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...
>
> >I am using SQL 2005 and have multiple instances installed on multiple
> > servers. None are on the default port. When I connect to box 01
> > without specifying the port in the connection string, it connects.
> > But on box 02, it will only connect to the instance if I specify the
> > port name. Is this because it will only connect to the default
> > instance without specifying a port? or is there something else I need
> > to have setup on box 02 to make this work?
> > thanks in advance :)- Hide quoted text -
> - Show quoted text -
Thanks folks! I have checked and the Browser service is disabled on
both boxes (event he working one), so I could try turning it on, but I
would rather explain/understand what the difference is between these
boxes. I have also confirmed that no ports are blocked at all. Any
other suggestions?|||Hi,
You can access named instances (if you know port number) in this way:
tcp:server_name,port_number
--
Regards,
anxcomp|||On Mar 13, 11:12=A0am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> <<Thanks folks! =A0I have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. =A0I have also confirmed that no ports are blocked at all. =A0Any
> other suggestions?>>
> We can only explain how things work:
> When you connect to a default instance (no backslash and instance name), t=he data access components
> will connect to port 1433. The SQL Server service by default listens to 14=33 for a default instance
> (well-known port).
> The port number for a named instance is determined dynamically the first t=ime you start the
> instance. SQL Server asks Windows for an available port, uses it and store=s the port number in the
> registry (as you can see using SQL Server Configuration Manager). It will =try to use the same port
> number on subsequent start-ups.
> If you from the client app only specify machine name/IP backslash instance=name, then you need some
> component to translate this instance name to a port number. That component= is SQL Server Browser
> service. The client data access components connects to the SSB service usi=ng port 1434 UDP and
> passes the instance name, and the SSB service returns the port number. You= can also from the client
> app specify machine/IP comma portnumber, so there would now be no use for =the SSB service. SQL
> Server 2000 didn't come with an SSB service so for 2000 the database engin=e did this job (listening
> on port 1434).
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asph=
ttp://sqlblog.com/blogs/tibor_karaszi
> "Victag" <miketagg...@.gmail.com> wrote in message
> news:bee0415f-6523-45e7-9d46-ad9a01846809@.d62g2000hsf.googlegroups.com...
> On Mar 13, 4:26 am, "Dan Guzman" <guzma...@.nospam-
>
>
> online.sbcglobal.net> wrote:
> > > Is this because it will only connect to the default
> > > instance without specifying a port? or is there something else I need
> > > to have setup on box 02 to make this work?
> > Check to ensure the SQL Browser service is running as Tibor suggested.
> > Another possible cause is that UDP port 1434 is blocked.
> > When you connect to the default instance, TCP port 1433 is used by defau=lt.
> > When you connect to a named instance without a specifying a port, the cl=ient
> > requests a list of the named instances and corresponding ports via UDP p=ort
> > 1434 (this is the SQL Browser service). The client then determines the
> > named instance port.
> > --
> > Hope this helps.
> > Dan Guzman
> > SQL Server MVPhttp://weblogs.sqlteam.com/dang/
> > "Victag" <miketagg...@.gmail.com> wrote in message
> >news:0ef672ad-08dd-49da-8ff6-1abfcf4982bb@.s12g2000prg.googlegroups.com...=
> > >I am using SQL 2005 and have multiple instances installed on multiple
> > > servers. None are on the default port. When I connect to box 01
> > > without specifying the port in the connection string, it connects.
> > > But on box 02, it will only connect to the instance if I specify the
> > > port name. Is this because it will only connect to the default
> > > instance without specifying a port? or is there something else I need
> > > to have setup on box 02 to make this work?
> > > thanks in advance :)- Hide quoted text -
> > - Show quoted text -
> Thanks folks! =A0I have checked and the Browser service is disabled on
> both boxes (event he working one), so I could try turning it on, but I
> would rather explain/understand what the difference is between these
> boxes. =A0I have also confirmed that no ports are blocked at all. =A0Any
> other suggestions... Hide quoted text -
> - Show quoted text -
Thanks again. I have made progress and found that the boxes that are
not working have many client aliases created on them, some of which
appear to be invalid. When I deleted the aliases that did not exist
on the server that is working, it fixed them. So now that I know how
to fix it, I am curious to know how these bad aliases got created
since we did not create them manually.|||"Victag" wrote:
>I am curious to know how these bad aliases got created
> since we did not create them manually.
Did you install Visio? For example Visio installation process create for me
some alias. I have to delete it manually.
Regards,
anxcomp

no such interface supported virus

I'm running an access 2000 front end with a slq server 2000 back end on a lo
cal network. All of the sudden one workstation couldn't connect to the serv
er. So after trying several things I think I've came to the correct conclus
ion. I believe that the ma
chine was infected by a virus that was missed by two different scanners. I
think its a hijack virus that takes control of sql when its trying to connec
t to the server using the server name. Its very odd and isn't detected by s
canners. A temp. fix is to
just use the ip of the server to connect and then it works. Also if I try a
nd ping the server by name it doesn't get a return however if I use the elon
gated full name of the server with domain its fine. Any ideas suggestions c
lues?Is the server running a Personal Firewall?
Are you connecting via TCP or Named Pipes?
What are you using for Name Resolution of the server?
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.