June 16, 2009 at 4:14 pm
Hi All
I am having trouble getting my SQL Agent job to process a cube on SQL Svr 2008.
I can run the SQL Server Analysis Services Command as myself, but has errors when run as SQL Agent.
The SQL Agent log message is as follows:
Message
Executed as user: TECHNOT\SBSSVR$. Microsoft.AnalysisServices.Xmla.ConnectionException: A connection cannot be made. Ensure that the server is running. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:2383 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.AnalysisServices.Xmla.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) --- End of inner exception stack trace --- at Microsoft.AnalysisServices.Xmla.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) at Microsoft.AnalysisServices.Xmla.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo) at Microsoft.AnalysisServices.Xmla.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession) at Microsoft.SqlServer.Management.Smo.Olap.SoapClient.Connect() at OlapEvent(SCH_STEP* pStep, SUBSYSTEM* pSubSystem, SUBSYSTEMPARAMS* pSubSystemParams, Boolean fQueryFlag). The step failed.
SQL Agent and Analysis Services are running on the same box. I have tried to allow port 2383, and have tried turning the firewall off to see if this is the issue.
(I also have issues when I try to run a SSIS package which processes the cubes.)
Any ideas on solutions?
Thanks in advance.
Kevin
June 16, 2009 at 10:11 pm
Problem solved.
Had to play around with the service accounts. and that resolved it.
October 4, 2009 at 9:51 pm
We are facing the similar issue the cube processing succeeds when processing manually by right click the cubedb->process but throws an error when we process through dynamic xmla:
Microsoft.AnalysisServices.Xmla.ConnectionException: A connection cannot be made. Ensure that the server is running. ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:2383 at System.Net.Sockets.TcpClient..ctor(String hostname, Int32 port) at Microsoft.AnalysisServices.Xmla.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) --- End of inner exception stack trace --- at Microsoft.AnalysisServices.Xmla.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo) at Microsoft.AnalysisServices.Xmla.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo) at Microsoft.AnalysisServices.Xmla.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession) at Microsoft.AnalysisServices.Xmla.XmlaClient.Connect(String connectionString, Boolean beginSession) at Microsoft.SqlServer.Management.Smo.Olap.SoapClient.Connect() at OlapEvent(SCH_STEP* pStep, SUBSYSTEM* pSubSystem, SUBSYSTEMPARAMS* pSubSystemParams, Boolean fQueryFlag).
October 5, 2009 at 4:39 am
Run a trace on the Analysis Server to see which account is accessing the cube to perform the processing.
Ensure that account has the security clearance to process the cube in the Cube Roles
Kind Regards, Will
August 17, 2011 at 9:40 am
What did you do to fix this?
March 26, 2014 at 12:21 pm
rshepard (8/17/2011)
What did you do to fix this?
No connection could be made because the target machine actively refused it 127.0.0.1:2383
By default, BIDS / SSDT assumes that SQL Server and SSAS are running on default local instance. In my specific case, I had installed to a local named instance, so fixing the above error involved the following:
In the solution property pages, I clicked 'Configuration Properties' and changed 'Server' from 'local' to actual '<server name>\<instance name>'.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply