May 2009 - Posts
There is a great MSDN site that gathers all the information and feedbacks for the Team System 2010 and the .NET Framework 4 Beta 1 version.
You can get all the downloads, installations instructions, walkthroughs and more all in this site.
you can find the site in the following URL: http://msdn.microsoft.com/en-us/vstudio/dd582936.aspx
For all my customers that kept asking me when it will finally be here I am glad to say after all this exhausting waiting for it, it is finally here!!!
The official announcement was two days ago 18/05/2009, you can read more about the release in Brian Harry’s post here.
I can’t wait to start using the cool feature in this release and I am sure I am not alown.
I have seen a good list for the new features coming in Jeff Beehler’s Blog, you can read it here.
This is not the only resources list that was published but it gives a nice view on the new features in a serious of videos.
These videos gives a good summary of the new features that will be released in the beta version of the Team System 2010.
We have seen that our little bug was caught and documented on the last Bugs Life post, if you didn’t read that yet you can read it here.
Today I have got my verdict, Obama the Project Manager has decided to “Fix” me.
They say that it will be expansive to “fix” me but it will cost more to leave me unfixed, they say that this part of the software is not a critical part but still will be used by part of the customers and loosing there trust will cost more than the “fix” cost.
Dennis the programmer said that he don’t know if they can fix such a bug and Obama said: Yes We Can!
I tell you its not easy to be a bug, rumors say that there are companies that don’t have trained testers, and better than that are companies with no testers at all, what a life… I can only imagine such a life where you can spend all day jumping from one while loop to another drinking bits and bytes all day you can do what ever you like and they will only notice that when you get to what they call the customers.
The customer is so mean that I even heard that the project manager Obama is scared of.
But even if the customer finds you most of the time the programmers will be so busy and the cost to fix you are so high that you can live mounts if not years without anyone will bother you.
But that is not the case here.
I guess that these are my final words, they are about to fix me soon they have already decided on “Bug Fixing” stage in the project and my priority to be fixed is one (the highest priority) so this is goodbye…”
What we can learn from our bug’s testimonial?
We can see that the project manager reevaluate the bug he used the team members opinion for that and the cost to not fix the bug.
It is very important to reevaluate all the bugs before the “Bug Fixing” stage where the project manager will supply the team with a list of bugs to fix after an evaluation of all the bugs in the system, this process only can save a lot of money on fixing bugs that will not return there investment and will reduce the project’s total ROI, and will cause less revenue to the company.
Lets look at the steps of bugs management:
Step 1: The bug is found and documented in a bugs tracking tool.
Step 2: The bug is assigned with a severity by the QA team.
Step 3: The bug is being evaluated by the project manager where he checks for its ROI.
Step 4: If the bug will not be fixed than document it and move to the next bug else…
Step 5: Document the bug’s target version and assign it with a priority.
Step 6: Fix the bug in the “Fixing Bugs” stage in the project and move it to Resolve state.
Step 7: QA tests to see if the bug is fixed and close the bug, if not they Reopen the bug.
These are some guidelines on how to manage bugs, you may add your own interpretation to it.
The Details of this message are:
“Detailed Message: The pending configuration changes were not successfully added to the cube because of the following error: System.Security.Principal.IdentityNotMappedException: Some or all identity references could not be translated.
at System.Security.Principal.NTAccount.Translate(IdentityReferenceCollection sourceAccounts, Type targetType, Boolean forceSuccess)
at System.Security.Principal.NTAccount.Translate(Type targetType)
at Microsoft.TeamFoundation.Warehouse.OlapCreator.AddAccountToRole(Role role, String accountName, Boolean needToUpdate)
at Microsoft.TeamFoundation.Warehouse.OlapCreator.SetupAnalysisDatabase(Server server, String analysisDBName, String accessUser, String dataReaderAccounts)
at Microsoft.TeamFoundation.Warehouse.OlapCreator.CreateOlap(WarehouseConfig whConf, String accessUser, String dataReaderAccounts, Boolean dropDB, Boolean processCube)
So what can we do about it?
There are two actions to take in this situation:
Purpose: Removing users that are invalid or old.
Step 1: Connect to your analysis services database using Sql Server Management Studio.
Step 2: Right click on the server node.
Step 3: Select properties and look under the Security tab.
Step 4: Remove any invalid or old users.
Step 5: Browse to Databases –> TfsWarehouse –> Roles
Step 6: Double click on TfsWarehouseDataReader
Step 7: Go to the Membership tab
Step 8: Remove any invalid or old users.
In case this action doesn’t help go to Action 2.
Purpose: Rebuild the OLAP cube.
Go to this Post that I have published in the past and follow the instructions there.