Sql Cannot connect: group

Showing posts with label group. Show all posts

Sunday, March 25, 2012

Cannot divide

I'm having a real hard time with a division in my table. It is in a field in a group that I have no problem getting the correct result by these expressions:
=SUM(Fields!NrOfOptysTotal.Value + Fields!NrOfActivities.Value) or
=SUM(Fields!NrOfOptysTotal.Value - Fields!NrOfActivities.Value)
But if I do this:
=SUM(Fields!NrOfOptysTotal.Value / Fields!NrOfActivities.Value) or
=SUM(Fields!NrOfOptysTotal.Value * Fields!NrOfActivities.Value)
,I don't get the correct results, I only get Infinity or NaN, but I shouldn't. I have tried manipulating the expressions like
=SUM(Fields!NrOfOptysTotal.Value) / SUM(Fields!NrOfActivities.Value) and several other combinations, but it never works. I really don't understand the problem! Please help...Somehow I got it to work now with
=SUM(Fields!NrOfOptysTotal.Value) / SUM(Fields!NrOfActivities.Value)
I'm SURE I tried that before, I don't get it, but whatever...
"FredrikT" wrote:
> I'm having a real hard time with a division in my table. It is in a field in a group that I have no problem getting the correct result by these expressions:
> =SUM(Fields!NrOfOptysTotal.Value + Fields!NrOfActivities.Value) or
> =SUM(Fields!NrOfOptysTotal.Value - Fields!NrOfActivities.Value)
> But if I do this:
> =SUM(Fields!NrOfOptysTotal.Value / Fields!NrOfActivities.Value) or
> =SUM(Fields!NrOfOptysTotal.Value * Fields!NrOfActivities.Value)
> ,I don't get the correct results, I only get Infinity or NaN, but I shouldn't. I have tried manipulating the expressions like
> =SUM(Fields!NrOfOptysTotal.Value) / SUM(Fields!NrOfActivities.Value) and several other combinations, but it never works. I really don't understand the problem! Please help...
>

Monday, March 19, 2012

cannot create job steps in 2005

I have a feeling this might be a security problem so I posting the question
in the security group as well. Sorry for the double post, I'll paste any
answers over there as well.
Here's the problem;
I'm trying to do some prototyping with SQL 2005 Standard - Full Text Search
in preparation for moving away from SQL 2000. I setup a FTS index and tried
to create a job to rebuild the index nightly. This job build feature is
built right into the
FTS wizard. The job is created but it fails to create the steps and just
says "Failed to connect to server...blah blah blah....Naped Pipes Provider,
Error 40, Could not open connection"
At first I thought it was something with FTS not configured right but then I
just tried to create simple maintenance plan job and the same thing
happened. It
couldn't create the job step. The message from that was even more helpful.
It said "Job failed"

I'm doing all this from SSMS logged in with SA.
Anyone have any idea why I can't create job steps on a newly installed SQL
2005 using SA?
Thanks in advance
--
MazSome of the things to check for:
- Make sure that the 'shared memory' prtocol is enabled on the server and
has order=1
- Make sure that sql server is configured to listen on the shared memory net
lib
You can check the settings using the SQL Server Configuration Manager.
hth
--
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>I have a feeling this might be a security problem so I posting the question
> in the security group as well. Sorry for the double post, I'll paste any
> answers over there as well.
> Here's the problem;
> I'm trying to do some prototyping with SQL 2005 Standard - Full Text
> Search
> in preparation for moving away from SQL 2000. I setup a FTS index and
> tried
> to create a job to rebuild the index nightly. This job build feature is
> built right into the
> FTS wizard. The job is created but it fails to create the steps and just
> says "Failed to connect to server...blah blah blah....Naped Pipes
> Provider,
> Error 40, Could not open connection"
> At first I thought it was something with FTS not configured right but then
> I
> just tried to create simple maintenance plan job and the same thing
> happened. It
> couldn't create the job step. The message from that was even more
> helpful.
> It said "Job failed"

I'm doing all this from SSMS logged in with SA.
> Anyone have any idea why I can't create job steps on a newly installed SQL
> 2005 using SA?
> Thanks in advance
> --
> Maz
>|||Thanks Vikran
I have everything enabled except VIA. Don't know what that is so I left it
alone.
I think there's something wrong with this FTS product in SQL Server. I'm
logged into SQL as the system adminstrator (sa). I'm also logged onto
windows as a domain admin. It can't be security. it doesn't seem to be a
config problem. I'm stumped
--
Maz
"Vikram Vamshi" wrote:

> Some of the things to check for:
> - Make sure that the 'shared memory' prtocol is enabled on the server and
> has order=1
> - Make sure that sql server is configured to listen on the shared memory n
et
> lib
> You can check the settings using the SQL Server Configuration Manager.
> hth
> --
> Vikram Vamshi
> Database Engineer
> Eclipsys Corporation
> "Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
> news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>
>|||Did you ever get this resolved? I'm having the same problem. I'm using
the sa account and logged in as domain admin and yet I cannot create a
job step for any maintenance plan. We're running SQL 2005 Standard
with noe fancy bells or whistles. Even the "Wizard" craps out every
time. Can anyone offer any advice?
E
On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> Thanks Vikran
> I have everything enabled except VIA. Don't know what that is so I left i
t
> alone.
> I think there's something wrong with this FTS product inSQLServer. I'm
> logged intoSQLas the system adminstrator (sa). I'm also logged onto
> windows as a domain admin. It can't be security. it doesn't seem to be a
> config problem. I'm stumped
> --
> Maz
>
> "Vikram Vamshi" wrote:
>
>
>
>
>
>
> - Show quoted text -|||No, I never got it resolved. For the time being I've tabled the issue and
moved on to the rest of the project development. However, I will need an
answer in a few weeks.
Doesn anyone understand what has changed with permissions in SQL 2005 OR is
this a hard bug and no one (except a few of us) seem to care
Thanks anyone
--
Maz
"Elroyskimms" wrote:

> Did you ever get this resolved? I'm having the same problem. I'm using
> the sa account and logged in as domain admin and yet I cannot create a
> job step for any maintenance plan. We're running SQL 2005 Standard
> with noe fancy bells or whistles. Even the "Wizard" craps out every
> time. Can anyone offer any advice?
> E
>
> On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>|||SP2 was released a couple of weeks ago. I read a bug report where
someone mentioned an issue similar to this and the MS tech linked to
the SP2 download site. Of course, it is always MS's policy to say
"install the service pack" as a standard answer to all of your
questions (about as useful as using 42 as the answer). I will try and
run the install of SP2 over the weekend and see if that resolves the
issue. I'll report back here with the results.
-E
On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> No, I never got it resolved. For the time being I've tabled the issue and
> moved on to the rest of the project development. However, I will need an
> answer in a few weeks.
> Doesn anyone understand what has changed with permissions in SQL 2005 OR i
s
> this a hard bug and no one (except a few of us) seem to care
> Thanks anyone
> --
> Maz
>
> "Elroyskimms" wrote:
>
>
>
>
>
>
>
>
>
>
>
>
> - Show quoted text -|||Theh machine I'm running this on is Windows 2003 Server. It has all the
latest security updates, sp's, etc. It's totally clean
Give it a shot but don't hold your breath until it works.
MICROSOFT TECHS MONITORING THIS BOARD: Any suggestions?
Maz
"Elroyskimms" wrote:

> SP2 was released a couple of weeks ago. I read a bug report where
> someone mentioned an issue similar to this and the MS tech linked to
> the SP2 download site. Of course, it is always MS's policy to say
> "install the service pack" as a standard answer to all of your
> questions (about as useful as using 42 as the answer). I will try and
> run the install of SP2 over the weekend and see if that resolves the
> issue. I'll report back here with the results.
> -E
> On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>

cannot create job steps in 2005

I'm doing all this from SSMS logged in with SA.
Anyone have any idea why I can't create job steps on a newly installed SQL
2005 using SA?
Thanks in advance
Maz
Some of the things to check for:
- Make sure that the 'shared memory' prtocol is enabled on the server and
has order=1
- Make sure that sql server is configured to listen on the shared memory net
lib
You can check the settings using the SQL Server Configuration Manager.
hth
Vikram Vamshi
Database Engineer
Eclipsys Corporation
"Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>I have a feeling this might be a security problem so I posting the question
> in the security group as well. Sorry for the double post, I'll paste any
> answers over there as well.
> Here's the problem;
> I'm trying to do some prototyping with SQL 2005 Standard - Full Text
> Search
> in preparation for moving away from SQL 2000. I setup a FTS index and
> tried
> to create a job to rebuild the index nightly. This job build feature is
> built right into the
> FTS wizard. The job is created but it fails to create the steps and just
> says "Failed to connect to server...blah blah blah....Naped Pipes
> Provider,
> Error 40, Could not open connection"
> At first I thought it was something with FTS not configured right but then
> I
> just tried to create simple maintenance plan job and the same thing
> happened. It
> couldn't create the job step. The message from that was even more
> helpful.
> It said "Job failed"

I'm doing all this from SSMS logged in with SA.
> Anyone have any idea why I can't create job steps on a newly installed SQL
> 2005 using SA?
> Thanks in advance
> --
> Maz
>
|||Thanks Vikran
I have everything enabled except VIA. Don't know what that is so I left it
alone.
I think there's something wrong with this FTS product in SQL Server. I'm
logged into SQL as the system adminstrator (sa). I'm also logged onto
windows as a domain admin. It can't be security. it doesn't seem to be a
config problem. I'm stumped
Maz
"Vikram Vamshi" wrote:

