Melick's Blog

Normally  MDX queries are returning caption for reports when we are using data in SSRS. But  we need other information such as UniqueNumber and other when passing as parameters to other reports and datasets. Below shows example query used for get the member properties. (We can declare it using WITH MEMBER ). DayKey is the custom column we are creating with member DayKey as [Date].[Date]. currentmember . uniquename SELECT NON EMPTY { DayKey ,[Measures].[Sample], [Measures].[Sample2] } ON COLUMNS , NON EMPTY { [Date].[Year-Month-Date].[Date]. ALLMEMBERS } ON ROWS FROM [RetailigenceBI]

This error Occurred to me while I design the query in the Query Builder and generate the report in SSRS ( MDX). Months are showing alphabetical order (April , August,..) , but it should be January , February .. I did some background works and even follows the the thread http://social.msdn.microsoft.com/Forums/en/sqlreportingservices/thread/27765eda-371d-4428-ab13-2e96b2fbb6ca . But ultimately I  found there is a sorting adding by default to that column. I Deleted it .. Bingo .. It worked ..  

This error is occurring when  you are going to access the UI with another thread. There are method you can use to over come this situation. The best approach is to use method Invoker to update the UI when it is required. if (txtDataRx.InvokeRequired) { txtDataRx.Invoke( new MethodInvoker ( delegate { txtDataRx.Text = txtDataRx.Text + szData; })); } else { txtDataRx.Text = txtDataRx.Text + szData; }

I had a difficult time to get user profile service synchronization started. Following are the errors encountered to me when I tried to start the synchronization manually as well as through SharePoint. Errors Encountered Windows could not start the forefront identity manager synchronization services on local computer The system cannot find the file specified. … Windows could not start the forefront identity manager synchronization services on local computer You account is not a member if a required security group (came from Forefront Identity Manager) The Forefront Identity Manager Service cannot connect to the SQL Database Server. Windows Could not start the Forefront Identity Manager Synchronization Service on local. for more info review the system event log. If this is a non Microsoft service contact the vendor and refer the specific error code 2145185792. Workaround These are things we need to consider to make it work. First make sure you don’t give fully qualified...