Hi all,

Since last friday the warehouse will not longer process and as result of that most of the reports are frozen or show data that is out of date. In the eventlog there are always 2 error messages on the time the warehouse should be processed:

TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
...
Detailed Message: Create OLAP failed Exception Message: The following system error occurred: No mapping between account names and security IDs was done. . (type OperationException)

followed by:

TF53010: An unexpected condition has occurred in a Team Foundation component. The information contained here should be made available to your site administrative staff.
...
Detailed Message: The pending configuration changes were not successfully added to the cube because of the following error: Microsoft.AnalysisServices.OperationException: The following system error occurred: No mapping between account names and security IDs was done.

(for complete messages see below)

Has anyone a clue of what is causing this problem and, maybe more important, how to fix it?

Kind regards,
Ferdinand Kuiper

Message 1:

TF53010: 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): 26-7-2006 7:25:09
Machine: DEV-TEAM01
Application Domain: /LM/W3SVC/3/Root/Warehouse-4-127983686837343750
Assembly: Microsoft.TeamFoundation.Warehouse, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 4368
Thread Id: 4432
Account name: DEV\tfsservice

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

Exception Stack Trace: at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.Alter(IMajorObject obj, ObjectExpansion expansion, ImpactDetailCollection impact, Boolean allowCreate)
at Microsoft.AnalysisServices.Server.Update(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
at Microsoft.AnalysisServices.Server.SendUpdate(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings)
at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options)
at Microsoft.TeamFoundation.Warehouse.OlapCreator.CreateOlap(WarehouseConfig whConf, String accessUser, String dataReaderAccount, Boolean dropDB)

Message 2:

TF53010: 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): 26-7-2006 7:25:09
Machine: DEV-TEAM01
Application Domain: /LM/W3SVC/3/Root/Warehouse-4-127983686837343750
Assembly: Microsoft.TeamFoundation.Warehouse, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a; v2.0.50727
Process Details:
Process Name: w3wp
Process Id: 4368
Thread Id: 4432
Account name: DEV\tfsservice

Detailed Message: The pending configuration changes were not successfully added to the cube because of the following error: Microsoft.AnalysisServices.OperationException: The following system error occurred: No mapping between account names and security IDs was done. .

at Microsoft.AnalysisServices.AnalysisServicesClient.SendExecuteAndReadResponse(ImpactDetailCollection impacts, Boolean expectEmptyResults, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.Alter(IMajorObject obj, ObjectExpansion expansion, ImpactDetailCollection impact, Boolean allowCreate)
at Microsoft.AnalysisServices.Server.Update(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
at Microsoft.AnalysisServices.Server.SendUpdate(IMajorObject obj, UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings, ImpactDetailCollection impactResult)
at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options, UpdateMode mode, XmlaWarningCollection warnings)
at Microsoft.AnalysisServices.MajorObject.Update(UpdateOptions options)
at Microsoft.TeamFoundation.Warehouse.OlapCreator.CreateOlap(WarehouseConfig whConf, String accessUser, String dataReaderAccount, Boolean dropDB)
at Microsoft.TeamFoundation.Warehouse.AdapterScheduler.EnsureCubeIsUpToDate()

Hi Ferdinand,

I suspect that there was a failure to resolve an account to a security identifier (SID). Can you look in the event viewer and see if you see any warnings or errors from the event source "SceCli"? Are there any other strange event viewer messages that mention the mapping problem? Are the TFS service account and the TFS report account still valid? Were their usernames renamed?

Thanks,

Mauli

Hi Ferdinand,

Can you also please restart Analysis Services and see if the problem goes away? We've seen this problem in the past

Thanks

Federico

Hi Federico and Mauli,

I've rebooted the entire system (I used a single server installation for Foundation Server and SQL Server) but that didn't solve the problem.
I also checked the EventLog and found serveral information messages from 'SceCli' with the following text:

Security policy in the Group policy objects has been applied successfully.

Thanks,
Ferdinand.

Hi Ferdinand,

I remember that this was an issue in Analysis Services and that restarting the service will solve the problem but in your case that didn't work. I'll be out of the office on Monday but I'll be back on Tuesday and I will look for the Analysis Services bug that causes this to see if there is another workaround that can be applied.

Rebuilding the cube using setupwarehouse.exe wiht the -o option may solve this problem but before we try that I want to see if we can fix it in Analysis Services first.

Thanks.

Federico

Hi Frederico,

After re-reading the posts I decided to restart not the entire server, but only the Analysis Services Service as you suggested and guess what... everything seams to work again. My guess is that there is a 'sequence problem' in starting the services during a system boot that causes AS to malfunction. Is there some sort of boot sequence that we can configure to force the SQL Analysis Service as last service starting?

I guess sometimes you have to leave your problems behind, have a good night sleep, celebrate your weekend and come back on Monday morning and fix that problem you??e been working on for hours in just 5 minutes J

Kind regard,
Ferdinand.

Hi Ferdninad,

The bug is in Analysis Services and it seems it is caused when a bad user is in it's list (for instance, if a deleted local account is in the list). What you can do is connect to Analysis Services with the SQL Tools and look for that type of users in the server or the TfsWarehouse database and delete them and that should solve the problem.

Thanks.

Federico

Which 'list' do you mean ?

Do you mean the Person table ?

Hello Osiris, this issue is in Analysis Services itself and not related to the data in the Warehouse. The Person table exists in the TfsWarehouse relational database in SQL Server and it is represented in the TfsWarehouse cube database in Analysis Services as the Person dimension. The issue is not in the person dimension. The issue is in the permission list in Analysis Services itself. For instance this issue will appear if a user was added to that list and then the user was deleted.

I hope I answered your question.