pubsub Forum Rss Feed

New Post: "BadImageFormatException" when installing the x86 Setups

keithh — Mon, 29 Apr 2013 12:57:24 GMT

Like I said previously, I have never seen your behavior nor have I ever seen TIME_WAIT for any tcp connections. I think this is something you're going to have to debug. The code on codeplex should build fine for you now. Something appears to be closing the connections outside of Wsp. It could be some network router/load balancer, a security application, or something similar.

New Post: "BadImageFormatException" when installing the x86 Setups

Wheels — Mon, 29 Apr 2013 08:58:18 GMT

Hei Keihh,

First of all, thank you for looking into this. Your support is as always, fantastic.

As for the matter in hand, the problem continues. Restarted the PC and this is what I get. Connection establish, followed by some TIME_WAIT, followed by blank.

On the bright side, I just got confirmation that they are going to upgrade the 32-bit Servers to 64-bit soon. So maybe this wont be a problem by the time I have this wrapped up.

netstat -ano |findstr 1300
  TCP    172.16.20.124:1031     172.16.20.32:1300      ESTABLISHED     3512

netstat -ano |findstr 1300
  TCP    172.16.20.124:1031     172.16.20.32:1300      TIME_WAIT       0

netstat -ano |findstr 1300
  TCP    172.16.20.124:1031     172.16.20.32:1300      TIME_WAIT       0
  TCP    172.16.20.124:1032     172.16.20.32:1300      TIME_WAIT       0
  TCP    172.16.20.124:1033     172.16.20.32:1300      TIME_WAIT       0

netstat -ano |findstr 1300

New Post: "BadImageFormatException" when installing the x86 Setups

keithh — Sat, 27 Apr 2013 15:26:21 GMT

I uploaded some new x86 install files. It runs fine on my x86 home machine. Let me know if you have any issues.

New Post: Error 1001. Source WspEventRouter already exists on the local computer

keithh — Tue, 23 Apr 2013 19:33:42 GMT

When you uninstall Wsp, be sure the WspEventRouter process is not running or you can get into this situation. At this point, you need to manually delete the instances of WspEventRouter from the registry. This all seems to be the deficiency of using deployment projects to create an msi.

I'm not sure about your resource issue, this is not something I run into. When I want to debug, I either start the debug version and attach to the process, or I start the exe from VS where you give it a parameter so it runs as a normal command-line exe.

New Post: Error 1001. Source WspEventRouter already exists on the local computer

jonreis — Tue, 23 Apr 2013 18:20:50 GMT

Hello Keith,

I uninstalled the application, then tried to reinstall and I get the aforementioned error. This occurred with the latest release on Windows 7 on 2 separate computers. Any idea on how I can resolve the install error. I have tried restarting the machine, but that did not seem to help.

I'm also having trouble running this from the debugger. I get the following exception when I attempt to run the Router project:

Could not find any resources appropriate for the specified culture or the neutral culture. Make sure \"Microsoft.WebSolutionsPlatform.Router.WspEventRouter.resources\" was correctly embedded or linked into assembly \"WspEventRouter\" at compile time, or that all the satellite assemblies required are loadable and fully signed

Cheers,
Jon

New Post: "BadImageFormatException" when installing the x86 Setups

keithh — Fri, 19 Apr 2013 17:28:32 GMT

It will take me, maybe a week, to build out a 32 bit server to create and test a build on. I need to fit it in with all my other stuff.

New Post: "BadImageFormatException" when installing the x86 Setups

Wheels — Fri, 19 Apr 2013 16:50:09 GMT

I went to another colleague's laptop, this time a 64-bit machine with a 32-bit windows 7 and installed WspEventRouterx86Release as a node and had no problem establishing connection.

Running the snippet, an error occured saying it could not load Microsoft.WebSolutionsPlatform.Event.Event type.

