October 16, 2012 at 10:51 am
hello
I am getting error when i am processing qube on instance . But it works fine on one instance but not on the other one.
Error is "Process failed. Trace information is still being transferred. If you do not want to wait for all of the information to arrive press Stop"
if anyone have solution please let me know so i can fix this issue.
Thanks
Hiren
October 16, 2012 at 1:08 pm
This error really describes nothing of why the process failed. Please try waiting until you get the entire trace information.
One thing to check and make sure is that the data source for the cube is valid on this instance. Check the Connection String and Impersonation Info. If the Impersonation is set to Use Service Account, make sure the account running the Analysis Services has access to the data source.
October 16, 2012 at 3:35 pm
Thanks for replaying for problem
but this what i am getting if press stop.
The connection was lost. Close all processing dialog boxes and try processing the object again. (Microsoft Visual Studio)
===================================
The connection either timed out or was lost. (Microsoft.AnalysisServices)
------------------------------
Program Location:
at Microsoft.AnalysisServices.XmlaClient.EndRequest()
at Microsoft.AnalysisServices.XmlaClient.SendExecuteAndReadResponse(Boolean skipResults, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.Execute(String command)
at Microsoft.AnalysisServices.Server.Execute(String command)
at Microsoft.AnalysisServices.ManagementDialogs.OlapProcessProgressContainer.ProcessObjects()
===================================
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. (System)
------------------------------
Program Location:
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
at Microsoft.AnalysisServices.DimeRecord.ForceRead(Stream stream, Byte[] buffer, Int32 length)
at Microsoft.AnalysisServices.DimeRecord.ReadHeader()
at Microsoft.AnalysisServices.DimeRecord..ctor(Stream stream)
at Microsoft.AnalysisServices.DimeReader.ReadRecord()
at Microsoft.AnalysisServices.TcpStream.GetResponseDataType()
===================================
An existing connection was forcibly closed by the remote host (System)
------------------------------
Program Location:
at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
October 16, 2012 at 4:03 pm
Can you run a SQL trace on the data source? It seems like your connection to the data source is getting dropped and causing the SSAS process to error out.
Is the error happening almost immediately or after it's been running for a while? Immediate most likely means the Analysis Service instance cannot connect to the data source.
October 17, 2012 at 2:27 pm
sounds to me like normal verbiage on a failed process.
What you need to do when it fails is poke around in the top window to find the actual error message because nothing you have provided is it, it's just ancilliary info that I would see regardless of what error I actually generated.
October 17, 2012 at 4:18 pm
Hello!!!
Thanks for Replying
but i am not sure
in top window where ? i am DBA and i Dont have sound knowledge about ssas ?
Thanks
October 18, 2012 at 7:53 am
When SSAS errors you will often see the error messages under the measure group or dimension (whatever has failed) that are processing at the time whether they have failed or not.
Expand all the measure groups/dimensions and look at each error message. Some of the error messages will be a generic error message as the processing has been cancelled by whatever has errored. Eventually you will find the correct error message
Clear? It is a bit of a mission and I often get my support team misinforming me due to this
Mack
October 18, 2012 at 10:04 am
Sorry, I was referring to the Process Cube window ("Process Progress") that I believe is generated no matter how you attempt to process. Bottom part is all gray, shows status which is probably Process Failed for you right now.
The "top" shows the objects and their status, you are wanting to poke around up there wherever you find those dreaded red Xs.
As you traverse you may find "Operation canceled; HY0008" which is standard on a failure and not the least bit helpful. keep digging!
Eventually you will find a real, actionable error, something like "attribute key cannot be found" or "no logon servers available". It's a big pain for all the dims and facts to look like they failed, but it is generally one failure and the others are prevented from attempting.
In the lucky case where it's Attribute Key Cannot Be Found, the query is Right There, you can copy it and run it yourself.
One thing to watch for is to process your dimensions first. Process Full is supposed to do those first, but when I'm in the weeds it is almost always helpful to blow through every dimension first so that I known that an unfound attribute key error should NOT happen.
October 19, 2012 at 4:06 pm
i have posted snapshot error i tried everything almost but it is not showing details of error.
if you any more suggestion by seeing this snapshot
That will great help to me.....
Thanks
October 19, 2012 at 4:53 pm
hpatelc (10/16/2012)
helloI am getting error when i am processing qube on instance . But it works fine on one instance but not on the other one.
Error is "Process failed. Trace information is still being transferred. If you do not want to wait for all of the information to arrive press Stop"
if anyone have solution please let me know so i can fix this issue.
Thanks
Hiren
Did you try to process all individual dimensions first and then process the whole cube at the end? Sometime it works. Manytimes, did for me.
Good Luck 🙂 .. Visit www.sqlsaga.com for more t-sql code snippets and BI related how to articles.
October 22, 2012 at 4:04 am
Going back to your first post, you say that the cube refreshes fine on one instance, but not on another instance.
If this is exactly the same cube, then the error must be related to connectivity with the database server.
In your last post, you attached a screenshot. The window that states it is waiting for trace information should eventually fill with data of varying interest. The most important thing is that, as other posters have stated, you should see which items failed and, when you expand out, why those items failed. Many items may tell you nothing useful, but there should be one item which has the answer.
you need to wait for the trace to complete though.
October 23, 2012 at 2:22 pm
Thank You all for replying answer.
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply