Hi All,
I am trying to connect to the SQL Server Analysis Services on a remote server from my local machine, using SQL Server Management Studio.
I am able to connect to the SQL Server Database engine, but while connecting to the SQL Server Analysis services I get the following error :-
"Cannot connect to <IP Address>
A Connection cannot be made. Ensure that the server is running.
(Microsoft.AnalysisServices.AdomdClient)
A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connection host has failed to respond(System)"
Things I have tried:-
- Ensured that the remote connection is enabled.
- Have SQL Server 2005 SP1 installed on the remote server.
- Tried installined SQL Server 2005 SP2 on my local machine, but same error.
I think some issue with the ports might exists, Dont have an exact idea of how to check on with the port settings.
Any kind of help will be appreciated on this.
Regards,
Sumeet:-)
We had similar problems when deploying cubes (although running Vanilla - not SP1)
We could replicate this problem by doing the following
1) Ensure all of the SQL Server Services (inc Analysis Services) are running
2) Browse a cube on your local machine
3) Rebuild this cube on your local machine
4) Check back on the remote server to see if AS is still running
If your issue is the same as ours, AS will no longer be running and there will be errors in the Application event log which read the following
"
The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File system error: Error opening file; \\?\C:\Program Files\Microsoft SQL Server\MSSQL.3\OLAP\Data\CubeTest.0.db\Data Warehouse.8.cub.xml is not a disk file or file is not accessible..
"
We found upgrading to SP2 stopped this issue
|||Hi,
Nice to see your reply.
The issue that I am actually facing is not related to the cube, since I am not able connect to the Analysis services from my local machine, so their's no chance for me to browse a cube.
Are you able to connect to the remote Analysis services using SQL Server management studio on your lcoal machine? I am not able to achieve this and getting the error here itself...
Regards,
Sumeet
|||hi
did you check the security settings of the analysis server? (right click -> properties-> security)
add 'everyone' to it and try again for testing. i believe you should put your active directory user in it
for http connectivity, the default port number of analysis services is 2383
hope this helps
|||Hi Christina,
I have checked with the security settings, and I have the active directory user added into it, also I tried adding 'everyone' to the list, but still I am getting the same error.
Regarding the port no, Can you please let me know where exactly we need to check with the port nos., since I havent made any changes to the port no of Analysis services.
Regards,
Sumeet
|||hi, i had the same problem on my local machine, where i was running sql server 2000 and sql2k service pack 3 installed. noone could browse my cubes. I read somewhere that when installing sp 3, it changes some user roles. i can give you a clue, i am not sure that it will work for you, but it worked for me:i have reinstalled Analysis services once again on another computer which was running win xp sp2. After that i installed sql2k sp 4, before, and not sql2k sp 3. This made it work
good luck
|||
Hi Vali,
I am using SQL Server 2005 on both my remote and local server, Also I have SP1 installed on both of my machines and it doesnt works.
Later on I installed SP2 on my local machine and still I am getting the same error.
Regards,
Sumeet.
|||In the SQL Server Surface Area Configuration tool the instance of Analysis Services might be set to Local Connections Only.
Can you even ping the remote machine from your local machine? Are you specifying a named instance when connecting?
|||Hi John,
I have Local and Remote Connections selected in the SQL Server Surface Area Configuration,
Also I am able to connect to the Database engine from my local machine to the Remote server using a SQL Server Authentication, but in Analysis services, theirs no option to login using SQL Server Authentication, and using Windows Authentication I am getting the above mentioned error.
Regards,
Sumeet
|||Have you resolved this issue? We are experiencing the same problem. We can connect to the Database Engine but are no longer able to connect remotely to the Analysis Services.
Thanks in advance.
Sarah Cameron - Incycle Software
|||The port setting for Analysis Service is configured in the 'msmdredir.ini' file that should be located in your '\Program Files\Microsoft SQL Server\90\Shared\ASConfig' directory. You should see a section at the bottom of the configuration settings for your specific instance with the name and the port number:
<Instances>
<Instance>
<Name>SQL2005</Name>
<Port>2194</Port>
</Instance>
</Instances>
Hi Sarah,
We actually are not yet able to find a fool proof solution for this, but found that it makes connection using the full doamin name. again this behavior is not consistent for each and every machine.
So still waiting for help..
Regards,
Sumeet
|||Thanks for the response. We were able to get our connection back yesterday evening. I think it had to do with some domain name resolution and active directory account authentication issues. The weird thing was that it was only affecting the Analysis Services and we were still able to connect to the Database Services. Sorry I can't be of more help in detailing why it is working again.
__
Sarah Cameron - Incycle Software
No comments:
Post a Comment