> Some of the things to check for:
> - Make sure that the 'shared memory' prtocol is enabled on the server and
> has order=1
> - Make sure that sql server is configured to listen on the shared memory net
> lib
> You can check the settings using the SQL Server Configuration Manager.
> hth
> --
> Vikram Vamshi
> Database Engineer
> Eclipsys Corporation
> "Spicy Mikey" <Maz@.newsgroups.nospam> wrote in message
> news:A993F690-0AC3-4FA6-9760-85C2F24523C8@.microsoft.com...
>
>
|||Did you ever get this resolved? I'm having the same problem. I'm using
the sa account and logged in as domain admin and yet I cannot create a
job step for any maintenance plan. We're running SQL 2005 Standard
with noe fancy bells or whistles. Even the "Wizard" craps out every
time. Can anyone offer any advice?
E
On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> Thanks Vikran
> I have everything enabled except VIA. Don't know what that is so I left it
> alone.
> I think there's something wrong with this FTS product inSQLServer. I'm
> logged intoSQLas the system adminstrator (sa). I'm also logged onto
> windows as a domain admin. It can't be security. it doesn't seem to be a
> config problem. I'm stumped
> --
> Maz
>
> "Vikram Vamshi" wrote:
>
>
>
> - Show quoted text -
|||No, I never got it resolved. For the time being I've tabled the issue and
moved on to the rest of the project development. However, I will need an
answer in a few weeks.
Doesn anyone understand what has changed with permissions in SQL 2005 OR is
this a hard bug and no one (except a few of us) seem to care
Thanks anyone
Maz
"Elroyskimms" wrote:

> Did you ever get this resolved? I'm having the same problem. I'm using
> the sa account and logged in as domain admin and yet I cannot create a
> job step for any maintenance plan. We're running SQL 2005 Standard
> with noe fancy bells or whistles. Even the "Wizard" craps out every
> time. Can anyone offer any advice?
> E
>
> On Feb 5, 8:34 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>
|||SP2 was released a couple of weeks ago. I read a bug report where
someone mentioned an issue similar to this and the MS tech linked to
the SP2 download site. Of course, it is always MS's policy to say
"install the service pack" as a standard answer to all of your
questions (about as useful as using 42 as the answer). I will try and
run the install of SP2 over the weekend and see if that resolves the
issue. I'll report back here with the results.
-E
On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
> No, I never got it resolved. For the time being I've tabled the issue and
> moved on to the rest of the project development. However, I will need an
> answer in a few weeks.
> Doesn anyone understand what has changed with permissions in SQL 2005 OR is
> this a hard bug and no one (except a few of us) seem to care
> Thanks anyone
> --
> Maz
>
> "Elroyskimms" wrote:
>
>
>
>
>
>
> - Show quoted text -
|||Theh machine I'm running this on is Windows 2003 Server. It has all the
latest security updates, sp's, etc. It's totally clean
Give it a shot but don't hold your breath until it works.
MICROSOFT TECHS MONITORING THIS BOARD: Any suggestions?
Maz
"Elroyskimms" wrote:

> SP2 was released a couple of weeks ago. I read a bug report where
> someone mentioned an issue similar to this and the MS tech linked to
> the SP2 download site. Of course, it is always MS's policy to say
> "install the service pack" as a standard answer to all of your
> questions (about as useful as using 42 as the answer). I will try and
> run the install of SP2 over the weekend and see if that resolves the
> issue. I'll report back here with the results.
> -E
> On Mar 5, 6:16 am, Spicy Mikey <M...@.newsgroups.nospam> wrote:
>
>

Sunday, March 11, 2012

Cannot create an instance of OLE DB provider "IBMDADB2" for linked server

System:Win 2003, SQL Server 2005, Using an AD win account that is not a member of the Admin group on the server.

Error message from Management Studio query window:

Msg 7302, Level 16, State 1, Line 1

Cannot create an instance of OLE DB provider "IBMDADB2" for linked server "Sname".

Event messages associated with this error:

App Event ID: 19036

The OLE DB initialization service failed to load. Reinstall Microsoft Data Access Components. If the problem persists, contact product support for the OLEDB provider.

Sys Event ID: 10016

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {2206CDB0-19C1-11D1-89E0-00C04FD7A829}

to the user domain\user SID (S-1-5-21-126051702-1034962659-2130403006-7826). This security permission can be modified using the Component Services administrative tool.

