Integrated Security: connect

Showing posts with label connect. Show all posts

Wednesday, March 28, 2012

Intermittent connection

Monday, March 26, 2012

Intermittent connection error (with workaround)

Hi all,
I have a strange error when I try to connect to SqlServer from Bde
Administrator (and also with my Delphi program which uses the BDE) on
some computers (in this post I'll call this problematic computer
SERVER_A).
When I try to open a BDE alias which connects to the local SqlServer I
get (on 90 % of attempts) a "General Sql Error" Bde error 13059.
Sometimes (let's say 10% of attempts) it connects ok.
This is quite strange (it's not a password error) and I can't explain
this behavior.
I can connect (using Bde Administrator) with no errors from the same
computer (SERVER_A) to a SqlServer installed in another Pc (let's call
this computer PC_B) and I can connect (using Bde Administrator) with
no error from PC_B computer to the SqlServer installed on the
SERVER_A.
I use SqlServer security, the BDE uses ntwdblib.dll to connect (using
tcp/ip).
I've stopped all firewalls, proxies etc... but nothing helps.
The only thing that fixes the problem is to add a new route from
SERVER_A that goes out to a proxy instead of going to 127.0.0.1
address (the loopback address).
In other term if I add a new route in the SERVER_A pc for SERVER_A IP
address that goes out to a proxy with a metric that is less than the
127.0.0.1 one then all the connections are ok.
This is very strange: it seems a TCP-IP problem.....
Do you have any ideas about this strange behavior?
Thank you,
Bye, Rocco.
I have the same problem, BDE and Windows 2003 SP2.
I solved it temporarily by using the named pipes protocol in SQL
Server Client Configuration.
But I would like to solve it by continuing to use TCP/IP.
Perhaps a security problem in windows 2003 SP2.
I checked also with portqry, and the server listens to port 1433.
Any other ideas ?
Jean-Christophe

Intermittent connection error (with workaround)

Hi all,
I have a strange error when I try to connect to SqlServer from Bde
Administrator (and also with my Delphi program which uses the BDE) on
some computers (in this post I'll call this problematic computer
SERVER_A).
When I try to open a BDE alias which connects to the local SqlServer I
get (on 90 % of attempts) a "General Sql Error" Bde error 13059.
Sometimes (let's say 10% of attempts) it connects ok.
This is quite strange (it's not a password error) and I can't explain
this behavior.
I can connect (using Bde Administrator) with no errors from the same
computer (SERVER_A) to a SqlServer installed in another Pc (let's call
this computer PC_B) and I can connect (using Bde Administrator) with
no error from PC_B computer to the SqlServer installed on the
SERVER_A.
I use SqlServer security, the BDE uses ntwdblib.dll to connect (using
tcp/ip).
I've stopped all firewalls, proxies etc... but nothing helps.
The only thing that fixes the problem is to add a new route from
SERVER_A that goes out to a proxy instead of going to 127.0.0.1
address (the loopback address).
In other term if I add a new route in the SERVER_A pc for SERVER_A IP
address that goes out to a proxy with a metric that is less than the
127.0.0.1 one then all the connections are ok.
This is very strange: it seems a TCP-IP problem.....
Do you have any ideas about this strange behavior?
Thank you,
Bye, Rocco.I have the same problem, BDE and Windows 2003 SP2.
I solved it temporarily by using the named pipes protocol in SQL
Server Client Configuration.
But I would like to solve it by continuing to use TCP/IP.
Perhaps a security problem in windows 2003 SP2.
I checked also with portqry, and the server listens to port 1433.
Any other ideas ?
Jean-Christophe

Intermittent connection

I am running SQL2000 on windows2003. I often connect to the database through the SQL Server Enterprise Manager on a client machine to administer it. The strange thing is sometimes I can connect to this database but other times cannot. THe error message is "SQL does not exist or not known to be running". I have checked the server status at the host terminal and it is running.
Anyone knows what's the problem for such intermitent connection? Network prob? SQL registration at the client side? ODBC setting?
Someone suggests that it may be because the host and the client are sitting on different domain in the network. Is this true?Hi,
Due the problem situation, can you run a ping comand to the SQL Server
machine (Ping <ipaddress of sql server>). If a request time out occurs
contact the "Network admin".
THis type of errors will come only if there is a slow network.
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> I am running SQL2000 on windows2003. I often connect to the database
through the SQL Server Enterprise Manager on a client machine to administer
it. The strange thing is sometimes I can connect to this database but other
times cannot. THe error message is "SQL does not exist or not known to be
running". I have checked the server status at the host terminal and it is
running.
> Anyone knows what's the problem for such intermitent connection? Network
prob? SQL registration at the client side? ODBC setting?
> Someone suggests that it may be because the host and the client are
sitting on different domain in the network. Is this true?|||Hi, Hari.
I can ping the sql server machine from the client terminal. But the client and host are in different domain. Is this the problem?
Thanks.
Tay
"Hari Prasad" wrote:
> Hi,
> Due the problem situation, can you run a ping comand to the SQL Server
> machine (Ping <ipaddress of sql server>). If a request time out occurs
> contact the "Network admin".
> THis type of errors will come only if there is a slow network.
>
> --
> Thanks
> Hari
> MCDBA
>
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> > I am running SQL2000 on windows2003. I often connect to the database
> through the SQL Server Enterprise Manager on a client machine to administer
> it. The strange thing is sometimes I can connect to this database but other
> times cannot. THe error message is "SQL does not exist or not known to be
> running". I have checked the server status at the host terminal and it is
> running.
> >
> > Anyone knows what's the problem for such intermitent connection? Network
> prob? SQL registration at the client side? ODBC setting?
> >
> > Someone suggests that it may be because the host and the client are
> sitting on different domain in the network. Is this true?
>
>|||HI,
If you have a Trust relation ship between both domains, then it should not
be a issue at all.
--
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> Hi, Hari.
> I can ping the sql server machine from the client terminal. But the client
and host are in different domain. Is this the problem?
> Thanks.
> Tay
> "Hari Prasad" wrote:
> > Hi,
> >
> > Due the problem situation, can you run a ping comand to the SQL Server
> > machine (Ping <ipaddress of sql server>). If a request time out occurs
> > contact the "Network admin".
> >
> > THis type of errors will come only if there is a slow network.
> >
> >
> > --
> > Thanks
> > Hari
> > MCDBA
> >
> >
> > "Tay" <Tay@.discussions.microsoft.com> wrote in message
> > news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> > > I am running SQL2000 on windows2003. I often connect to the database
> > through the SQL Server Enterprise Manager on a client machine to
administer
> > it. The strange thing is sometimes I can connect to this database but
other
> > times cannot. THe error message is "SQL does not exist or not known to
be
> > running". I have checked the server status at the host terminal and it
is
> > running.
> > >
> > > Anyone knows what's the problem for such intermitent connection?
Network
> > prob? SQL registration at the client side? ODBC setting?
> > >
> > > Someone suggests that it may be because the host and the client are
> > sitting on different domain in the network. Is this true?
> >
> >
> >|||hi
I just found out that both the host and the client did not join any domain but in the same workgroup. I can successfully search for the sqlserver after I login to a shared folder from my client terminal. It seems like the client need to establish the network path to the host before it can find the sqlserver.
Any way to avoid logging in yet still can locate the sqlserver?
Thanks.
"Hari Prasad" wrote:
> HI,
> If you have a Trust relation ship between both domains, then it should not
> be a issue at all.
> --
> Thanks
> Hari
> MCDBA
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> > Hi, Hari.
> >
> > I can ping the sql server machine from the client terminal. But the client
> and host are in different domain. Is this the problem?
> >
> > Thanks.
> > Tay
> >
> > "Hari Prasad" wrote:
> >
> > > Hi,
> > >
> > > Due the problem situation, can you run a ping comand to the SQL Server
> > > machine (Ping <ipaddress of sql server>). If a request time out occurs
> > > contact the "Network admin".
> > >
> > > THis type of errors will come only if there is a slow network.
> > >
> > >
> > > --
> > > Thanks
> > > Hari
> > > MCDBA
> > >
> > >
> > > "Tay" <Tay@.discussions.microsoft.com> wrote in message
> > > news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> > > > I am running SQL2000 on windows2003. I often connect to the database
> > > through the SQL Server Enterprise Manager on a client machine to
> administer
> > > it. The strange thing is sometimes I can connect to this database but
> other
> > > times cannot. THe error message is "SQL does not exist or not known to
> be
> > > running". I have checked the server status at the host terminal and it
> is
> > > running.
> > > >
> > > > Anyone knows what's the problem for such intermitent connection?
> Network
> > > prob? SQL registration at the client side? ODBC setting?
> > > >
> > > > Someone suggests that it may be because the host and the client are
> > > sitting on different domain in the network. Is this true?
> > >
> > >
> > >
>
>

Intermittent connection

Friday, March 23, 2012

interesting sql login issue

Hi all,
I have a SQL 2005 server running on SERVERA. I have the management studio
installed on my desktop (Windows XP Pro SP2) and connect to the sql server
using my regular domain login account (windows auth). This worked fine until
I had to change my domain user account's password as it had expired (we have
to change it every 90 days). Now, ever since then, I have been unable to
connect to the sql server in management studio. I get:-
Login Failed for user ''. Error: 18452
If I remote into the server and try to connect to sql it works fine (I am
member of local admin group on the server)
Any ideas'http://support.microsoft.com/kb/555332
Is it possible that you have your Windows auth password hardcoded somewhere?
When worse comes to worse, you may have to drop and re-create your login on
a
SQL Server.
"param@.community.nospam" wrote:

> Hi all,
> I have a SQL 2005 server running on SERVERA. I have the management studio
> installed on my desktop (Windows XP Pro SP2) and connect to the sql server
> using my regular domain login account (windows auth). This worked fine unt
il
> I had to change my domain user account's password as it had expired (we ha
ve
> to change it every 90 days). Now, ever since then, I have been unable to
> connect to the sql server in management studio. I get:-
> Login Failed for user ''. Error: 18452
> If I remote into the server and try to connect to sql it works fine (I am
> member of local admin group on the server)
> Any ideas'
>
>|||Can you connect from the command line with sqlcmd?
It may also be worth a try of deleting the registration and
reregistering the server.
-Sue
On Wed, 21 Mar 2007 14:50:49 -0500, <param@.community.nospam>
wrote:

>Hi all,
>I have a SQL 2005 server running on SERVERA. I have the management studio
>installed on my desktop (Windows XP Pro SP2) and connect to the sql server
>using my regular domain login account (windows auth). This worked fine unti
l
>I had to change my domain user account's password as it had expired (we hav
e
>to change it every 90 days). Now, ever since then, I have been unable to
>connect to the sql server in management studio. I get:-
>Login Failed for user ''. Error: 18452
>If I remote into the server and try to connect to sql it works fine (I am
>member of local admin group on the server)
>Any ideas'
>|||What do you mean by hardcoded? I just login to my workstation using my
windows domain login and password?
I have tried dropping and re-creating the login in SQL Server.
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:D1639F71-646C-4286-983F-87AF7C25360A@.microsoft.com...[vbcol=seagreen]
> http://support.microsoft.com/kb/555332
> Is it possible that you have your Windows auth password hardcoded
> somewhere?
> When worse comes to worse, you may have to drop and re-create your login
> on a
> SQL Server.
> "param@.community.nospam" wrote:
>|||If you notice the username is empty in the error message below. Could it be
a bug where management studio is not passing credentials to the server?
"Leon Shargorodsky" <LeonShargorodsky@.discussions.microsoft.com> wrote in
message news:D1639F71-646C-4286-983F-87AF7C25360A@.microsoft.com...[vbcol=seagreen]
> http://support.microsoft.com/kb/555332
> Is it possible that you have your Windows auth password hardcoded
> somewhere?
> When worse comes to worse, you may have to drop and re-create your login
> on a
> SQL Server.
> "param@.community.nospam" wrote:
>

Friday, March 9, 2012

Intellisense..when?

This is one of the top requested feature for next version (or SP) of SQL Server. (http://connect.microsoft.com/SQLServer/feedback ) There si some third parity tools but light years away from Visual Studio intellisense. I have only one simple question based on this answer

This is a very popular feature request. We will be working with teams across Microsoft to determine how best to do this. The intellisense offered by 3rd party ISVs is not perfect from what I've seen. This is something we're considering for a future release.

Thanks for the feedback!

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

When we can expect this feauture? (next version of SQL Server , SP 2 I hope so, or SP3

Thank you

In the mean time I'm using SQL Prompt which works pretty well.

http://geertverhoeven.blogspot.com/2007/01/intellisense-in-sql-server-management_18.html

Greetz,

Geert

Geert Verhoeven
Consultant @. Ausy Belgium

My Personal Blog

|||

It looks like we're going to earn a "". It is not going to come in Service Pack 2 () or any service pack for SQL Server 2005 ().

There are 3rd party tools available. I heard there were many issues in Red Gate's SQL Prompt 2 that were addressed with SQL Prompt 3. I have not used it myself.

Due to the inherent nature of the T-SQL language, it is far more difficult to make intellisense work as well as it does with C# or Visual Basic. There are two teams at Microsoft looking to address the problem. One is in the SQL Server team, the other is in the Visual Studio team. We do not have any official commitments to what is going to be in the next release of SQL Server ("Katmai"). Once we firmly establish what is in the next release and what isn't, we'll make sure to inform the SQL Server community.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

Friday, February 24, 2012

Integration Services in SSMS

We use Windows Authentication to connect to SQL Server, is there any special permissions required to connect to Integration Services in SSMS?

Whenever I try to browse the servers available with Integration Services (from Object Browser), none of the servers gets listed. If I directly give server name and try to connect to Integeration Services I get the following error. But I'm able to connect to the database engine.

TITLE: Connect to Server

Cannot connect to <servername>.

ADDITIONAL INFORMATION:

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "<servername>" failed:
Access is denied.

Thanks

Have you searched this forum or the Internet?

A well documented issue exists. Make sure you follow:

http://www.ssistalk.com/2007/04/13/ssis-access-is-denied-when-connection-to-remote-ssis-service/|||I think I went through those threads, forgive me for my ignorance, these steps of DCOM configuration needs to be done on the server where SSIS is running? since the final step says restart Integeration Services, I assume this needs to be done at the server.

Thanks
|||

Karunakaran wrote:
I think I went through those threads, forgive me for my ignorance, these steps of DCOM configuration needs to be done on the server where SSIS is running? since the final step says restart Integeration Services, I assume this needs to be done at the server.
Thanks

Correct. This is all on the server.

Sunday, February 19, 2012

integratedSecurity issues with Microsoft SQL Server 2005 JDBC Driver

I am using Microsoft SQL Server 2005 JDBC Driver to connect to SQL Server 2000 database, I am using the following connection URL

boolean iSecurity = true;

String connectionUrl = "jdbc:sqlserver://machine_name:1433;" + "databaseName=dbname;integratedSecurity=" + iSecurity;

I am getting the following error.

com.microsoft.sqlserver.jdbc.SQLServerException: This driver is not configured for integrated authentication.

How do I resolve it? I have the following set

VMOPTIONS = -Xrs -Djava.compiler=NONE -Djava.library.path=C:\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.1\enu\auth\x86\sqljdbc_auth.dll

Any help will be highly appreciated.

Regards

Arup

Hi Arup,

Try the following instead:

-Djava.library.path=C:\Microsoft SQL Server 2005 JDBC Driver\sqljdbc_1.1\enu\auth\x86\

The java.library.path JVM argument takes the location of a directory and not the .dll file itself.

Regards,

Jaaved Mohammed

Wednesday, March 28, 2012

Intermittent connection

Monday, March 26, 2012

Intermittent connection error (with workaround)

Intermittent connection error (with workaround)

Intermittent connection

Intermittent connection

Intermittent connection

Friday, March 23, 2012

interesting sql login issue

Friday, March 9, 2012

Intellisense..when?

Friday, February 24, 2012

Integration Services in SSMS

Sunday, February 19, 2012

integratedSecurity issues with Microsoft SQL Server 2005 JDBC Driver

Integrated Security

Blog Archive

About Me