System.TypeLoadException: Could not load type 'Microsoft.WebSolutionsPlatform.Event.Event' from assembly 'WspEvent, Version=3.0.0.0, Culture=neutral, PublicKeyToken=d8f84176f389054b'.
   at WSPEventRouterV3Subscriber.Form1.button1_Click(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnClick(EventArgs e)
   at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.ButtonBase.WndProc(Message& m)
   at System.Windows.Forms.Button.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

New Post: "BadImageFormatException" when installing the x86 Setups

Wheels — Fri, 19 Apr 2013 16:04:30 GMT

I decided to try and install WspEventRouter on a colleague's laptop since it's 64-bit and everything went fine. I even ran a little subscriber snippet and it was receiving everything my machine was publishing.

I run the same snippet on the 32-bit machine with the connection established, and I get the error on the Event Viewer:

Application: WSPEventRouterV3Subscriber.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.TypeLoadException
Stack:
   at WSPEventRouterV3Subscriber.Subscriber.Treat_SOSChangeMessage(Byte[])
   at WSPEventRouterV3Subscriber.Subscriber.SubscriptionCallback(System.Guid, Microsoft.WebSolutionsPlatform.PubSubManager.WspEvent)
   at Microsoft.WebSolutionsPlatform.PubSubManager.SubscriptionManager.CallSubscriptionCallback(System.Object)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(System.Object)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Para mais informações, consulte o 'Centro de ajuda e suporte' em http://go.microsoft.com/fwlink/events.asp.

So maybe it's a problem with the 32-bit machines?

New Post: "BadImageFormatException" when installing the x86 Setups

keithh — Fri, 19 Apr 2013 13:30:15 GMT

I've never seen your behavior before. I don't even recall seeing a TIME_WAIT state of a tcp connection. If there is a tcp connection issue, I normally see a SYN_SENT state. The normal reasons I get the connection issues are either the firewall is blocking or the network routers are configured to block unknown traffic and I have to go to the networking team to have them open port 1300 traffic. I'm not sure I can provide any help for debugging your issue.

New Post: "BadImageFormatException" when installing the x86 Setups

Wheels — Fri, 19 Apr 2013 10:28:46 GMT

Well the Node server doesnt have VS 2010 installed. Would have to setup remote debugging.

Something is happening but I dont know what. So as I said, finally I was able to establish a connection. I then stopped WspEventRouter on the Node server, re-run it and I'm no longer able to connect :S

So I restarted the machine, started the service again and got this from spamming netstat (the number after the TIME_WAIT is the PID)

netstat -ano |findstr 1300
  TCP    172.16.20.124:1040     172.16.20.32:1300      ESTABLISHED     2464

netstat -ano |findstr 1300
  TCP    172.16.20.124:1040     172.16.20.32:1300      TIME_WAIT       0

netstat -ano |findstr 1300
  TCP    172.16.20.124:1040     172.16.20.32:1300      TIME_WAIT       0

netstat -ano |findstr 1300
  TCP    172.16.20.124:1040     172.16.20.32:1300      TIME_WAIT       0

netstat -ano |findstr 1300
  TCP    172.16.20.124:1040     172.16.20.32:1300      TIME_WAIT       0
  TCP    172.16.20.124:1041     172.16.20.32:1300      TIME_WAIT       0

netstat -ano |findstr 1300
  TCP    172.16.20.124:1040     172.16.20.32:1300      TIME_WAIT       0
  TCP    172.16.20.124:1041     172.16.20.32:1300      TIME_WAIT       0

After a while, like a minute or so, netstat again comes up blank. Restarting WspEventRouter, and spamming netstat it always returns:

netstat -ano |findstr 1300
  TCP    172.16.20.124:1042     172.16.20.32:1300      TIME_WAIT       0

So, After this, restarted the node server again and voila...connection established

netstat -ano |findstr 1300
  TCP    0.0.0.0:1300           0.0.0.0:0              LISTENING       8384
  TCP    172.16.20.32:1300      172.16.20.124:1032     ESTABLISHED     8384

New Post: "BadImageFormatException" when installing the x86 Setups

keithh — Thu, 18 Apr 2013 18:26:01 GMT

If you install the debug build on the Node, you should be able to attach to the process to debug. Then if you stop and restart the Hub you should be able to have a breakpoint on the method on the Node. Does this not work for you?

New Post: "BadImageFormatException" when installing the x86 Setups

Wheels — Thu, 18 Apr 2013 17:46:29 GMT

Yea I saw that the code was diferent from 2.0.

The problem is I cant run it in debug mode because of the error System.Resources.MissingManifestResourceException

Edit: I get the Error

{"Could not find any resources appropriate for the specified culture or the neutral culture.  Make sure \"Microsoft.WebSolutionsPlatform.Router.WspEventRouter.resources\" was correctly embedded or linked into assembly \"WspEventRouter\" at compile time, or that all the satellite assemblies required are loadable and fully signed."}

at Router.cs Line 268

New Post: "BadImageFormatException" when installing the x86 Setups

keithh — Thu, 18 Apr 2013 17:36:56 GMT

If you provide an IP address, it shouldn't be trying to do a dns lookup unless IPAddress.TryParse does a dns lookup. Even if it tries a dns lookup, I would expect things to work fine unless the TryParse is failing when provided an IP address. Here is the code:

        private static Socket ConnectSocket(string server, int port)
        {
            Socket socket;
            IPHostEntry hostEntry = null;
            IPAddress addressIn = null;

            if (IPAddress.TryParse(server, out addressIn) == true)
            {
                try
                {
                    IPEndPoint ipe = new IPEndPoint(addressIn, port);

                    socket = new Socket(ipe.AddressFamily, SocketType.Stream, ProtocolType.Tcp);

                    socket.Connect(ipe);

                    if (socket.Connected)
                    {
                        return socket;
                    }
                }
                catch
                {
                    // Intentionally left empty, just loop to next.
                }
            }
            else
            {
                // Get host related information.
                hostEntry = Dns.GetHostEntry(server);

                // Loop through the AddressList to obtain the supported AddressFamily. This is to avoid
                // an exception that occurs when the host IP Address is not compatible with the address family
                // (typical in the IPv6 case).
                foreach (IPAddress address in hostEntry.AddressList)
                {
                    // Only use IPv4
                    if (address.AddressFamily == AddressFamily.InterNetworkV6)
                    {
                        continue;
                    }

                    try
                    {
                        IPEndPoint ipe = new IPEndPoint(address, port);

                        socket = new Socket(ipe.AddressFamily, SocketType.Stream, ProtocolType.Tcp);

                        socket.Connect(ipe);

                        if (socket.Connected)
                        {
                            return socket;
                        }
                    }
                    catch
                    {
                        // Intentionally left empty, just loop to next.
                    }
                }
            }

            return null;
        }

New Post: "BadImageFormatException" when installing the x86 Setups

Wheels — Thu, 18 Apr 2013 17:30:50 GMT

OMG......

Finally was able to establish a connection! The problem was skype ! it was taking the port 80 and IIS default website was stopped.

Anyhow, I need to have the HOSTS file with the entry I said on the previous post or I'll get the DSN error.

Edit: on version 2.0 WspEventRouter always had 2 connections for each server. In 3.0 there seems to be only 1 connection. Is this ok?

New Post: "BadImageFormatException" when installing the x86 Setups

Wheels — Thu, 18 Apr 2013 17:13:20 GMT

I disabled all firewalls.

When I start the Node wspevent router, I'm still getting the error: Hub entry [172.16.20.32] cannot be resolved by DNS.

I edited the Hosts file, and added a line with

172.16.20.32         rfazendeiro

and the error disappears but doing a Netstat I get the following
Hub Netstat:

netstat -an |findstr 1300
  TCP    0.0.0.0:1300           0.0.0.0:0              LISTENING

Node Netstat:

netstat -an |findstr 1300
  TCP    172.16.20.124:1037     172.16.20.32:1300      TIME_WAIT

After a while, on the node server, the netstat command comes up empty (like he wasnt able to connect so wont try anymore).

One thing tho, I was able to get one time a connection (with the Hosts file entry) and the hub indicated it as connected. I then restarted both wspevent routers and never again was able to connect.

netstat -an |findstr 1300
  TCP    172.16.20.124:1036     172.16.20.32:1300      ESTABLISHED
  TCP    172.16.20.124:1037     172.16.20.32:1300      TIME_WAIT

New Post: "BadImageFormatException" when installing the x86 Setups

keithh — Thu, 18 Apr 2013 16:58:31 GMT

The config files look correct. We have been using a mixture of IP addresses and host names for the hubs and things have been working. Did you verify the firewall isn't blocking the connection?

New Post: "BadImageFormatException" when installing the x86 Setups

Wheels — Thu, 18 Apr 2013 16:42:19 GMT

Hub Config File: (64-bit)

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <configSections>
        <section name="eventRouterSettings" type="Microsoft.WebSolutionsPlatform.Configuration.EventRouterSettings"/>
        <section name="hubRoleSettings" type="Microsoft.WebSolutionsPlatform.Configuration.HubRoleSettings"/>
        <section name="nodeRoleSettings" type="Microsoft.WebSolutionsPlatform.Configuration.HubRoleSettings"/>
        <section name="groupSettings" type="Microsoft.WebSolutionsPlatform.Configuration.GroupSettings"/>
        <section name="logSettings" type="Microsoft.WebSolutionsPlatform.Configuration.LogSettings"/>
    </configSections>

    <eventRouterSettings role="Hub" group="Version3" autoConfig="true" bootstrapUrl="http://172.16.20.32/GetConfig" mgmtGuid="DA761E42-69DD-45b0-BDE7-C500A6A0DA0E" cmdGuid="345CF9E9-F206-4572-8451-0F519C739A7E" publish="true"/>

    <hubRoleSettings>
      <subscriptionManagement refreshIncrement="3"  expirationIncrement="10"/>
        <localPublish eventQueueName="WspEventQueue" eventQueueSize="102400000" averageEventSize="10240"/>
        <outputCommunicationQueues maxQueueSize="200000000" maxTimeout="600"/>
        <thisRouter nic="" port="1300" bufferSize="1024000" timeout="5000" />
        <peerRouter numConnections="2" port="1300" bufferSize="1024000" timeout="5000" />
    </hubRoleSettings>

    <nodeRoleSettings>
      <subscriptionManagement refreshIncrement="3"  expirationIncrement="10"/>
        <localPublish eventQueueName="WspEventQueue" eventQueueSize="10240000" averageEventSize="10240"/>
        <outputCommunicationQueues maxQueueSize="200000000" maxTimeout="600"/>
        <parentRouter numConnections="1" port="1300" bufferSize="1024000" timeout="5000" />
    </nodeRoleSettings>

    <groupSettings>
      <group name="Version3">
        <hub name="172.16.20.32"/>
      </group>
    </groupSettings>

    <logSettings />

</configuration>

Node Config File: (32-bit)

<?xml version="1.0" encoding="utf-8" ?>
<configuration>
    <configSections>
        <section name="eventRouterSettings" type="Microsoft.WebSolutionsPlatform.Configuration.EventRouterSettings"/>
        <section name="hubRoleSettings" type="Microsoft.WebSolutionsPlatform.Configuration.HubRoleSettings"/>
        <section name="nodeRoleSettings" type="Microsoft.WebSolutionsPlatform.Configuration.HubRoleSettings"/>
        <section name="groupSettings" type="Microsoft.WebSolutionsPlatform.Configuration.GroupSettings"/>
        <section name="logSettings" type="Microsoft.WebSolutionsPlatform.Configuration.LogSettings"/>
    </configSections>

    <eventRouterSettings role="Node" group="Version3" autoConfig="true" bootstrapUrl="http://172.16.20.32/GetConfig" mgmtGuid="DA761E42-69DD-45b0-BDE7-C500A6A0DA0E" cmdGuid="345CF9E9-F206-4572-8451-0F519C739A7E" publish="false"/>

    <hubRoleSettings>
        <subscriptionManagement refreshIncrement="3"  expirationIncrement="10"/>
        <localPublish eventQueueName="WspEventQueue" eventQueueSize="102400000" averageEventSize="10240"/>
        <outputCommunicationQueues maxQueueSize="200000000" maxTimeout="600"/>
        <thisRouter nic="" port="1300" bufferSize="1024000" timeout="5000" />
        <peerRouter numConnections="2" port="1300" bufferSize="1024000" timeout="5000" />
    </hubRoleSettings>

    <nodeRoleSettings>
        <subscriptionManagement refreshIncrement="3"  expirationIncrement="10"/>
        <localPublish eventQueueName="WspEventQueue" eventQueueSize="10240000" averageEventSize="10240"/>
        <outputCommunicationQueues maxQueueSize="200000000" maxTimeout="600"/>
        <parentRouter numConnections="1" port="1300" bufferSize="1024000" timeout="5000" />
    </nodeRoleSettings>

    <groupSettings>
        <group name="Version3">
            <hub name="172.16.20.32"/>
        </group>
    </groupSettings>

    <logSettings />

</configuration>

New Post: "BadImageFormatException" when installing the x86 Setups

keithh — Thu, 18 Apr 2013 16:23:26 GMT

IP addresses should work fine with v3.0. Send me the config file from each server.

New Post: "BadImageFormatException" when installing the x86 Setups

Wheels — Thu, 18 Apr 2013 15:11:48 GMT

So i changed the code, recompiled and I'm getting the same errors as before:

On the 64-bit machine I'm getting the System.Resources.MissingManifestResourceException and on the 32-bit machine the Error 1001. Exception occurred while initializing the installation: System.BadImageFormatException.

I changed the LaunchConditions to .Net Framework 4.0 but I get the errors above (I said previously that changing the LauchConditions worked but it could be that I installed your version instead of mine by mistake).

Edit: For the 32-bit machine, I change the LauchConditions to .NET Framework 4 Client Profile and it installed but now I'm getting the same Error as the 64-bit machine System.Resources.MissingManifestResourceException

New Post: "BadImageFormatException" when installing the x86 Setups

Wheels — Thu, 18 Apr 2013 14:43:37 GMT

I just remembered having the same issue with 2.0. At the time I changed the code to use GetHostAddresses instead of GetHostEntry. I'll go and change it