Error 28704.Unable to connect to the Analysis server.

I just can't figure this one out - two tier installation where I have followed the setup manual to the letter (i think). Analysis service is in fact running, I can even connect to it from a mgmt studio installed on the application tier.

I tried watching the network traffic to see where it might be getting confused, but the servers were talking via soap, and then encrytped the conversation so I couldn't diagnose anything in particular.

I would guess this is a permissions issue, but I am installing as TFSSetup, and this user is admin on both boxes + sa on sql server.

Any guesses

EDIT: after reinstalling everything I still get the error, but now have a more detailed error in the app log:
Event Type: Error
Event Source: Tfs
Event Category: None
Event ID: 3000
Date:  10/5/2005
Time:  4:56:15 PM
User:  N/A
Computer: Description:
An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
Technical Information (for the administrative staff):
Date (UTC): 10/5/2005 8:56:15 PM
Machine:
Application Domain: SetupWarehouse.exe
Assembly: Microsoft.TeamFoundation.Common, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: SetupWarehouse
Process Id: 2484
Thread Id: 3880
Account name: TFSSetup

Detailed Message: Create OLAP failed:The following system error occurred: No mapping between account names and security IDs was done.

So, clearly a permissions issue as I expected. I guess this is due to some issue with the user on the domain I guess I can start looking there...

Answer this question

Error 28704.Unable to connect to the Analysis server.

jerry1
After another uninstall and restarting the process with SQL 2005 Developer Edition, the upgrade succeeded! I had been installing SQL 2005 Standard, as per the installation guide.
Patrick B

Run SqlServer Management Studio and choose Analysis Service from server type combo (login form). After login, right click on analysis server/properties/security. You should see strange (GUID like) user name - that is "bare SID" user name. Remove it and thats all...
Willeem
Hi all,
I have the same problem. i don't know what is the "bare SID". can you tell me how I remove the bare SID. Thanks !
yann sugere

Hi Folks:

Well after several times trying, I think I found the major culprit. For me it turned out to be my Anti-virsus software (Norton). I suggest turning off your ant-virsus and then try to start up Analysis Services. I put this to the test. When my anti-virus software is enabled, Analysis Services will not start, but when I disable it - Wham it starts right up. If this doesn't work for you, I suggest checking your fire-wall. If on, disable it and try again.

Good luck.
amitbadgi
Alright -- I figured this one out. To fix the "No mapping between account names and security IDs", connect to Analysis Server using SQL Studio. Once in, goto the properties of the Analysis Server and goto the security section. You should see a bare SID in the NT User and Group list. Remove this and you won't have this problem anymore.

...UNFORTUNATELY, however, I now have the infamous "Error loading event web service"! Gahhh!

cevans(at)confluence.com
raviganesh91221
The "No mapping between account names and security IDs" should not have anything to do with STD vs ENT vs DEV. When I hit it, I restarted Analysis Services. We had logged a bug for SQL which couldn't be reproed. The previous post mentioning the bare SID is interesting ...
moflaherty
If you are installing onto SQL Server Standard Edition then you will get this error due to the fact that nothing cleans up the old Analysis Server's TFSWarehouse database. You can't do it inside any of the GUI managers because the Analysis Services service will not start up correctly (nice one!). BUT THERE IS A WORK-AROUND.

When this error appears on-screen do this;
1. Control Panel/Administrative Tools/Services.
2. Stop the SQL Server Analysis Services service.
3. Navigate in Explorer to the database directory where the Analysis Services databases are stored (usually C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data).
4. Delete the file TFSWarehouse.0.db.xml and the directory TFSWarehouse.0.db
5. Start the SQL Server Analysis Services service.
6. See if you can now connect to the Analysis Services in SQL Server Management Studio (Object Explorer/Connect/Analysis Services/your server name). Typically there will be no Databases listed at this point.
7. Click the Retry button on the setup screen.
This essentially eliminated the database that Team Foundation Server is going to setup anyway... so it should work fine.
si downes