I’m getting this error message when trying to run an openquery statement through a linked server to DB2. (SELECT * FROM OPENQUERY(Sname, 'SELECT * FROM tablename’))

The linked server has a remote login and password that it uses to connect to DB2.

I found this from another post on how to fix this error:

Expand Component Services - Computers - My Computer - DCOM Config Select MSDAINITIALIZE Right Click properties then security

Under Security - Launch Permission: enable Local Launch and Local Activation for your SQL Service account

Under Security - Access permissions: Allow System: Local Access and Remote Access.

After completing these steps I still get the error message but the events are no longer generated.I’ve also tried different variations of these steps.The only way I can get this to work is to either make the AD user a member of the Admin group on the server or by putting in a user account that has admin rights to the server in the MSDAINITIALIZE properties – Identity Tab – Run this App as this User.

Can someone please tell me the steps that I’m missing?

Additional info:

If I set the providers allowinprocess to 1 with this,

EXEC master.dbo.sp_MSset_oledb_prop N'IBMDADB2', N'AllowInProcess', 1

It responds with this error:

OLE DB provider "IBMDADB2" for linked server "LName" returned message " SQL10007N Message "0" could not be retrieved. Reason code: "2".

Msg 7303, Level 16, State 1, Line 1

Cannot initialize the data source object of OLE DB provider "IBMDADB2" for linked server "LName".

Thursday, March 8, 2012

Cannot create a connection to data source !!!!!!!

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

no it usues whatever account iis is running under.

IUSR_something I think.

if you want use integrated auth you need to use impersonation.

|||ok....then how do incorporate personalization in Reporting Services! I don't see anything on that...I think you're referring to .NET, I'm talking about Reporting Services 2005|||I posted this in the wrong forum by accident..I'll move it to Reporting Services..sorry

Cannot create a connection to data source !!!! SSRS 2005

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Are the client, RS, and SQL server all on different machines? If so, then you are probably hitting the double-hop problem. This is a limitation of integrated security in environments which don't support kerberos.

Tudor talks about it a bit in this blog entry:

http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

You might want to check that out and see if the problem described there is what you are experiencing.

|||

No, I have gotten this to work fine for my test server which is the server running both RS and SQL Server 2005. RS and SQL Server 2005 are on the same box. The server I'm trying to connect to now is a different server's DB which is where the datasource is pointing to. So there is no double-hop issue here at least!

So in other words if I change the datasets to use the datasources that piont to ServerA below, my report runs for me ok. If I change the datasets in my report to talk to ServerB, I get the error immediately. The datasets are running stored procs and referencing the data sources for the DB connection in the dataset properties. I am using 3 datasets in my report and around 4 datasources are in my project that are uploaded automatically when I deploy my report to the report serve (TestServerA)

TestServerA - Has RS and SQL Server 2005. When using Datasources that point to this server's stored procs, it works for me at least the other users still have issues though where it's prompting them for a windows username and password

ServerB - a production server running SQL Server 2000 (doesn't have Reporting Services on it, we're just runnign stored procs against it for the datasets) in which the dataset (on TestServerA) is trying to run a stored proc off of ServerB. It stil uses ServerA for Reporting services part...whcih is where I'm getting the error from my own client when trying to run the report from the client in Report Manager

|||Ok, now I tried logging on directly to my TestServerA and ran the report from IE on that server (report Manager) and it works fine. Ok, so how am I getting a double hop issue if I have everything installed on the same server? I don't think hopping is the issue here still!|||scratch my last response...it was working only because my datasets were pointing to the datasources that were pointing to my TestServerA. Once I changed it back to the point where I got the error (for this post) whcih was to chagne teh datasets to point to the datasources that point to ServerB, I still get the error, even when running the report from TestServerA's Report Manager....|||

Here's a diagram to show you what's going on. Keep in mind, if the datasets aren't using datasources that point to ServerB and are using datasources that point to TestServerA, all works fine...it's just when my report is using datasources trying to talk to ServerB.

http://www.webfound.net/diagram.jpg

|||

Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

Thanks,

Tudor

|||

In your second setup (ServerB) you are describing what I would expect to be the symptoms of the double hop problem. You have 3 machines, A->B->C. A is the client machine, B is the machine with reporting services, and C is the machine that has the data you are reporting against. You are trying to pass credentials from machine A all the way to machine C. Unless you have set up your environment to allow kerberos delegation (see the links that I pasted above), then this will fail. If you don't want to (or cannot) enable delegation, then a workaround for you is to store credentials for accessing the datasources in the catalog.

In your 1st scenario (TestServerA), I am not certain why they are getting prompted for credentials. I suspect it is because your test users don't have access to your machine, are they able to connect when providing their credentials?

|||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

,I have missed the same problem once ,the problem is that ur datasource was set ot windows Authentification,(if u pay more attention to ur report'Connection string,u could find the bugs),but ur database has no right for this kind of user,

u could follow this steps to add a user or a group which the user belong to :

1.login in database

2.extend the security node

3.extend the logins node

3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

And there is a skill,if ur user is a member of administrator,and u assign permissions to the other user,by default,this kind of user only is a menber of user,dont have the role of administrator,so if u use the windows Authentification to build connection string for ur report,the user who just have a role of user don't have logins to database,u need to follow the steps above to add the user or the group to Database'logins.

|||Samuel, they definitely already have logins to the database, right down to the permissions of the stored procs being called by the datasets so this is covered! They have read rights as well as datawriter (which isn't really needed). This is why I posted, I have done almost everything.|||

I believe you are running into a couple of problems which are not necessarily related.

When you are prompted for credentials in IE with the standard credentials dialog, it is because IIS did not accept the user's token when IE presented it in response to a 401. This usually means that the user is not a valid user on the target machine. Check your IIS logs for 401s.

The datasource problems are because the user we are trying to access the database with is not allowed access. This can be for any number of reasons, the double-hop issue being a pretty common one when people are trying to pass through Windows credentials.

|||I have a similar problem to FlavorFlave. Our setup:

Machine A : client
Machine B: SSRS 2005
Machine C: SSAS 2000

Running reports from Machine B works, running from from A does not - getting the exact error he specified. Logged on to machine A with a limited user account, onto B/C with full admin rights.

Enabling delegation is not going to be possible on our network. John, i see you say a workaround is to "store credentials for accessing the datasources in the catalog". Not sure what you meant by this.. or where to do this?|||never mind.. ive figured it out :)

stored the credentials securely within the datasource on the report server itself. works now... though its slower to initialise than when the security is integrated.
|||talwar, can you explain the steps you took in detail so hopefully I can do the same...thanks

Cannot create a connection to data source !!!! SSRS 2005

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Tudor talks about it a bit in this blog entry:

http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

You might want to check that out and see if the problem described there is what you are experiencing.

|||

http://www.webfound.net/diagram.jpg

|||

Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

Thanks,

Tudor

|||

|||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

u could follow this steps to add a user or a group which the user belong to :

1.login in database

2.extend the security node

3.extend the logins node

3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

I believe you are running into a couple of problems which are not necessarily related.

|||I have a similar problem to FlavorFlave. Our setup:

Machine A : client
Machine B: SSRS 2005
Machine C: SSAS 2000

Running reports from Machine B works, running from from A does not - getting the exact error he specified. Logged on to machine A with a limited user account, onto B/C with full admin rights.

Cannot create a connection to data source !!!! SSRS 2005

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Tudor talks about it a bit in this blog entry:

http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

You might want to check that out and see if the problem described there is what you are experiencing.

|||

http://www.webfound.net/diagram.jpg

|||

Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

Thanks,

Tudor

|||

|||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

u could follow this steps to add a user or a group which the user belong to :

1.login in database

2.extend the security node

3.extend the logins node

3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

I believe you are running into a couple of problems which are not necessarily related.

|||

I have a similar problem to FlavorFlave. Our setup:

Machine A : client
Machine B: SSRS 2005
Machine C: SSAS 2000

Running

reports from Machine B works, running from from A does not - getting the

exact error he specified. Logged on to machine A with a limited user

account, onto B/C with full admin rights.

Enabling delegation is

not going to be possible on our network. John, i see you say a

workaround is to "store credentials for accessing the datasources in

the catalog". Not sure what you meant by this.. or where to do this?|||never mind.. ive figured it out :)

stored the credentials securely within the datasource on the report server itself. works now... though its slower to initialise than when the security is integrated.|||talwar, can you explain the steps you took in detail so hopefully I can do the same...thanks

Cannot create a connection to data source !!!! SSRS 2005

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg

Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

An error has occurred during report processing.

Cannot create a connection to data source 'datasourcename'.

For more information about this error navigate to the report server on the local server machine, or enable remote errors

Tudor talks about it a bit in this blog entry:

http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

You might want to check that out and see if the problem described there is what you are experiencing.

|||

http://www.webfound.net/diagram.jpg

|||

Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

Thanks,

Tudor

|||

|||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

u could follow this steps to add a user or a group which the user belong to :

1.login in database

2.extend the security node

3.extend the logins node

3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

I believe you are running into a couple of problems which are not necessarily related.

|||I have a similar problem to FlavorFlave. Our setup:

Machine A : client
Machine B: SSRS 2005
Machine C: SSAS 2000

Running reports from Machine B works, running from from A does not - getting the exact error he specified. Logged on to machine A with a limited user account, onto B/C with full admin rights.

Cannot create a connection to data source - SSRS 2005

I cannot get this error resolve either for myself or any users, and I'm
actually part of the Admin group! Furthermore, a user with whom I'm
tring allow to view this report keeps getting prompted for their
windows username and password. I thought that since this datasource
was set to Windows Authentification that it would just pass it through?
I'm pulling my hair out at this point:
Screen Shots:
http://www.webfound.net/datasource_connection.jpg
http://www.webfound.net/datasource_connection2.jpg
http://www.webfound.net/datasource_connection3.jpg
Also As far as I know, I've given proper permissions to the right
logins and right users on my SQL Databases and related stored procs
that the datasets (not datasource) run
An error has occurred during report processing.
Cannot create a connection to data source 'datasourcename'.
For more information about this error navigate to the report server on
the local server machine, or enable remote errorsWith windows authentication issue, there is a parameter in Internet
Explorer which can cause this. Goto Tools|Internet options|Security
then I think the problem is likely to be the Intranet Zone, but
depending on your setup it could be one of the others too. Anyway,
select the Intranet Zone then custom, scroll to the bottom and you
should see User Authentication, you've probably got it set to Prompt on
this particular PC. This seems to be the default on Windows 2000
machines.
You may also find Active Directory policies can override this setting,
when they reboot.
On the data source issue:
A bit of a long shot this, but try removing the hyphens '-' from the
datasource names. It's never a good idea to put these sorts of
characters in SQL related stuff (this is the voice of experience!).
Also, can you run it from BIDS? If you can, then it would suggest the
server you are deploying to cannot see the server containing the actual
datasource.
Also, it may be worth checking the datasource "file" on the report
server. Remember, when you deploy a report it won't overwrite a
datasource if it already exists, and if it's been changed on the server
in any way the report will use that instead. Having said that, viewing
your screenshots it doesn't look like this is the case.
My hunch is your report server can't gain access to the server with the
data. Maybe describing the server setup a bit more may shed some more
light on the issue.
Hope some of this helps.
Cheers
Chris
dba123 wrote:
> I cannot get this error resolve either for myself or any users, and
> I'm actually part of the Admin group! Furthermore, a user with whom
> I'm tring allow to view this report keeps getting prompted for their
> windows username and password. I thought that since this datasource
> was set to Windows Authentification that it would just pass it
> through?
> I'm pulling my hair out at this point:
> Screen Shots:
> http://www.webfound.net/datasource_connection.jpg
> http://www.webfound.net/datasource_connection2.jpg
> http://www.webfound.net/datasource_connection3.jpg
>
> Also As far as I know, I've given proper permissions to the right
> logins and right users on my SQL Databases and related stored procs
> that the datasets (not datasource) run
> An error has occurred during report processing.
> Cannot create a connection to data source 'datasourcename'.
> For more information about this error navigate to the report server on
> the local server machine, or enable remote errors

Saturday, February 25, 2012

cannot connect to the local instance

I have SQL server 2000 installed on my machine,
Under the "SQL Server Group" , if I click on the local insatnce (computerNam
e\NETSDK(window NT)) , I get the following error:
"The SQL server \\computerName\NETSDK is not known to be running, are you s
ure you wish to connect"
if I click yes, I get this second error message:
"A connection could not be established to computername/NETSDK.
Reason: SQL server does not exist or access denied.
ConnectionOpen(Connect())...
Please verify SQL Server is running and check your SQL Server registration p
roperties..."
when I check the registration, nothing look unusual for me.
thanks for helpYou didn't indicate whether you verified that the MSSQLServer service was
running. If so, are you using windows authentication or SQL authentication?
If you are using Windows authentication, try the sa account (assuming you
know/remember the password and that the server is in mixed mode). If you
get in using sa, check to be sure that you haven't removed the
builtin\administrators login without also adding your own. People tend to
forget this and get themselves locked out...
"tony" <myemail@.mail.com> wrote in message
news:2C272FD6-7C9E-441D-9AB7-DE70AC17946F@.microsoft.com...
> I have SQL server 2000 installed on my machine,
> Under the "SQL Server Group" , if I click on the local insatnce
(computerName\NETSDK(window NT)) , I get the following error:
> "The SQL server \\computerName\NETSDK is not known to be running, are you
sure you wish to connect"
> if I click yes, I get this second error message:
> "A connection could not be established to computername/NETSDK.
> Reason: SQL server does not exist or access denied.
> ConnectionOpen(Connect())...
> Please verify SQL Server is running and check your SQL Server registration
properties..."
> when I check the registration, nothing look unusual for me.
> thanks for help
>|||Hi Tony,
Thank you for using the newsgroup and thanks for Don's reply.
Don have pointed out some place you should check first and here I just want
to add some more information for your reference. You could look at this
following article:
INF: Potential Causes of the "SQL Server Does Not Exist or Access Denied"
Error Message
http://support.microsoft.com/?id=328306
Hope this help. If you still have questions, please feel free to post
message here and we are glad to help.
Thanks
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||the problem occured while backing up a database, the backup failed and I los
t connection to my local instance.
SQL server(as interface) is running fine on my machine and I can connect to
other remote server but not to the local one.
when I try to register the local one (under 'SQL Server Group') , I get an e
rror message saying that 'SQL Server does not exist or .....)
when I check the service, SQLServer service does not have even an entry an
d I couldn't locate it as a service.
I uninstalled SQL server (client tool) and I can still run the client on my
machine as if I didn't uninstall it, but with no connection to the local one
.
I installed it again and still getting the same error message.
The service does not exist, and SQL server is installed, how can that happen
s ?
thank you again.|||how can I add MSSQLServer as a service.
SQL server is running but does not have entry under the Service node.|||Hi Tony,
Thank you for your update.
It is a little strange now. Do you mean that after un-install the SQL
Server, and then in the Services Snap-in in the MMC, you cannot see the
SQL Server Service but your application could still connect to it? When a
SQL Server is running well on you computer, it should have the service
configured on your computer, no matter it is started or stopped.
I would like to narrow down the problem step-by-step
1) Please go to the command prompt ( 'Start'->'Run', then type in 'cmd' and
press Enter), then type 'net start', could you get any service of SQL
Server? It could be
MSSQLSERVER or MSSQL$<instance_name>.
2) If no, type in 'net start MSSQLSERVER, what's the message you get?
Note: For other SQL Server instance, type in 'net start
MSSQL$<The_Instance_Name>'
3) If it said
The MSSQLSERVER service is starting......
The MSSQLSERVER service was started successfully.
OR
The requested service has already been started.
Then you could be sure that the SQL Server is installed on your computer.
Then, please use the Enterprise Manager to register it.
Hope this helps.
Thanks
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.|||Hi Baisong,
Thank you for yall your help.
I reinstalled SQL server (client) again in order to see if it is going to ap
pear in the " Services Snap-in in the MMC",
and it INSTALLED SUCCEFULLY (as the install said) , and I run it, through
"Entreprise Manager", and I could connect to other remote sql servers, but w
hen I tried to register the local instance, I get a message :"SQL server doe
s not exist or..."
then I checked the Services Snap-in in the MMC, but still cannot see it or s
ee any SQL service at all.
Then I followed your instruction excatly:
1) when typing : "net start" , I can see all services except anything for SQ
L or MSSQL or .......
2) when typing : "net start MSSQLSERVER" , that's what I got: "The service
name is invalid"
After done all that, I create a shortcut for "Entreprise Manager" on the des
ktop, then I uninstalled SQL server again.
1) Now I cannot see "Microsoft SQL Sever" entry under start -> Programs ->
Microsoft Sql server anymore,
but the shortcut to it still exist on my desktop, and when I double click it
, it run normally as I didn't uninstall it, and I still
can run queries and connect to other remote servers except the local one, th
en I followed you instruction again, and got
the same message as I got before the uninstall; (nothing for MSSQL.... and
"The service name is inavlid").
Is there anyway to add MSSQLServer as a service in the Services Snap-in in t
he MMC manually ?
Thank you again|||Hi Tony,
Thank you for your update.
From your informtion, it seems you do not installed the SQL Server service
on you machine, just the SQL Server management tools such as the Enterprise
Manager or Query Analyzer.
So, I recommend you to un-installed the tools again. Then check your
Operating System and choose the right edition of SQL Server. Please refer
to the following article:
Operating Systems Supported by the Editions of SQL Server 2000
http://msdn.microsoft.com/library/d...-us/architec/8_
ar_ts_7eur.asp
Then, please re-intall the proper SQL Server 2000 by choosing 'Server and
Client Tools' selection during the intallation. After all the installation,
you will notice the SQL Server Service is in the Server snap-shot in the
MMC.
Hope this helps and if you still have question, please feel free to post
message here and I am glad to help.
Thanks
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

