search

albertjan / PipeToCom

Couple your Hyper-V namedpipe comport to a real one.
55 stars 21 forks source link

NP2COM Service Problem #5

Closed swklose closed 12 years ago

swklose commented 12 years ago

I am not a programmer, just an IT guy trying to get Fax Services running on a Small Business Server 2011. The SBS is running as a VM under Hyper-V. The core for Hyper-V is Windows Server 2008 R2 with a PCIE Fax Modem Installed. The Hyper-V Manager settings for the VM have COM Port 1 set with a named pipe (not sure if this is correct, but I set the computer name of VM running SBS in the named pipe).

I get the following error when I try to install the NP2COM service on the SBS VM Instance.

C:\Windows\Microsoft.NET\Framework64\v4.0.30319>installutil.exe c:\utils\np2com\np2coms.exe Microsoft (R) .NET Framework Installation utility Version 4.0.30319.1 Copyright (c) Microsoft Corporation. All rights reserved.

Exception occurred while initializing the installation: System.BadImageFormatException: Could not load file or assembly 'file:///c:\util s\np2com\np2coms.exe' or one of its dependencies. An attempt was made to load a program with an incorrect format..

Any help would be greatly appreciated!

albertjan commented 12 years ago

Hi yes thats probably because it's compiled to x86 and your system is x64. I'll make a new binary version. compiled to 64bit. I Will probably have to change a few things to get it working :)

albertjan commented 12 years ago

I've uploaded a new binary version that should work on 32 and 64bit. And I've added some logging if you delete the log4net.config file from the directory it will stop logging. Let me know if it works.

swklose commented 12 years ago

Albert,

Thanks for the quick response. I will update you as soon as I try it out.

I do think I have things backwards, and the service need to be running on the core machine, not the VM instance. Is that correct?

Thanks,

Steve Klose KITS LLC Cell: 205.427.5420

-----Original Message----- From: Albert-Jan Nijburg [mailto:reply@reply.github.com] Sent: Wednesday, November 30, 2011 3:48 AM To: Steve Klose Subject: Re: [PipeToCom] NP2COM Service Problem (#5)

I've uploaded a new binary version that should work on 32 and 64bit. And I've added some logging if you delete the log4net.config file from the directory it will stop logging. Let me know if it works.

Reply to this email directly or view it on GitHub: https://github.com/albertjan/PipeToCom/issues/5#issuecomment-2957275

albertjan commented 12 years ago

That's correct. The VM intance opens a namedpipe on the host machine and the service proxies the data from that pipe to the com port, and back.

dave518 commented 11 years ago

Was there ever a link posted to a 64 bit version? I have troubles with the viewer when clicking test, about there can't be a null field, but all of my fields have been selected or filled in. Not sure if creating the pipe will work with the service or not, and if its just the viewer.

dave518 commented 11 years ago

Nevermind, stupidness on my part. I thought it was the viewer and the service that created the named pipe and hyper-v reference it. Didn't realize you actually make it on hyper-v, and its the viewer that references it. Seems to be working good now. For those of you who might be having issues too. You have to power down the virtual machine to create the pipe. At least for me, the pipe doesn't show up in the viewer list until you actually repower that machine. Tested, program works great