Help! Help! I have been trying everything to startup the Analysis Server and keeo getting the following error:

TITLE: Connect to Server
------------------------------

Cannot connect to RBM.

------------------------------
ADDITIONAL INFORMATION:

A connection cannot be made. Ensure that the server is running. (Microsoft.AnalysisServices.AdomdClient)

------------------------------

No connection could be made because the target machine actively refused it (System)

------------------------------
BUTTONS:

OK
------------------------------

===================================

Cannot connect to RBM.

===================================

A connection cannot be made. Ensure that the server is running. (Microsoft.AnalysisServices.AdomdClient)

------------------------------
Program Location:

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.ConnectXmla()
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

===================================

No connection could be made because the target machine actively refused it (System)

------------------------------
Program Location:

at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPAddress address, Int32 port)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClientByAddress(String hostName, Int32 port)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)

Can anyone help me, Please!!! Microsoft, why is this so difficult. I tried re-installing 3 times (many, many hours) and still the same problem. Please help!!!

Thanks.
subansuba
I had the same problem, and removing the bare SID also worked for me. Thanks for the information.
bebel
I have also encountered this error while trying to install the TFS Beta 3 Refresh. This is a single server installation. TFS Beta 3 was running without any problems, and I followed the Beta 3 Refresh upgrade instructions carefully. Unfortunately, after the 28704 error appears and the TFS installation fails, all of the TFS databases are blown away! I have to restore TfsBuild, TfsIntegration, TfsVersionControl, etc. from backups.

I have attempted the upgrade 3 times, and the 28704 error appears every time. I have tried uninstalling SQL 2005, STS, .NET Framework, etc. and starting from "scratch" (using the restored TFS databases) without success. The Analysis Server service is running. Restarting the service does not help.

Any help would be appreciated.

The following Application errors are in the Event Log:

Event Type: Error
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 19
Date:  11/1/2005
Time:  8:08:30 PM
User:  N/A
Computer: ENGTFSB3
Description:
Errors in the metadata manager. An error occurred when loading the Code Churn perspective, from the file, '\\ \C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\TFSWarehouse.0.db\Team System.1.cub\Code Churn.1.persp.xml'.

--------

Event Type: Error
Event Source: MSSQLServerOLAPService
Event Category: (289)
Event ID: 19
Date:  11/1/2005
Time:  8:08:30 PM
User:  N/A
Computer: ENGTFSB3
Description:
Errors in the metadata manager. An error occurred when loading the Team System cube, from the file, '\\ \C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Data\TFSWarehouse.0.db\Team System.840.cub.xml'.

---------

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 10005
Date:  11/1/2005
Time:  8:08:58 PM
User:  FANFARE\tfssetup
Computer: ENGTFSB3
Description:
Product: Microsoft Visual Studio 2005 Team Foundation Server - ENU -- Error 28704.Unable to connect to the Analysis server. Please check that you have the necessary permissions and the Analysis Server process is running on the data tier. See the setup logs for more information.
mdon
I got around this by installing SQL Enterprise rather than Standard - but now I have other problems :{
Mehmet ECEV&#304;T
I had the error 28704 problem, then removed the bare SID in the user group list, and this worked great for me. Everything installed fine after doing this.
staelenss
Yes, I went through the same exact thing. Installed SQL Server Standard per instructions, then it wouldn't work. Went back to my snapshot and installed SQL Server developer and install worked fine.

HEY MICROSOFT - you listening Can someone please update the instructions so more poor souls don't waste hours of time
MichaelZ
During the setup process we also give permissions to the TFSService account to do 'stuff' in the DB. Just so you know.

I'm assigning this to one of the folks that handles the Warehouse pieces.

In the meantime, try stopping and restarting Analysis Services. We've seen issues where the service is running BUT it really isn't responding to API requests.

-marc [MSF]
Error 28704.Unable to connect to the Analysis server.

Answer this question