Showing posts with label receive. Show all posts
Showing posts with label receive. Show all posts

Friday, March 9, 2012

Non domain user receive access denied error

I am trying to run a VBScript that uses a SQL user to access a 2000 SQL SP4
clustered instance.
The script runs successfully only when I am logged on with a domain account.
What can the reason for this be?
Thanks in advance,
Ido Friedman
My first thought is that the VBScript is using NT authentication instead of
SQL Authentication.
Can you post the script?
Keith Kratochvil
"Ido friedman" <Idofriedman@.discussions.microsoft.com> wrote in message
news:A1B97509-42C7-4EBB-9BA3-786FA81E682F@.microsoft.com...
>I am trying to run a VBScript that uses a SQL user to access a 2000 SQL SP4
> clustered instance.
> The script runs successfully only when I am logged on with a domain
> account.
> What can the reason for this be?
>
> Thanks in advance,
> Ido Friedman

Monday, February 20, 2012

No such interface supported

I receive "No such interface supported" in SQL Server 2005, when:

1. on server, from my desktop client: attempting to create a maintenance plan within Management Studio without the wizard (with the wizard, works fine)

2. trying to copy, using SMO, an entire database from the server, to my local machine, from again, my desktop client.

Any thoughts?

No solution, I'm afraid, but this is happening to me, too.

Did you find a solution yourself by any chance?

|||Unfortunately, no |||Verified by me too.|||A good candidate to keepup the details under http://connect.microsoft.com/ and might check someone already reported. I presume you have applied SP1 on that SQL 2005.|||it's been a while, several installations ago, several months now, since I've had this issue, sicne applying SP1 I believe ...

No such interface supported

I receive "No such interface supported" in SQL Server 2005, when:

1. on server, from my desktop client: attempting to create a maintenance plan within Management Studio without the wizard (with the wizard, works fine)

2. trying to copy, using SMO, an entire database from the server, to my local machine, from again, my desktop client.

Any thoughts?

No solution, I'm afraid, but this is happening to me, too.

Did you find a solution yourself by any chance?

|||Unfortunately, no |||Verified by me too.|||A good candidate to keepup the details under http://connect.microsoft.com/ and might check someone already reported. I presume you have applied SP1 on that SQL 2005.|||it's been a while, several installations ago, several months now, since I've had this issue, sicne applying SP1 I believe ...

No such interface supported

I receive "No such interface supported" in SQL Server 2005, when:

1. on server, from my desktop client: attempting to create a maintenance plan within Management Studio without the wizard (with the wizard, works fine)

2. trying to copy, using SMO, an entire database from the server, to my local machine, from again, my desktop client.

Any thoughts?

No solution, I'm afraid, but this is happening to me, too.

Did you find a solution yourself by any chance?

|||Unfortunately, no |||Verified by me too.|||A good candidate to keepup the details under http://connect.microsoft.com/ and might check someone already reported. I presume you have applied SP1 on that SQL 2005.|||it's been a while, several installations ago, several months now, since I've had this issue, sicne applying SP1 I believe ...

No such interface supported

I receive "No such interface supported" in SQL Server 2005, when:

1. on server, from my desktop client: attempting to create a maintenance plan within Management Studio without the wizard (with the wizard, works fine)

2. trying to copy, using SMO, an entire database from the server, to my local machine, from again, my desktop client.

Any thoughts?

No solution, I'm afraid, but this is happening to me, too.

Did you find a solution yourself by any chance?

|||Unfortunately, no |||Verified by me too.|||A good candidate to keepup the details under http://connect.microsoft.com/ and might check someone already reported. I presume you have applied SP1 on that SQL 2005.|||it's been a while, several installations ago, several months now, since I've had this issue, sicne applying SP1 I believe ...