June 19, 2017 at 8:10 am
All of a sudden the jobs I had scripted out backing up my tabular databases started failing with the error
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 10.0.212.129:56940
If I just backup the database from the GUI it works, anyone seen this before?
June 19, 2017 at 3:51 pm
Xmla works with IDs and names in conjunction. Script put the backup again (from the place where it works in the gui) and examine the Xmla. Does it match what you had previously scripted?
If it's not this, has there been an environmental change at all? I've seen this sort of error caused by a loopback issue.
June 20, 2017 at 6:16 am
not the issue found issue but have another problem. This is on a physical active passive cluster. WHen we fail to node 2 tabular name is dwsql01tab\dwsql01tab, on node 1 it is dwsql01tab. It is a clustered resource and all tabular databases show on each node. Of course this causes a problem with power bi with the different names
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply