Am hoping i can count on skill set of the experts in the house.
I have a BI solution developed with Microsoft Analysis Services (aka SSAS) and am trying to connect to it via qlikview, the error thrown is
Ensure SQL Server browser is running
and upon ports opened it try to connect and endless asking for user credentials without browsing the cubes.
I have tried couple of suggested solutions such as :
Firstly, the SQL Server browser is running on the said server
Secondly, have opened up the port for SSAS using a fixed port as the instance is a named instance
Also, have opened up the port on which SQL Server browser runs.
Firewall has been switched off on the said port while remote connectivity has been allowed.
Yet the error persists.
Although I can connect with the SSAS database on the local machine.
The problem does lie with trying to connect to SSAS on a remote server connection.
N.B: Am using Qlikview version 11.20, SQL server 2012 while the remote server is Windows Server 2012 R2 Standard 64 bit
Kindly be of help here please.
MB
Related
Hi we're building out some test clusters in Azure, using Developer edition of SQL Server 2016. However with no firewalls between the two nodes, both nodes in same subnet, all tcp/ip settings enabled and sa permissions on both servers we're unable to connect using SSMS (management studio), what I'm trying to understand is are there any limitations with creating AlwaysOn Availabiity groups using SQL Developer 2016? Getting the following error
Mcrosoft SQL Server, Error 5 "Access is Denied"
However I can log onto the instances on both machines locally using ssms, but not across the network.
Think it might be a limitation on the sql server edition?
Thanks and sorry if this seems a bit random :)
In order to connect to SQL server on VM from a local machine. you have to not only open 1433 port for the VM on the portal, but also do you need to set up the firewall inside of the VM machine. Make sure you have the inbound 1433 port opened as below:
I have set up an Azure Virtual Machine with a SQL Server 2016 Standard Edition image. I have installed an instance of Analysis Services Tabular on the machine and configured endpoints such that I can access it from my local machine.
I have deployed SQL Server, SSAS Multidimensional, and SSAS Tabular databases to this machine. I am able to connect to the relational databases, and when I connect to Analysis Services I either use the IP Address or DNS name, and I am able to connect to SSAS Multidimensional databases. Usually I would add the suffix \tabular to the Server name to connect to a Tabular Instance when accessing it from Excel/Tableau/other reporting tool.
However using the \tabular suffix in the Server Name I receive the error "Errors in the OLE DB provider. Could not connect to the redirector. Ensure that the SQLBrowser server is running on that server". I have checked the virtual machine, and I have that service running. I'm wondering if perhaps \tabular is not the correct syntax to connect to a tabular instance of an Azure-hosted SQL Server.
Any help or advice would be appreciated.
I would RDP to the Server and connect in SSMS to the Tabular instance. Right click on Object Explorer on the Server Node and choose Properties. Go to the General tab and change the Port property to something like 1234 so the Port will be fixed. Restart the SSAS Tabular service. Open Windows Firewall app on the VM and open ports 2382 and 1234. Then edit the Network Security Group for that VM in the Azure portal and open tcp port 2382 for SQL Browser and 1234 (or whatever port you chose) for SSAS Tabular. Now you can connect to either of the following Server names:
Servername\TABULAR
or
Servername:1234
Documentation about this can be found here.
Has anyone accomplished pushing files to a BOE server using SSIS? I am trying to develop a SQL Server 2008 SSIS package that will push report (Excel) files to our Business Objects Enterprise (BO XI 3.1) server. Via a Script Task, I am using the Business Objects .NET SDK components to authenticate and connect to the BOE Server.
I have a copy of the package deployed to a local instance of SQL Server 2008 running on my Windows XP desktop. The package executes successfully (via a SQL Agent Job) and delivers the file to the designated location on the BOE server.
When I deploy the package to our development SQL server (SQL Server 2008 on Windows Server 2008 64-bit) and attempt to execute the package via a SQL Agent job, I receive the error message "File Repository Server Input is down" when the script task attempts to "Commit" the file to the BOE server. The package is able to open a session with the BOE Server, create a new info object, but fails on the infoStore.Commit command.
I have another SSIS package that executes successfully from our development SQL server - it communicates with the BOE server and searches for user sessions. It does not communicate with the Input File Repository - that seems to be the key distinction.
I have found limited information related to this error that indicates firewalls and ports between the SQL Server and BOE server may be the cause. I have reviewed the BOE Administrator's Guide to no avail (most likely due to my lack of understanding related to firewalls and ports). Both servers are within the same subnet and neither server has the firewall turned on. The ports for the BOE CMS servers and the Input/Output File Repository servers have been set to static port ids. Our network guy indicates there should be nothing preventing communication between the servers based on firewall or port settings.
Any help would be greatly appreciated!
Have you tried all the usual 'run as 32 bit' solutions? I guess yuor SDK is a 32 bit one, not a 64 bit one.
http://www.bidn.com/blogs/ShawnHarrison/ssis/2362/ssis-basics-running-a-package-in-32-bit-mode
However the fact the the SDK works for different services implies that it runs OK in 64 bit. So if you want to troubleshoot ports, I found this link http://scn.sap.com/thread/2027785 which indicates that the BOE ports are 6400 to 6411. To check that a given port is open, you go to a DOS prompt and type
TELNET hostname port
So if your BOE server is BOESERVER then you'd try this:
TELNET BOESERVER 6400
to test port 6400. You should get a black screen to indicate it's connected.
However, again, the fact that you seem to be able to connect and operate but not commit implies there is not a port problem as you can connect, just can't commit.
Are there any logs in the BOE side to give you a better idea of the issue?
A resolution to this issue has been identified and verified. The Windows AD account used by the proxy the SQL Agent job uses to execute the SSIS package did not have sufficient privileges on the network. Our DBA gave the account local Windows administrator privileges on the SQL server and this resolved the "File Repository Server Input is down" error I was receiving.
Thanks to those who responded and gave me other ideas to investigate.
I am not able to connect to a SQL Server 2005 hosted on a Win7 virtual machine. I am new to VM, can someone help me locate the problem?
I am able to connect another SQL server which is installed on the local machine.
When you say you can't connect - that can mean a lot of things - really you need to be much more specific.
In addition to the comments and answers already here - If you're having trouble connecting to it in Sql Server Management Studio - you should open Configuration Manager on the VM itself and make sure that Shared Memory and Named Pipes are enabled (open the SQL Server Network Configuration node in the tree).
For example, SQL Server Express instances are configured by default to reject the kind of remote connection that SSMS wants to open by default.
first of all check your connection string (for reference):
http://www.connectionstrings.com/
Second you need to add an exception in the guest machine firewall or completely disable it (port 1433 is for sql tcp/ip access).
this works fine for me:
SQLConn.ConnectionString = "Network Library=DBMSSOCN; Data Source=xxx.xxx.xxx.xxx,1433;
Initial Catalog=mySQLServerDBName; User ID=myUsername;Password=myPassword"
good luck
I might be the million'th person posting about this, but others' solutions haven't helped me. I have a database on Microsoft SQL Azure. I an trying to connect to it using the Visual Studio 2010's "Connect to Database" Tool.
From my Windows 7 machine, I can connect to it very easily. But from my Windows Server 2008R2 machine i am getting the classic error -
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
All the posts around the web seem to be focussing on the problems on the server side, no one cares if the client goes rogue. :(
Thanks for the replies.
I have seen similar problems with VS2010 DB Tool and Windows Server so I would not suggest try using SSMS 2008 R2 (must be R2). Once you have download SSMS 2008 R2 and configured properly to work on Windows Server it sure will work. In most of the case you really need to open SSMS settings to get it workon on Windows Server.
Next a few points to check:
Verify that the telnet is working from your Windows Server Machine:
c:>telnet _your_sqlazure_database_name.database.windows.net 1433
Disable your real time security and the try again
Finally following the link to keep applying settings in your Windows Server and SSMS which are applicable and I am sure it will work:
http://www.mssqltips.com/sqlservertip/2340/resolving-could-not-open-a-connection-to-sql-server-errors/
One issue is that you need to connect via tcp, not named pipes (per your error message).
Are both servers behind the same firewall (e.g. the same external IP address)? The SQL Azure firewall needs to be configured to allow access from remote IP addresses.