As a preface, I have done some checking around on this issue but found nothing that solves my question. This question was the closest I found but the answer did not resolve my issue.
Information about configuration: My local machine is Windows 7 with Visual Studio 2012 Update 3 and SSDT-BI installed. On the server machine I have SQL Server 2012 Developer Edition installed on Windows Server 2012 Standard. The data is coming from a third party database installed on a CentOS5 server.
I am trying to deploy a cube to my Analysis Services server, but I am getting the following error: "A connection cannot be made to redirector. Ensure that 'SQL Browser' service is running."
I have checked and the SQL Browser service is running both on my local machine and the server machine. As well, rather than connecting via < Server Name >\< Instance Name > I have tried connecting with IPAddress:Port.
I'm not sure if this is relevant, but in case it is: the database I am using to define the cube I'm trying to deploy is on a different server and has different authentication than my SQL Server 2012 Instance. Moving the data to the SQL Server is not an option.
To FrankPl: just to chime in, you answered my question a few hours ago which is essentially the same problem: VS2012 Pro with SSDT-BI installed, also Update-3 and the Aug.2013 update to AS. We're unable to connect and/or open a project.
Related
I am working on sharepoint 2013 ,while working on Performance Point Service when i amd connecting to a new Analysis source in Dashboard Designer ,it is not loading databases.
I have googled the problem and found the in my EventLogs it appears
"The data source provider for data sources of type 'ADOMD.NET' is not registered. Please contact an administrator.PerformancePoint Services error code 10115."
I downloaded and installed latest version of ADOMD.NET but it didnt worked.Please Help
If you are using SQL Server 2012 or newer, and SharePoint Server 2013, it will try to load the SQL Server 2008 version of the ADMD.NET dll.
Try to install the SQL Server 2008 R2 ADMD.NET component from here: http://www.microsoft.com/en-us/download/details.aspx?id=16978 and restart IIS.
I'm having troubles enabling remote debugging on sharepoint online. I have 2 machines, my local machine (Windows 8.1) and my development server(Windows Server 2008 R2). On my development server I first tried remote debugging using Visual Studio 2012 Update 4, as described here: http://azure.microsoft.com/en-us/documentation/articles/web-sites-dotnet-troubleshoot-visual-studio/#remotedebug.
When this didn't work I tried doing exactly the same thing on my local machine, which has Visual Studio 2013 (Ultimate) update 1 and the latest windows azure sdk (2.3). This worked perfectly. Thinking upgrading to visual studio 2013 would solve my problem I've installed 2013 (Premium) on my dev server, next to 2010 and 2012. After installing and updating everything for 2 hours however, I came to the conclusion that I received the same error as on VS 2012.
Googling came up with a few interesting causes for this bug: sitenames longer than 20 characters or sitenames containing hyphens. This is not the case. Then I verified port settings, the dev server has no active firewall but I wanted to exclude any possibilities. And low and behold, both telnetting from my local machine as my dev server to ports 4016 and 4018 of my azurewebsites.net url worked.
Are there any other solutions for this bug? Since debugging locally is not an option (sharepoint provider hosted app for project online) this is very inconvenient.
Thanks,
UPDATE: Deploying the site as a cloud service works, and so does remote debugging them. However, we would like to stay with azure web sites for now..
I know this is a duplicate of Azure Remote Debugging: Failed to enable remote debuggingException from HRESULT: 0x89710023; but none of the solutions there or on twitter were of any use.
Check out Azure Remote Debugging: Failed to enable remote debuggingException from HRESULT: 0x89710023
I think this has to do with blocked ports 4016 and 4018
I installed VS2012, SSME 2012 with localdb, and I discovered that I have 2 servers that I can connect to: (localDB)\v11.0 and (localDB)\Projects.
Which of them do I have to use for execising, what are them both for?
I know I am bit late. But I am facing the same question now and found the answer. Thought I should share the Answer:
(localdb)\Projects is the SQL Server Express LocalDB instance which is used by SQL Server Data Tools by default to host the sandbox databases created for your database projects (*.sqlproj) to enable F5 deployment and debugging.
(localdb)\v11.0 is the generic SQL Server Express LocalDb instance which gets created when LocalDB is installed, and this is also used by other Visual Studio projects like the ASP.NET projects.
See http://msdn.microsoft.com/en-us/library/hh510202.aspx for more information on LocalDB
Update
Starting from EntityFramework 5.0, the default sql server is the your localdb\vxx.x instance now.
This explains the difference and some issues to watch out for
http://aeronaught.wordpress.com/2012/11/22/vs2012-localdb-v11-1-v11-0-automatic-instance-horror/
Not sure on the difference but you should be using
(localdb)\v11.0
Environment: 64 bit Windows 8
Platform: Visual Studio 2012, SQL server 2012, IIS8
Language: C#
I'm currently creating an asp.net web application using a tutorial from msdn. The site runs fine and is visible in google chrome when I select the run button. I published the website to a folder on my desktop and am attempting to host it through IIS. The main issue I am having is trying to figure out the full computer name so I can update my connection strings in the web.cong.
The connection string is as follows:
connectionString="Data Source=(LocalDb\v11.0);"
When I try to browse the website in IIS I get a database error because I'm not defining the full machine name in the datasource attribute. I'm in a workgroup and am not on a domain. Also I can't log into sql server with just my ip address. I can only log into sql server with (LocalDb)\v11.0.
Can anyone help me find a way to determine what the value of my data source should be so I can possibly hit the website externally? Has anyone run into this problem on a home pc without a domain? I have done this on my work computer many times but have never tried to host anything from IIS on my home computer.
I've been struggling for some time now to be able to use the built-in functions in Visual Studio 2008 to handle *.mdf database files with SQL Server 2008 Express. I'm running on an x64-based system, and I've read that there is a known problem with this setup, but the hotfix has not solved my problems.
Basically, what happens is that when I try to add a new *.mdf file to the App_Data folder of a project, I get an error message saying:
Connections to SQL Server files (*.mdf) require SQL Server Express 2005 to
function properly. Please verify the installation of the component or download
from the URL: http://go.microsoft.com/fwlink/?LinkId=49251
My (unsuccessful) steps to solve this:
Uninstall all possible associated programs to Visual Studio, SQL Server or .NET Framework (which left .NET 2.0 Compact Framework and .NET 3.5 Compact Framework, and nothing else .NET related, installed).
Reboot.
Install .NET 3.5 SP1, SQL Server 2008 Express and SQL Server Management Studio 2008 Express via the Web Platform Installer 2.0 (Beta).
Reboot.
Install Visual Studio 2008 Professional from disc.
Reboot.
Install Visual Studio 2008 Service Pack 1.
Reboot.
Install hotfix.
Reboot.
Start VS, create new Web site and try to add database. Still get the error message...
When I look in the Help/About dialog, the hotfix shows up among applied updates. I have also checked and double-checked that the SQL Server instance name is correctly set in Visual Studio (I copy-pasted the instance name from the login screen in SSMS).
Why does the hotfix not solve my problems? Am I doing things in the wrong order, or do I have the wrong software versions somewhere?
According to the KB article, the problem is that Visual Studio doesn't correctly detect "some registry keys" - but nothing is said about which keys. Does anyone know how to fix this manually?
Oh, and yes - I've seen this post. I know I could just "downgrade" to the x86 version of SQL Server, but I really want to make this work with the x64 version (if nothing else, just because it's supposed to work...), so that solution doesn't really solve my problems. Please don't close this as a duplicate.
I had this same error, VS 2008 SP 1 on Vista Ultimate 64 bit with SQL 2008 Express 64 bit. Downloaded the hotfix and rebooted, started up SQLEXPRESS and still got the error.
Then I changed my "SQL Server Instance Name" (under VS 2008 -> Tools -> Options -> Data Connections), which was blank, to "SQLEXPRESS" (versus ".\SQLEXPRESS", which is what I use in my login screen under SSMS.) and now it works like a charm!
Dave
Try changing the user on which the SQL Server Express is running. This can be changed in Services managment (press Win+R, type in services.msc). Choose SQL Server Express, right click -> Properties. 'Log On' tab and select: 'Local System account', tick the 'Allow service to interact with desktop' - this is what worked for me.
I'm not sure I ever solved this, but I've now moved over to Visual Studio 2010 (RC at the moment, but I'll get the full version when it's availabel) and everything works seemlessly.