Access 2000 application on client can log-in to SQL server using one of the SQL server logins.
Problem is that from certain clients you can log in using ANY id.
From other clients, the login attempt produces the SQL Server login box.
Any ideas why this might be ?
Client is Win2000.
All help would be appreciated!Have u tried connecting to sql from same box with diff network usernames ?
U prob running integrated security ?|||The login box should not come up at all ! That's the problem.
For the clients where it is the correct behaviour, you do not see the login box at all after starting the application.
However, when you start the application from some clients on the network, then the login box appears ...
Thanks.|||Sorry I'm not familiar with Access 2000 very much.
I was wondering wheter some clients are getting into sql via integrated security - taking the clients network login credentials by default - & if that fails the sql security login then the Login Box appears
Have u tried connecting to sql from same box with diff network usernames
Is it Box or user specific SQL Security Access problem.|||Try WINDOWS AUTHENTICATION on SQLSErver side.|||Originally posted by Satya
Try WINDOWS AUTHENTICATION on SQLSErver side.
Hi Satya -
I do not understand - could you please explain what you mean in more detail?
Many thanks.
Showing posts with label login. Show all posts
Showing posts with label login. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
Intermittent Logon
Most of the time all the users can login to SQL.
On occation one or two will fail.
If I then try their login using Query Analyser it works...and then they are
able to log in.
What's going on?!?!?!
Kyle!
"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:OJpLo7X0EHA.2016@.TK2MSFTNGP15.phx.gbl...
> Most of the time all the users can login to SQL.
> On occation one or two will fail.
> If I then try their login using Query Analyser it works...and then they
are
> able to log in.
> What's going on?!?!?!
Have you enabled failed login auditing on both the server and SQL Server?
Steve
|||When it fails what error do they see?
Rand
This posting is provided "as is" with no warranties and confers no rights.
On occation one or two will fail.
If I then try their login using Query Analyser it works...and then they are
able to log in.
What's going on?!?!?!
Kyle!
"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:OJpLo7X0EHA.2016@.TK2MSFTNGP15.phx.gbl...
> Most of the time all the users can login to SQL.
> On occation one or two will fail.
> If I then try their login using Query Analyser it works...and then they
are
> able to log in.
> What's going on?!?!?!
Have you enabled failed login auditing on both the server and SQL Server?
Steve
|||When it fails what error do they see?
Rand
This posting is provided "as is" with no warranties and confers no rights.
Intermittent Logon
Most of the time all the users can login to SQL.
On occation one or two will fail.
If I then try their login using Query Analyser it works...and then they are
able to log in.
What's going on?!?!?!
Kyle!"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:OJpLo7X0EHA.2016@.TK2MSFTNGP15.phx.gbl...
> Most of the time all the users can login to SQL.
> On occation one or two will fail.
> If I then try their login using Query Analyser it works...and then they
are
> able to log in.
> What's going on?!?!?!
Have you enabled failed login auditing on both the server and SQL Server?
Steve|||When it fails what error do they see?
Rand
This posting is provided "as is" with no warranties and confers no rights.
On occation one or two will fail.
If I then try their login using Query Analyser it works...and then they are
able to log in.
What's going on?!?!?!
Kyle!"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:OJpLo7X0EHA.2016@.TK2MSFTNGP15.phx.gbl...
> Most of the time all the users can login to SQL.
> On occation one or two will fail.
> If I then try their login using Query Analyser it works...and then they
are
> able to log in.
> What's going on?!?!?!
Have you enabled failed login auditing on both the server and SQL Server?
Steve|||When it fails what error do they see?
Rand
This posting is provided "as is" with no warranties and confers no rights.
Intermittent Logon
Most of the time all the users can login to SQL.
On occation one or two will fail.
If I then try their login using Query Analyser it works...and then they are
able to log in.
What's going on?!?!?!
Kyle!"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:OJpLo7X0EHA.2016@.TK2MSFTNGP15.phx.gbl...
> Most of the time all the users can login to SQL.
> On occation one or two will fail.
> If I then try their login using Query Analyser it works...and then they
are
> able to log in.
> What's going on?!?!?!
Have you enabled failed login auditing on both the server and SQL Server?
Steve|||When it fails what error do they see?
Rand
This posting is provided "as is" with no warranties and confers no rights.
On occation one or two will fail.
If I then try their login using Query Analyser it works...and then they are
able to log in.
What's going on?!?!?!
Kyle!"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:OJpLo7X0EHA.2016@.TK2MSFTNGP15.phx.gbl...
> Most of the time all the users can login to SQL.
> On occation one or two will fail.
> If I then try their login using Query Analyser it works...and then they
are
> able to log in.
> What's going on?!?!?!
Have you enabled failed login auditing on both the server and SQL Server?
Steve|||When it fails what error do they see?
Rand
This posting is provided "as is" with no warranties and confers no rights.
Intermittent Login failure at boot
I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
Thanks
Go through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:
>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thanks
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
Thanks
Go through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:
>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thanks
Intermittent Login failure at boot
I have a Windows Service middleware application that depends on SQL
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
ThanksGo through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:
>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thankssql
Server. We are migrating from an existing Windows 2000 server/
SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
boot time and more often than not, the middleware application fails to
start and SQLServer reports a Failure Audit saying the Login failed
for the user 'SomeUser'. This is the account the middleware uses, it
is a SQLServer account and not a Windows account.
But once the machine is booted and I login to the server, I can start
the middleware application successfully using the Services control
panel. I'm assuming that despite the dependency of my middleware
service on the SQLServer service, SQLServer is not sufficiently
initialised to accept client connections at the point that my
middleware service tries to connect. I can't say whether this is
peculiar to SQLServer Express because to see if it also occurs with
SQLServer Standard 2005 I would need to reinstall and configure the
operating system and application software.
If there is no workaround for this, the only solution I can think of
(without going to Windows 2003 Standard and SQLServer 2005 Standard)
is to write another Windows Service to check whether or not my
middleware started successfully and to start it if it failed to start.
Any help with this problem would be much appreciated.
ThanksGo through the SQL Server log to get a better idea if it's
just a timing issue...which I would guess it probably is.
You should see the login failure with a date time as well as
when the database the middleware uses is available, when SQL
is ready to accept client connections. You would also want
to check the state of the login failure to see the cause of
the failure.
But...going through the log should give you more information
to understand what's going on in your situation.
-Sue
On Tue, 31 Jul 2007 17:46:13 -0700, Dave
<pigwin32@.gmail.com> wrote:
>I have a Windows Service middleware application that depends on SQL
>Server. We are migrating from an existing Windows 2000 server/
>SQLServer 2000 to Windows 2003 Web Edition and SQLServer Express. At
>boot time and more often than not, the middleware application fails to
>start and SQLServer reports a Failure Audit saying the Login failed
>for the user 'SomeUser'. This is the account the middleware uses, it
>is a SQLServer account and not a Windows account.
>But once the machine is booted and I login to the server, I can start
>the middleware application successfully using the Services control
>panel. I'm assuming that despite the dependency of my middleware
>service on the SQLServer service, SQLServer is not sufficiently
>initialised to accept client connections at the point that my
>middleware service tries to connect. I can't say whether this is
>peculiar to SQLServer Express because to see if it also occurs with
>SQLServer Standard 2005 I would need to reinstall and configure the
>operating system and application software.
>If there is no workaround for this, the only solution I can think of
>(without going to Windows 2003 Standard and SQLServer 2005 Standard)
>is to write another Windows Service to check whether or not my
>middleware started successfully and to start it if it failed to start.
>Any help with this problem would be much appreciated.
>Thankssql
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:
>
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:
>
Wednesday, March 21, 2012
interesting case for "SQL Server does not exist or access denied." error
My connection string is :
server=localhost;Database=INFOSEC;Integrated Security=true
It works for the login page, but it does not work for the registration page, and give the "SQL Server does not exist or access denied." error.
Any IDEA?
You shouls check your connection string properly and make sure you are calling proper database for registration form.Otherwise can you give the code here.So i can findout the error.
Friday, February 24, 2012
Integration Services Login
How do I add myself into the Integration Services? so I can use SQL Server
Management Studio to log in Integration Services
First I tried loggin into the SQL Server 2005 itself using 'sa', add my NT
login as a login ie 'SomeGroup\SomeloginName', open the properties for the N
T
Login name & assign all roles including sysadmin to the name.
Then, go back to SQL Server Management Studio to connect to Integration
Services, it still say access deny
Thanks
--
MVP888Hi,
From your descriptions, I understood you are not able to connect SSIS with
the account even you have assigned SA privilege. If I have misunderstood
your concern, please feel free to point it out.
First of all, please use SQL Server Configuration Manager to make sure you
have started SQL Server Intergration Services.
Secondly, have you tried use both Windows Authentication and SQL
Authentication to login the SSIS?
Thirdly, is it possible for you to show us some screen shot?
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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.|||Thanks Michael
1. SQL Server Integration Services started because I can login using the NT
account that was used to install the SQL Server but not other NT accounts.
2. I can not switch over to use the SQL Authentication option when I log
into Integration Services because it is grayed out. However, I do have the
SQL Authentication option when I log into the SQL Server Database itself.
(Why is that).
3.I have problem pasting the screen, but here is what on the error screen
when I try to log into SSIS
Cannot connect to ldqcedcmcache1.--> my machine name
Additional Information:
-->Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
--> Connect to SSIS Service on machine “ldqcedcmcache1” failed:
Access is denied.|||Hi,
[vbcol=seagreen]
the[vbcol=seagreen]
itself.[vbcol=seagreen]
Only Microsoft Windows Authentication is available for SSIS. Windows
Authentication mode allows a user to connect through a Windows user account.
For more detailed information, check the BOL topic below
Connect to Server (Integration Services)
http://msdn2.microsoft.com/en-us/library/ms183366(en-US,SQL.90).aspx
[vbcol=seagreen]
Since the SSIS will only allow Windows Authentication, please make sure
your Windows Account has sufficient privilege to SSIS.
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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,
I've just fixed this problem myself. This probably isn't the proper fix,
but I found that adding the user to the local machine's (ie the SQL Server's
local group) administrators group gave me the rights to log on.
This is only a quick fix, but the issue must be that whatever user you want
to access integrations services must need certain levels of access to the
OS, most likely the ability to start and stop services.
Its a starting point anyway!
Regards
Brett
"MVP888" wrote:
[vbcol=seagreen]
> Thanks Michael
> 1. SQL Server Integration Services started because I can login using the N
T
> account that was used to install the SQL Server but not other NT accounts.
> 2. I can not switch over to use the SQL Authentication option when I log
> into Integration Services because it is grayed out. However, I do have th
e
> SQL Authentication option when I log into the SQL Server Database itself.
> (Why is that).
> 3.I have problem pasting the screen, but here is what on the error screen
> when I try to log into SSIS
> Cannot connect to ldqcedcmcache1.--> my machine name
> Additional Information:
> -->Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
> --> Connect to SSIS Service on machine “ldqcedcmcache1” failed:
> Access is denied.
> .
> --> Connect to SSIS Service on machine “ldqcedcmcache1” fail
ed:
> Access is denied.
> .
> Thanks Again.
> --
> MVP888
>
> "Michael Cheng [MSFT]" wrote:
>|||I was pleased to find this subject posted on the technet board, but somewhat
dissappointed in the resolution. I too am getting the exact error as posted
by the originator. I just CANNOT get connected to an installation of
Integration Services other than the one running on my machine (Developer
Edition).
Where do I specify that a Domain Group has access to the Integration
Services? I can go to the Database Engine and give the group rights on the
server, but that only applies to the Database Engine, not the Integration
Services.
Do I need to do like Brett Hargreaves pointed out and add the Domain Group
to the local server's administrator group. I like to think there is a better
solution that that.
**********************************[vbcol
=seagreen]
> Since the SSIS will only allow Windows Authentication, please make sure
> your Windows Account has sufficient privilege to SSIS.[/vbcol]
***********************************
Where do I go to make that happen?
Thank you in advance.
ToddC
"Michael Cheng [MSFT]" wrote:
> Hi,
>
> the
> itself.
> Only Microsoft Windows Authentication is available for SSIS. Windows
> Authentication mode allows a user to connect through a Windows user accoun
t.
> For more detailed information, check the BOL topic below
> Connect to Server (Integration Services)
> http://msdn2.microsoft.com/en-us/library/ms183366(en-US,SQL.90).aspx
>
> Since the SSIS will only allow Windows Authentication, please make sure
> your Windows Account has sufficient privilege to SSIS.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner 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
.
>|||I've installed SQL2005 on my desktop, and have no problem connecting to "dat
abase engine" for databases, jobs etc, but when I try to connect to Integrat
ion Services from my desktop, I get the error:
Connect to SSIS Service on machine "SQL_TestServer" failed:
Access is denied.
I'm a member of sysadmin within SQL, as well as an administrator on the serv
er. I don't have any problem when I log on to the server directly via Remot
e Desktop and open IS. Am I missing something obvious ?
Management Studio to log in Integration Services
First I tried loggin into the SQL Server 2005 itself using 'sa', add my NT
login as a login ie 'SomeGroup\SomeloginName', open the properties for the N
T
Login name & assign all roles including sysadmin to the name.
Then, go back to SQL Server Management Studio to connect to Integration
Services, it still say access deny
Thanks
--
MVP888Hi,
From your descriptions, I understood you are not able to connect SSIS with
the account even you have assigned SA privilege. If I have misunderstood
your concern, please feel free to point it out.
First of all, please use SQL Server Configuration Manager to make sure you
have started SQL Server Intergration Services.
Secondly, have you tried use both Windows Authentication and SQL
Authentication to login the SSIS?
Thirdly, is it possible for you to show us some screen shot?
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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.|||Thanks Michael
1. SQL Server Integration Services started because I can login using the NT
account that was used to install the SQL Server but not other NT accounts.
2. I can not switch over to use the SQL Authentication option when I log
into Integration Services because it is grayed out. However, I do have the
SQL Authentication option when I log into the SQL Server Database itself.
(Why is that).
3.I have problem pasting the screen, but here is what on the error screen
when I try to log into SSIS
Cannot connect to ldqcedcmcache1.--> my machine name
Additional Information:
-->Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
--> Connect to SSIS Service on machine “ldqcedcmcache1” failed:
Access is denied.|||Hi,
[vbcol=seagreen]
the[vbcol=seagreen]
itself.[vbcol=seagreen]
Only Microsoft Windows Authentication is available for SSIS. Windows
Authentication mode allows a user to connect through a Windows user account.
For more detailed information, check the BOL topic below
Connect to Server (Integration Services)
http://msdn2.microsoft.com/en-us/library/ms183366(en-US,SQL.90).aspx
[vbcol=seagreen]
Since the SSIS will only allow Windows Authentication, please make sure
your Windows Account has sufficient privilege to SSIS.
Sincerely yours,
Michael Cheng
Microsoft Online Partner 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,
I've just fixed this problem myself. This probably isn't the proper fix,
but I found that adding the user to the local machine's (ie the SQL Server's
local group) administrators group gave me the rights to log on.
This is only a quick fix, but the issue must be that whatever user you want
to access integrations services must need certain levels of access to the
OS, most likely the ability to start and stop services.
Its a starting point anyway!
Regards
Brett
"MVP888" wrote:
[vbcol=seagreen]
> Thanks Michael
> 1. SQL Server Integration Services started because I can login using the N
T
> account that was used to install the SQL Server but not other NT accounts.
> 2. I can not switch over to use the SQL Authentication option when I log
> into Integration Services because it is grayed out. However, I do have th
e
> SQL Authentication option when I log into the SQL Server Database itself.
> (Why is that).
> 3.I have problem pasting the screen, but here is what on the error screen
> when I try to log into SSIS
> Cannot connect to ldqcedcmcache1.--> my machine name
> Additional Information:
> -->Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
> --> Connect to SSIS Service on machine “ldqcedcmcache1” failed:
> Access is denied.
> .
> --> Connect to SSIS Service on machine “ldqcedcmcache1” fail
ed:
> Access is denied.
> .
> Thanks Again.
> --
> MVP888
>
> "Michael Cheng [MSFT]" wrote:
>|||I was pleased to find this subject posted on the technet board, but somewhat
dissappointed in the resolution. I too am getting the exact error as posted
by the originator. I just CANNOT get connected to an installation of
Integration Services other than the one running on my machine (Developer
Edition).
Where do I specify that a Domain Group has access to the Integration
Services? I can go to the Database Engine and give the group rights on the
server, but that only applies to the Database Engine, not the Integration
Services.
Do I need to do like Brett Hargreaves pointed out and add the Domain Group
to the local server's administrator group. I like to think there is a better
solution that that.
**********************************[vbcol
=seagreen]
> Since the SSIS will only allow Windows Authentication, please make sure
> your Windows Account has sufficient privilege to SSIS.[/vbcol]
***********************************
Where do I go to make that happen?
Thank you in advance.
ToddC
"Michael Cheng [MSFT]" wrote:
> Hi,
>
> the
> itself.
> Only Microsoft Windows Authentication is available for SSIS. Windows
> Authentication mode allows a user to connect through a Windows user accoun
t.
> For more detailed information, check the BOL topic below
> Connect to Server (Integration Services)
> http://msdn2.microsoft.com/en-us/library/ms183366(en-US,SQL.90).aspx
>
> Since the SSIS will only allow Windows Authentication, please make sure
> your Windows Account has sufficient privilege to SSIS.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner 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
.
>|||I've installed SQL2005 on my desktop, and have no problem connecting to "dat
abase engine" for databases, jobs etc, but when I try to connect to Integrat
ion Services from my desktop, I get the error:
Connect to SSIS Service on machine "SQL_TestServer" failed:
Access is denied.
I'm a member of sysadmin within SQL, as well as an administrator on the serv
er. I don't have any problem when I log on to the server directly via Remot
e Desktop and open IS. Am I missing something obvious ?
Subscribe to:
Posts (Atom)