Archive

Posts Tagged ‘Windows’

Docker for Windows start-up error

September 25th, 2016 1 comment

After installing Docker for Windows I was unable to run it, following error appeared.

elmore_blog_docker_windows_powershell01

Unable to create: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The specified module 'Hyper-V' was not loaded because no valid module file was found in any module directory.
at <ScriptBlock>, <No file>: line 76
 at Docker.Backend.HyperV.RunScript(String action, Dictionary`2 parameters)
 at Docker.Backend.ContainerEngine.Linux.Start(Settings settings)
 at Docker.Core.Pipe.NamedPipeServer.<>c__DisplayClass8_0.<Register>b__0(Object[] parameters)
 at Docker.Core.Pipe.NamedPipeServer.RunAction(String action, Object[] parameters)</pre>

I checked that Hyper-V was installed but it seems that Docker also needs to have the Powershell tools installed. So activate the feature and Docker will run fine 🙂

elmore_blog_docker_windows_powershell02

IIS 8.5 Boncode Tomcat Connector

March 4th, 2016 No comments

This guide assumes you have already installed Tomcat Server 7/8. Tomcat offers a connector (mod_jk) but it’s very old and requires a lot of configuration. So I’ll explain how to install and configure the connector from Boncode that’s hosted on RiaForge. This specific example was for an installation of HP Service Manager running on Windows 2012 / IIS 8.5

Installation

Download the latest version from http://tomcatiis.riaforge.org
Extract the .zip-file to a temp folder (AJP13_v1026.zip)

Windows2012_IIS8.5_Tomcat_riaforge_connector_01

Run “dotnetfx35setup.exe” if .NET 3.5 is not yet installed on the server.

Execute “Connector_Setup.exe”

Windows2012_IIS8.5_Tomcat_riaforge_connector_02

Windows2012_IIS8.5_Tomcat_riaforge_connector_03

Windows2012_IIS8.5_Tomcat_riaforge_connector_04

Windows2012_IIS8.5_Tomcat_riaforge_connector_05

Windows2012_IIS8.5_Tomcat_riaforge_connector_06

Windows2012_IIS8.5_Tomcat_riaforge_connector_07

Windows2012_IIS8.5_Tomcat_riaforge_connector_08

Windows2012_IIS8.5_Tomcat_riaforge_connector_09

Windows2012_IIS8.5_Tomcat_riaforge_connector_10

Windows2012_IIS8.5_Tomcat_riaforge_connector_11

Windows2012_IIS8.5_Tomcat_riaforge_connector_12

Windows2012_IIS8.5_Tomcat_riaforge_connector_13

Configuration

The installer has copied the binaries and configuration file to “C:\Windows”

Windows2012_IIS8.5_Tomcat_riaforge_connector_20

Open the file “BonCodeAJP13.settings” and modify the content as below. Feel free to change the path to LogFiles.

<Settings>
  <Port>8009</Port>
  <Server>localhost</Server>   
  <MaxConnections>200</MaxConnections>
  <LogLevel>1</LogLevel>  
  <FlushThreshold>0</FlushThreshold>
  <EnableRemoteAdmin>False</EnableRemoteAdmin>
  <LogDir>E:\LogFiles\APPLogs\BoncodeAJP</LogDir>
  <EnableHTTPStatusCodes>True</EnableHTTPStatusCodes>
</Settings>

Make sure the IIS Application Pool user has write access on the LogDir folder!
A folder named “BIN” has been created in the root of your website. It will be empty so copy these 2 files in it:

  • C:\Windows\BonCodeAJP13.dll
  • C:\Windows\BonCodeIIS.dll

Windows2012_IIS8.5_Tomcat_riaforge_connector_21

Now we need to tell IIS which folders we want to forward to Tomcat. For HPSM this will be “smsso”. Create a new folder in the root of the website named “smsso”

Windows2012_IIS8.5_Tomcat_riaforge_connector_22

Copy the “BIN” folder in “smsso”

Windows2012_IIS8.5_Tomcat_riaforge_connector_23 Windows2012_IIS8.5_Tomcat_riaforge_connector_24

Now add a handler mapping in IIS. Go to the subfolder named “smsso” and add a new managed handler.

Click on image for full version

Click on image for full version

Request path: *
Type: [select BonCodeIIS…. from the dropdown]
Name: BonCodeAll

Click on image for full size

Click on image for full size

Run “iisreset” to reload the settings file

Categories: IIS Tags: , , , , , ,

Access server locally using alias name failes (archive)

August 11th, 2010 1 comment

Error message when you try to access a server locally by using its FQDN or its CNAME alias after you install Windows Server 2003 Service Pack 1: “Access denied” or “No network provider accepted the given network path.

\<servername><sharename>

In this scenario, you experience one of the following symptoms:
• You receive repeated logon windows.
• You receive an “Access denied” error message.
• You receive a “No network provider accepted the given network path” error message.
• Event ID 537 is logged in the Security event log.

P.S.: archive post Dec 1st, 2006
Read more…

Categories: Windows Tags: