A new member could not be added to a local group because the member has the wrong account type

Hi all,

I installed SQL 2005 SP2 + ReportServices Add-in for Sharepoint (WSS 3.0). All it's OK until I try to grant database access in the Sharepoint Central Admin site.

I setup the Reporting Services Integration (Manage integration settings). I use the default SQL instance, I put the USERNAME and the PASSWORD of my ADMIN account in the ENTER CREDENTIALS windows.. When I click the "OK" button, I receive always the error ...

"A new member could not be added to a local group because the member has the wrong account type"

I tried a lot of things... without success.

Is there someone who can help me....

PS: There is no error in the LOG

Thanks

I am also having this same issue. I cannot seem to find any help for this out there by Google search or otherwise. I've seen some blip about installing on a domain controller. Please help.|||I discovered a workaround. I used the IP address of the DBMS instead of the local computer name. Then I used the DOMAINNAME\SP_Setup_User (or admin) account and password. This worked. Hopefully no ill effects.|||

Unfortunately, this approach didn't work for me. If any other idea, please let me know.

Thanks

|||

Erik,

I came to the conclusion to use the IP address of the SQL Server instead of the name because, you know how you want to map a drive to the same server using two different user accounts? Well, you have to use the server name for one mapping and then something else for the second mapping, like the IP address. It probably has nothing to do with this problem, but it reminded me of it. So it did work, at least on my system. Again, I do not know if there are any obscure consequences of doing this. So far all is well. Maybe there is a Microsoft person listening in or someone who could lend some thoughts to the situation for you.

Mike

|||

Hi Guys, had the same problem. Tried with IP address and yes it worked. However, when I went into Visual Studio and created a report when I went to deploy it a username/password form pops up. No matter what username/password is inserted can't get it to deploy. Any help would be greatly appreciated.

Keith

|||

Try using Fully Qualified domain Name of the SQL Server..

and It Works!..

|||

do you mean servername\username & password because it did not work. I enterede servername/username in the reporting services UI and then went into visual studio to deploy (on same machine) but when I went to deploy you would enter servername/username and it would just keep poping up and never do anything.

Any thing to look at for the account. I have tried a user account and on last atempt I used administrator, but no luck.

Thanks for any help!

|||

I have done some more work on it and in sharepoint central administration, reporting services, manage integration services, set to windows account. and it all saves with out complaing. Now when I gointo Visual studio on the same machine as reporting service and sharepoint I no longer get a log in box but I get "a connection could not be made to the report server... this operation is not supported on a report server that is configured to run in sharepoint integration...

anybody and thoughts?

Thanks

|||

did some more work/investigation and I stumbled into that if you go the sharepoint site, document library and try to add the new document type of reporting services, it does not show up in the list. So I think everything deployed okay but it appears there is no link between sharepoint and report services. Also incase this helps, sharepoint is not in the default website, but is it's own web site that instead of www we have companyweb. Other that reporting services sharpoint works fine.

Help!

|||

Keith,

Our report server web service is at http://{Report Server servername}:8080/ReportServer2K5, port 8080 being the new port of the re-enabled IIS default web site. However, the deployment properties for the VS 2005 report project actually had to be set like so: (1) TargetDataSourceFolder and TargetReportFolder = http://{SharePoint servername}:{Admin Site Port Number}/{Our Report Library Name}/, and (2) TargetServerURL = http://{SharePoint servername}:{Admin Site Port Number}/. I can deploy right from Visual Studio with this configuration. The account used for the Windows service identity is the same as that used for SharePoint administration in my case. There are a myriad of possible combinations for these accounts, though.

Mike