I have been able to install 'VS2008 SP1' and 'VS2008 Tools for Silverlight' on my Windows Server 2008 development machine, but I have not been able to install the MSI for 'Silverlight Toolkit July 2009'. The install fails with the following:
"The system administrator has set policies to prevent this installation"
I am a local admin on the box. I have seen something similar when try to to 32-bit MSI on a 64-bit machine. Is that the problem that I am having?
I don't think that you need to install the SL toolkit on the server. At least, we haven't had to. We're using 64-bit Windows Server 2003, and any required Silverlight DLLs, etc., just get included in our .xap file, and get downloaded by the client when it downloads that file. All the server knows is that it's got to pass the .xap file down to a client when it requests it. The only thing that any server-side process might need to know about is the System.ServiceModel.PollingDuplex.dll (if you're using duplex WCF services), but if you simply install the SL 3.0 SDK on your dev machine, and then reference that DLL from your WCF project, it'll get included with your WCF project when you roll it out to the server in question.
The only reason you'd need to install those things on the server is if you're planning to do development on the server, which I suppose you might want to, but certainly isn't normal :-).
Related
I'm trying to install an Umbraco version 8.4.0 on Windows 2016 Standard Server.
The dev machine is Windows 10 Pro on which the installation works fine.
But when I deploy to the Windows 2016 Standard Server the pages loaded do not format well - the footer, header and other compositions setup in the back-end do render.
There are no 500 server errors or Javascript errors in console. I'm clueless about whats going wrong?
Has anyone installed Umbraco v8 on windows 2016 server, are there any special considerations for installing it?
Please could someone help me, I'm really stuck on it and not sure how to go and resolve it.
We gave "Network Service" permissions to modify the website folders. That fixed it, not sure though why because Umbraco was already running without the "Network services" in the permissions. It was only the new release of the website that got affected, the previous release had no issues without Network Services having these permissions.
If anyone get stuck with something like this should check the permissions for the website folders.
When I try to deploy my artifact on IIS, I am getting the error as shown in the below screenshot. Any help will be greatly appreciated.
The "IIS Web App Management" screenshot is shown below:
The error message is pretty clear: You can't use it to install IIS on a client OS (such as Windows 10). You have to use a server OS (such as Windows Server).
There's nothing you can do about it other than to use a server OS or use an alternate tool to deploy.
Using Windows Remote Management (WinRM), connect to the host
machine(s) where IIS or SQL Server is installed, and manage the Web
application or deploy the SQL Server Database as described below:
Create a new website or update an existing website using AppCmd.exe.
Create a new application pool or update an existing application pool using AppCmd.exe.
Deploy a Web Application to the IIS Server using Web Deploy.
Deploy a SQL Server Database using DACPAC and SqlPackage.exe.
Your log mentioned the task was installing IIS, and it seemed the tasking was installing IIS on a windows client OS. You need to check your target machine to see whether it has IIS installed.
I want to migrate an exsisting Umbraco install from our developer's website into my private virtual server.
I suppose that the server configuration will be different i.e SQL server maybe different version .. ISS .. an so on ..
I wanted to understand what would you recommend as a method to migrate the install ..
I know my way around manually installing web applications (DB, IIS included).. would that be the case if so where can i find a manual on what settings are required to manually install exsisting Umbarco Website on a new server.
And most importantlly what do i need to request from my developer (i.e. files, IIS XML Config backup, SQL DB backup etc..)
There is nothing special about migrating an Umbraco setup to a new server. You'll need a copy of the entire web directory, and a backup copy of the database.
Restore the database to your SQL server, copy the web directory into a directory on your web server, change the connection strings in the web.config to use your SQL server and assuming you have met the prerequisites for running umbraco, you should be good to go.
Alternatively, If you are not sure that your server has everything it needs, you could use the 'Web Platform Installer' to install an empty 4.7.1.1 install, and then copy your developers files over the files installed by the WPI. Going the this route will make the WPI install the prerequisites if you don't have them.
Then you just modify the web.config where necessary to point it to your database server.
EDIT: If your developer has created any custom controls, you'll want to make sure you get copies of the source code for those as well, but you don't need the source to run the site.
You have a couple of options:
If you don't have Remote Desktop access to the developer's server, ask him to give you a Web Deploy package (if he doesn't have Web Deploy already installed, point him here), and install Web Deploy on your own machine. Then you can just right-click on "Web Sites" in IIS and choose "Import Package".
You could purchase Courier, a pro Umbraco add-on which allows you to do full migrations of Umbraco sites between disconnected servers. You set up a blank Umbraco installation from Codeplex, or use Web Platform Installer to get it (get v4.7, not v5, as they're incompatible with one another - v5 uses MVC), install Courier on both the developer site and your live site, and migrate document types, documents, templates, stylesheets, media, and all other necessary resources over to your new environment.
I am running into a weird problem with the installation / configuration of the BizTalk 2010 Adapter Pack. I am running BizTalk 2010 cluster on Windows Server 2008 R2, wanted to get WCF-SQL to work so I installed the 64 bit of LOB, 64-bit BizTalk Adapter Pack, 32-bit BizTalk Adapter Pack.
I was able to see the WCF-SQL adapter in the list of adapters, and created a new handler for it. Everything seemed to be working fine. However when I created a receive location that uses the WCF-SQL type, and click on Configure, I got this error:
Exception has been thrown by the target of an invocation. (mscorblib)
Additional information: Binding not found: sqlBinding
(Microsoft.Adapters.Common.Biztalk).
I double checked the machine.config for both framework and framework64, .net framework 2.0 and 4.0, they all have "sqlbindings" entries.
By the way, I had it working on one of my development box, but when I tried to set up my server and that's when I run into this problem.
Any help is appreciated!
Install in the following order:
64-bit WCF LOB Adapter SDK SP2
64-bit BizTalk Adapter Pack
32-bit BizTalk Adapter Pack
It turns out that I have been doing things not correctly. Instead of manually installing those components, go to BizTalk setup, one of the menu item is to install the adapter pack. Just follow the instruction there, and everything worked out for me.
I think the reason of this weird behaviour is maybe you have installed the wrong version of BizTalk Adapter Pack.
For BizTalk 2010, you have to install the 2010 version of the Adapter Pack, which can be found on BizTalk 2010 DVD/image.
You also have to pay attention to WCF LOB Adapter SDK version: you need the 2010 version which can be also found on the DVD/image.
The former versions of WCF LOB Adapter SDK and BizTalk Adapter Pack can be installed (nothing will stop you on that), but only works with BizTalk 2009.
Not being facetious, but have you restarted your Host Instance?
Adding a handler requires a Host Instance restart.
I built a Delphi-7 Windows Application which uses some web services. The application is built in such a way that it does not require run-time DLLs. When I deployed it on a Windows 2003 server it fails while calling the web service. It results in error "Access violation at address 00c05269. Write of address 00c05269". I believe the reasons is that it needs some package to be installed. Can anybody help me to figure that out?
TIA
Just a guess: If the client was built with D7, that runtime will AV on machines with DEP enabled. See the following link for more information:
groups.google.com/group/borland.public.delphi.webservices.soap/msg/b19f3c2681de50f4
You can disable DEP for just that client (or system-wide) on the Win 2003 machine to see if that's the issue:
technet.microsoft.com/en-us/library/cc738483(WS.10).aspx
And if it is, you can download a SOAP runtime fix from here:
http://cc.embarcadero.com/Item/24535
Cheers,
Bruneau
Some troubleshooting suggestions.
Can you browse to the web service from a web browser? If not, you have a connectivity problem.
If this works, I would build a bare bones client that consumes the web service and calls a couple of methods but doesn't read from or write to any external files.