Error deploying database to SQL Server Analysis Server

I have developed an SSAS database using Visual Studio 2005. During
development I have been deploying the database to an SSAS server on our
network. Now I want to deploy the database to the live server that is not on
our network and I get this error:

Error 1 The project could not be deployed to the XXX.XXX.XXX.XXX server
because of the following connectivity problems : A connection cannot be
made. Ensure that the server is running. To verify or update the name of the
target server, right-click on the project in Solution Explorer, select
Project Properties, click on the Deployment tab, and then enter the name of
the server.

I changed this setting in VS to deply to the live server:
Project / Properties / Deployment / Server = [live server IP address]

The live server is SQL Server Analysis Server 2005 Standard Edition.

Am I able to deploy to remote server? If so, why am I gett that error?

Hi Craighb,
Thank you for using Microsoft MSDN Managed Newsgroup.

From your description, I understand that you could not deploy your SSAS project to your live server that is in a different network.
If I have misunderstood, please let me know.

From the issue appearances, it seemed that this issue was most likely related to network access configurations or permissions.
For network connection check, I recommend that you:
1. Run PING command to see if you can reach the server via IP address;
2. Run FIREWALL.CPL from command line and check if your Windows Firewall is enabled on your SSAS server. If so, refer to the
following steps to add the listening TCP port of your SSAS instance to the Exception List: On your SSAS server, go to the directory
C:\Progarm files\Microsoft SQL Server\90\Shared\ASConfig and open the file msmdredir.ini with notepad, find the section
"" and check which TCP port your AS instance is listening and then open your Windows Firewall via run firewall.cpl to
add the TCP port to the Exception list.

After the above two steps, run "TELNET " from command line to check if your request can reach to the
SSAS instance. If telnet request can successfully reach to the TCP port however the issue persists, it should be related to
permission issues. Then we look at the next steps.

As you mentioned that your two computers (your client computer and your SSAS server) were in different networks, I am not sure
if they were in different domains or workgroups or if they were in the different domains but with trust relationship established.
Anyway I would like to separate this issue into two network scenarios for further analysis.

Scenario 1. Two isolated networks without any trust relationship established.
================================================== ============
In this case, the network Windows authentication is based on NTLM. You need to create a same Windows user account on the
SSAS server with the same password. After than add it to the SSAS users group which name is like "SQLServer2005MSOLAPUser
$$MSSQLSERVER".
To create an OLAP database, the user must also be added manually as member to the server role administrative group. You can
first logon your SSAS with a local administrator account from SSMS, right click your SSAS instance name and then click Properties,
click Security in the properties window, click Add to add the user to the list and then click OK.


Scenario 2. Two domain networks but with trust relationship established.
================================================== =========
In this case, you can utilize Kerberos authentication and you can just directly add the client domain user account to the SSAS user
group which name is like "SQLServer2005MSOLAPUser$$MSSQLSERVER" and then add it to the server role
administrative group same as the steps in Scenario 1.

Hope this helps. If you have any other questions or concerns, please feel free to let me know.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =========
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg-at-microsoft.com.
================================================== =========
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...#notifications.

Note: The MSDN Managed Newsgroup support offering is for
non-urgent issues where an initial response from the community
or a Microsoft Support Engineer within 1 business day is acceptable.
Please note that each follow up response may take approximately
2 business days as the support professional working with you may
need further investigation to reach the most efficient resolution.
The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by
contacting Microsoft Customer Support Services (CSS) at
http://msdn.microsoft.com/subscripti...t/default.aspx.
================================================== ==========
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Charles

Thanks for your help. I went through your email and this is what happened:

1. Run PING command to see if you can reach the server via IP address;
==> I pinged the SSAS server from my dev PC and got a reply.

2. Run FIREWALL.CPL from command line and check if your Windows Firewall is
enabled on your SSAS server. If so, refer to the
following steps to add the listening TCP port of your SSAS instance to the
Exception List: On your SSAS server, go to the directory
C:\Progarm files\Microsoft SQL Server\90\Shared\ASConfig and open the file
msmdredir.ini with notepad, find the section
"" and check which TCP port your AS instance is listening and then
open your Windows Firewall via run firewall.cpl to
add the TCP port to the Exception list.

==> I RDP'd onto the SSAS server and ran FIREWALL.CPL from command line. A
message box said that Windows firewall is not running (we use another
firewall).

After the above two steps, run "TELNET " from command
line to check if your request can reach to the
SSAS instance. If telnet request can successfully reach to the TCP port
however the issue persists, it should be related to
permission issues. Then we look at the next steps.

==> From my dev PC, I have tried to Telnet the SSAS server
TelNet [SSAS IP address] 2383 - this did not connect. I tried 2383 for the
port number, because I read it is the default port for SSAS. Is that correct?
Where can I check that on my SSAS?
TelNet [SSAS IP address] 1433 - this did connect

As you mentioned that your two computers (your client computer and your SSAS
server) were in different networks, I am not sure
if they were in different domains or workgroups or if they were in the
different domains but with trust relationship established.
Anyway I would like to separate this issue into two network scenarios for
further analysis.

==> SSAS server is part of a workgroup that is completely separate from my
dev PC that is part of a domain.


Scenario 1. Two isolated networks without any trust relationship established.
================================================== ============
In this case, the network Windows authentication is based on NTLM. You need
to create a same Windows user account on the
SSAS server with the same password. After than add it to the SSAS users
group which name is like "SQLServer2005MSOLAPUser
$$MSSQLSERVER".

==> I created a user on the SSAS server with the same username and password
that I use when I develope on my dev PC
==> I added that user to the
SQLServer2005MSOLAPUser$$MSSQLSERVER group

To create an OLAP database, the user must also be added manually as member
to the server role administrative group. You can
first logon your SSAS with a local administrator account from SSMS, right
click your SSAS instance name and then click Properties,
click Security in the properties window, click Add to add the user to the
list and then click OK.

==> Added myself under the Security section of the Analysis Services
Properties box


Scenario 2. Two domain networks but with trust relationship established.
================================================== =========
In this case, you can utilize Kerberos authentication and you can just
directly add the client domain user account to the SSAS user
group which name is like "SQLServer2005MSOLAPUser$$MSSQLSERVER"
and then add it to the server role
administrative group same as the steps in Scenario 1.

==> I didn't try Scenario 2, because the SSAS server is not on a domain
network



RESULT


==> I tried deploying from Visual Studio and connecting to the SSAS server
from the SSMS on my dev PC, but neither worked

==> Does it matter that the domain that my dev PC is on is a different name
to the workgroup that the SSAS server is on?
my username and password is the same on both.

Hi Craighb,
Thank you for your response.

Now we noticed that you could not telnet to the TCP port 2383 on which you thought that your SSAS
might listen. Generally you can find what the TCP port that your SSAS instance is listening on from
the section "" from the file C:\Progarm files\Microsoft SQL Server\90\Shared\ASConfig
\msmdredir.ini.
If you could not find it, it does not matter, you can also run "netstat -nab >c:\port.log" from command
line to check what the exact TCP port is listened by the SSAS process "msmdsrv.exe". For example,
my SSAS services is running with listening on the TCP port 2383. After I run the above command, I
can find the following log item:
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:2383 0.0.0.0:0 LISTENING 5648
[msmdsrv.exe]

If your SSAS is listening on the TCP port 2383, however you could not telnet to the TCP port 2383
from your client computer, that means you could not access your SSAS service due to network
limitation. You may check your Firewall to allow remote access to the TCP port 2383. After you can
telnet to the TCP port 2383, try deploying your SSAS project to your SSAS server.

Hope this helps.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg-at-microsoft.com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

It worked!

"You may check your Firewall to allow remote access to the TCP port 2383"
That was it. I needed to open port 2383 up on the firewall.

Thanks for your help, Charles

Hi Craighb,
Thank you for your response.

I am very glad to hear that the suggestions are helpful. If you have any other questions or concerns,
please feel free to let me know. Have a nice day!

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg-at-microsoft.com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

On Jul 29, 10:25*pm, chang...@online.microsoft.com ("Charles Wang
[MSFT]") wrote:
> Hi Craighb,
> Thank you for your response.
>
> I am very glad to hear that the suggestions are helpful. If you have any other questions or concerns,
> please feel free to let me know. Have a nice day!
>
> Best regards,
> Charles Wang
> Microsoft Online Community Support
> ================================================== =======
> Delighting our customers is our #1 priority. We welcome your
> comments and suggestions about how we can improve the
> support we provide to you. Please feel free to let my manager
> know what you think of the level of service provided. You can
> send feedback directly to my manager at: msd...@microsoft.com.
> ================================================== =======
> This posting is provided "AS IS" with no warranties, and confers no rights.
> ================================================== =======


I am having trouble deploying a cube that has a source table that is
very large.. like over 18 million records. It keeps timing out.. Any
suggestion?