Friday, February 24, 2012

Cannot connect to SQL server with NT groups

Hi.
Have problems connecting to SQL server with NT group authentication.
Get error 4064: Error connecting to user default database.

There's no problems connecting with NT users og SQL users.

SQL2000 + Windows2000 both running latest service packs. All SP have been reinstalled.

The server suddenly stopped accepting NT group logins. It have been running for 1 year with no problems - 4 days ago it started generating this error.

Any ideas anyone?Talk to the network guys...something changed...

Cannot connect to SQL server over network after SP2

Hello,
I'll try my luck in this group before I re-install the whole thing.
I'm running MS SQL Server 2005 developer edition on the Windows Server
2003 Small Business Edition.
Few days ago I have updated to the SP2 via windows update.
Since then I cannot connect to the SQL server remotely (using
Management Studio).
- If I log remotely to the server box I can connect locally and all
looks fine.
However, from the network it does not work.
- The SQL Server browser is running..
- TCP & Named Pipes are enabled.
- No errors in the Event Viewer
- "Allow remote connections to this server" property is enabled
- Both firewalls (server & client) are off.
- Both authentication types (SQL auth / Windows auth) are not working
Has anyone had similar problem? Any ideas?
Thank you,
Damir SudarevicWhat is the error message you are getting? We just finished installing SP2
on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
log event at all? Or when trying to access the server from remote location
the computer refuses to see the SQL server?
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:
> Hello,
> I'll try my luck in this group before I re-install the whole thing.
> I'm running MS SQL Server 2005 developer edition on the Windows Server
> 2003 Small Business Edition.
> Few days ago I have updated to the SP2 via windows update.
> Since then I cannot connect to the SQL server remotely (using
> Management Studio).
> - If I log remotely to the server box I can connect locally and all
> looks fine.
> However, from the network it does not work.
> - The SQL Server browser is running..
> - TCP & Named Pipes are enabled.
> - No errors in the Event Viewer
> - "Allow remote connections to this server" property is enabled
> - Both firewalls (server & client) are off.
> - Both authentication types (SQL auth / Windows auth) are not working
>
> Has anyone had similar problem? Any ideas?
> Thank you,
> Damir Sudarevic
>|||On Jun 27, 8:12 pm, Mohit K. Gupta
<MohitKGu...@.discussions.microsoft.com> wrote:
> What is the error message you are getting? We just finished installingSP2
> on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> log event at all? Or when trying to access the server from remote location
> the computer refuses to see the SQL server?
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
> > Hello,
> > I'll try my luck in this group before I re-install the whole thing.
> > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > 2003 Small Business Edition.
> > Few days ago I have updated to theSP2via windows update.
> > Since then Icannotconnectto the SQL server remotely (using
> > Management Studio).
> > - If I log remotely to the server box I canconnectlocally and all
> > looks fine.
> > However, from the network it does not work.
> > - The SQL Server browser is running..
> > - TCP & Named Pipes are enabled.
> > - No errors in the Event Viewer
> > - "Allow remote connections to this server" property is enabled
> > - Both firewalls (server & client) are off.
> > - Both authentication types (SQL auth / Windows auth) are not working
> > Has anyone had similar problem? Any ideas?
> > Thank you,
> > Damir Sudarevic
Hi,
No error messages. The Management Studio (from remote clients - more
than one) simply hangs up.
The studio actually sees the server (in browse servers), but
connection can not be established.
If I log in remotely to the server box and start MS over there it
works fine.
Thanks.|||Hangs up? SO you have to kill the SSMS and then you can use the computer,
only thing I had that is when our network guys mucked up the firewall
settings. Check for port 1433 connection.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:
> On Jun 27, 8:12 pm, Mohit K. Gupta
> <MohitKGu...@.discussions.microsoft.com> wrote:
> > What is the error message you are getting? We just finished installingSP2
> > on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> > log event at all? Or when trying to access the server from remote location
> > the computer refuses to see the SQL server?
> >
> > --
> > Mohit K. Gupta
> > B.Sc. CS, Minor Japanese
> > MCTS: SQL Server 2005
> >
> > "Damir" wrote:
> > > Hello,
> >
> > > I'll try my luck in this group before I re-install the whole thing.
> >
> > > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > > 2003 Small Business Edition.
> >
> > > Few days ago I have updated to theSP2via windows update.
> > > Since then Icannotconnectto the SQL server remotely (using
> > > Management Studio).
> >
> > > - If I log remotely to the server box I canconnectlocally and all
> > > looks fine.
> >
> > > However, from the network it does not work.
> >
> > > - The SQL Server browser is running..
> > > - TCP & Named Pipes are enabled.
> > > - No errors in the Event Viewer
> > > - "Allow remote connections to this server" property is enabled
> > > - Both firewalls (server & client) are off.
> > > - Both authentication types (SQL auth / Windows auth) are not working
> >
> > > Has anyone had similar problem? Any ideas?
> >
> > > Thank you,
> >
> > > Damir Sudarevic
> Hi,
> No error messages. The Management Studio (from remote clients - more
> than one) simply hangs up.
> The studio actually sees the server (in browse servers), but
> connection can not be established.
> If I log in remotely to the server box and start MS over there it
> works fine.
> Thanks.
>|||On Jun 29, 1:28 pm, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:
> Hangs up? SO you have to kill the SSMS and then you can use the computer,
> only thing I had that is when our network guys mucked up the firewall
> settings. Check for port 1433 connection.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
> > On Jun 27, 8:12 pm, Mohit K. Gupta
> > <MohitKGu...@.discussions.microsoft.com> wrote:
> > > What is the error message you are getting? We just finished installingSP2
> > > on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> > > log event at all? Or when trying to access the server from remote location
> > > the computer refuses to see the SQL server?
> > > --
> > > Mohit K. Gupta
> > > B.Sc. CS, Minor Japanese
> > > MCTS: SQL Server 2005
> > > "Damir" wrote:
> > > > Hello,
> > > > I'll try my luck in this group before I re-install the whole thing.
> > > > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > > > 2003 Small Business Edition.
> > > > Few days ago I have updated to theSP2via windows update.
> > > > Since then Icannotconnectto the SQL server remotely (using
> > > > Management Studio).
> > > > - If I log remotely to the server box I canconnectlocally and all
> > > > looks fine.
> > > > However, from the network it does not work.
> > > > - The SQL Server browser is running..
> > > > - TCP & Named Pipes are enabled.
> > > > - No errors in the Event Viewer
> > > > - "Allow remote connections to this server" property is enabled
> > > > - Both firewalls (server & client) are off.
> > > > - Both authentication types (SQL auth / Windows auth) are not working
> > > > Has anyone had similar problem? Any ideas?
> > > > Thank you,
> > > > Damir Sudarevic
> > Hi,
> > No error messages. The Management Studio (from remote clients - more
> > than one) simply hangs up.
> > The studio actually sees the server (in browse servers), but
> > connection can not be established.
> > If I log in remotely to the server box and start MS over there it
> > works fine.
> > Thanks.
Works!
Thank you Mohit, it was (something) about the ports. Changed TCP ports
to Dynamic and everything started working. Not quite sure what is
dynamic vs 1433; but as long as it works...
Thanks again,
Damir

Tuesday, February 14, 2012

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Sunday, March 25, 2012

Cannot divide

Monday, March 19, 2012

cannot create job steps in 2005

cannot create job steps in 2005

Sunday, March 11, 2012

Cannot create an instance of OLE DB provider "IBMDADB2" for linked server

Thursday, March 8, 2012

Cannot create a connection to data source !!!!!!!

Cannot create a connection to data source !!!! SSRS 2005

Cannot create a connection to data source !!!! SSRS 2005

Cannot create a connection to data source !!!! SSRS 2005

Cannot create a connection to data source !!!! SSRS 2005

Cannot create a connection to data source - SSRS 2005

Saturday, February 25, 2012

cannot connect to the local instance

Friday, February 24, 2012

Cannot connect to SQL server with NT groups

Cannot connect to SQL server over network after SP2

Cannot connect to SQL server over network after SP2

Cannot connect to SQL server over network after SP2

Tuesday, February 14, 2012

Cannot connect to localhost using Windows Security Group as login

Sql Cannot connect

Blog Archive

About Me