I'm configuring a new BizTalk 2016 install, Sql 2016 is installed on a separate server. I get the usual error re missing integration services.
So, at this point I go to Sandro's blog post to remind me what I missed: Sandro's Post
Problem is, the resolution no longer applies because the option for "Management Tools - Basic" / "Management Tools - Complete" is no longer an option, from the Sql Server 2016 Setup Wizard:
So, I go back to the 1st page of the Wizard and Notice the Option for "Install SQL Server Management Tools":
Trouble is, clicking this just attempts to navigate to a page on the web, to download SSMS v17.4. There is no internet connectivity out from this BizTalk server. So, I download from a laptop then get SSMS v17.4 installed onto the BizTalk server. I then restart the BizTalk configuration application (import my previously saved config and re-enter all the passwords!), this does not help with SSIS problem.
Does anyone know what I can install on the BizTalk application server to get around this problem?
Problem was, BizTalk config not happy with the version of SSMS had been installed. Solution was to remove v17.4 then download v16.5.3 from the following and install it: Microsoft Download
Related
I have tried to connect to a SQL Server database using the following steps:
-> Tools -> "Connect To Database"
"Add connection" gave me the server name to use:
Test connection succeeds:
But after clicking on "OK", this error pops up:
The steps you've described for connecting to the database are for the Server Explorer in the IDE -- the error dialog and message clearly indicate this. This is not related to an ASP.NET Core project. These steps can be performed w/o any solutions/projects opened in the IDE.
It's likely an issue with your installation. Try a "modify/repair" install, or a even a clean install. If the issue persists, open a ticket with the Visual Studio team. To open a ticket, from inside the IDE, at the top right corner, click the icon for sending feedback (next to the "Live Share" icon) and follow the prompts.
Please note that not being able to create a database connection in Server Explorer will NOT prevent you from coding an ASP.NET Core app that connects to that database.
So, I've solved my above error by [temporary workaround] replacing the "Microsoft.VisualStudio.Data.Providers.SqlServer" assembly with the older version of visual studio 2019, this assembly is present in "C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE".
you'll find the above assembly in the original answer(go to this below link).
Taken from : https://developercommunity.visualstudio.com/t/Could-not-find-any-resources-appropriate/1505966#T-N1506125
tried looking at other examples on this and am a bit confused. I have 2 web servers that are load balanced and a sql server box (sql 2012). my cube is created on the sql server box (i see it in management studio). when i try to access via my asp.net page i receive the above error.
now, i see the msolap110.dll in C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110 on the sql box. do i need to do something permission wise with the dll or something? do i need to install analysis services on the web server? is there a specific port or something (doubtful as sql is running fine).
connection string is as follows:
"Provider=msolap;Data Source=;Initial Catalog=AutoOLAPAW;Cube Name=SampleCube;"
going to try to force to use MSOLAP.5 but waiting on a republish from our security/deployment group.
this all works fine in dev but my (more secured/stripped down) prod/qa is where i'm seeing the issue. using iis7 on both.
If you are using ADOMD.NET then either set CopyLocal=True on that reference on your ASP.NET source code so Microsoft.AnalysisServices.AdomdClient is deployed with the web app... Or install SQL_AS_ADOMD.msi from:
https://www.microsoft.com/en-us/download/details.aspx?id=49999
If you are using OLEDB then install SQL_AS_OLEDB.msi from that same link.
If you don’t want the SQL2012 version but want the latest then install from here and use Provider=MSOLAP in the connection string (instead of a number like MSOLAP.5).
I have a BizTalk 2010 installed properly on window server 2008 R2 and SQL Server 2008 on a different server. When I create a project myself, I can deploy it to the BizTalk server fine. But when I deploy a sample project from someone else, I got this error at deployment: "Parameter name: strDBName"
When I look at my deployment tab on the property of my project, the configuration database was disabled. I am sure the connection is fine and I can get to it with the project I created. Just not the project from someone else.
It seems unreasonable to ask for sysadmin privilege and my DBA will surely not allow. Is there something I can do to deploy project not created by myself other than asking for sysadmin privilege?
You talk about disabling your config database on biztalk console, but the image provided is not biztak console. projects you open from someone will normally diable your configuration database area on biztalk project property page if the sample use a server other than yours.
I've been trying to install the new Microsoft Release Management app that has just been released to MSDN and am having issues
It consists of a server side component for TFS 2013, and a client side component for VS2013
The server side component runs through and says that it is installed fine, but then i can't seem to connect the client side part up to it
After a bit of investigation it seems that the web services site that is installed on the server side is not working properly
It is installed on a Windows 2012 box that is also running TFS 2013, SQL 2012, and SharePoint 2013
If i browse to the newly created ReleaseManagement website I get a 503 (Service Unavailable) message.
I checked out IIS and the app pool had stopped
in the application event log I could see a load of messages saying "current configuration only supports loading images for x86 processor architectures"
I thought this was possibly to do with the "Enable 32-bit Applications" option in the IIS app pool (was set to FALSE)
I changed that to true and tried the site again. This time the app pool doesn't crash, but I get ASP.NET errors stating "Could not load file or assembly 'Interop.ActiveDs' or one of its dependencies. An attempt was made to load a program with an incorrect format."
Has anyone managed to install this yet? Any ideas on what's going wrong here?
I know it's very new, but I'm struggling to find much information about the product at all
Thanks a lot
Here is a link towards some documentation regarding this problem. As pointed out in the comments, it is related to a bug caused by SharePoint: http://support.inreleasesoftware.com/entries/24794668
Interesting section:
The request failed with HTTP status 503: Service Unavailable.
This error message usually means that the InReleaseAppPool application
pool is stopped. Please ensure that it is started. If the application
pool stops after some time by itself, it might be due to a bug caused
by SharePoint 2013. Validate your problem by looking at the Event
Viewer. Confirm that your error is similar to the following:
Event Log Error Event ID 2282
The Module DLL 'C:\Program Files\Common Files\Microsoft Shared\Web
Server Extensions\15\isapi\spnativerequestmodule.dll' could not be
loaded due to a configuration problem. The current configuration only
supports loading images built for a x86 processor architecture. The
data field contains the error number. To learn more about this issue,
including how to troubleshooting this kind of processor architecture
mismatch error, see http://go.microsoft.com/fwlink/?LinkId=29349.
We can apply a quick fix using this command
appcmd.exe set config -section:system.webServer/globalModules
/[name='SPNativeRequestModule'].preCondition:integratedMode,bitness64
Or you can manually enter the preCondition entry in the
ApplicationHost.config file
More information can be found here:
http://blogs.flexnetconsult.co.uk/colinbyrne/2012/11/11/RunningA32bitApplicationAlongsideSharePoint2013Problems.aspx
FIX:
the user which you specified to run the TFS service needs "log on as a service" and "Log on as batch job" permissions. I've set that up via GPO.
This solution worked for me. I execute this command
appcmd.exe set config -section:system.webServer/globalModule/[name='SPNativeRequestModule'].preCondition:integratedMode,bitness64
in C:\Windows\System32\inetsrv and C:\Windows\System64\inetsrv.
I have installed Web Deploy 3.5 on Windows Server 2008 R2 and tried to run remote publish web application through visual studio 2012. However, I got the error - Destination Not Reachable.
I read some post and checked below and still got no luck.
Firewall was off
Both Web Management Service and Web Deployment Agent Service were restarted and running
Tried to open https://[server]:8172/msDeploy.axd in a browser and it is reachable. (Use default 8172)
Tried to use http://[server]/MsDeployAgentService and it is working with Admin username/password.
Did I miss anything? Thanks.
Maybe same issue as in https://stackoverflow.com/questions/16708021/msdeploy-wmsvc-not-working ?
It appears you have to activate the web management service first and
then install web deploy and i'd done it the other way round. I
uninstalled WebDeploy and re-installed it, restarted the server and
its working
I also met the same problem. When installing WebDeploy, do not choose classic installation, but choose complete installation.
If you messed with SSL certificates this could be one of the causes as well:
https://serverfault.com/questions/613634/could-not-connect-to-remote-computer-web-deploy-error-destination-not-reachable#answer-812712