Hi,

I installed my web application with cassini on multiple computers.
On some of them it works just fine.
But on some computers the application does not work. There were no errors during installation, but the application did not start.

I looked in Application event log and found the following error:
(I noticed that in this case there is no Cassini Web Server Explorer installed on clients).

Once again - it happened only on some computers, not all of them.

Here is the error from the event log:



Event Type: Error

Event Source: MsiInstaller

Event Category: None

Event ID: 11001

Date: 1/21/2008

Time: 4:29:06 PM

User: ENT\a0866714

Computer: LTA0866714

Description:

The description for Event ID ( 11001 ) in Source ( MsiInstaller ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Product: UltiDev Cassini Web Server Explorer -- Error 1001. Cassini Explorer Ex:

System.TypeInitializationException: The type initializer for "System.Net.IPAddress" threw an exception. ---> System.TypeInitializationException: The type initializer for "System.Net.Sockets.Socket" threw an exception. ---> System.Net.Sockets.SocketException: An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full

at System.Net.Sockets.Socket.InitializeSockets()

at System.Net.Sockets.Socket..cctor()

--- End of inner exception stack trace ---

at System.Net.Sockets.Socket.InitializeSockets()

at System.Net.IPAddress..cctor()

--- End of inner exception stack trace ---

at CassiniConfiguration.Metabase.IsPortFree(Int32 port)

at CassiniConfiguration.Metabase.CanUsePort(Int32 port)

at CassiniConfiguration.Metabase.RegisterApplication(ApplicationEntry appEntry, Boolean autoSave)

at CassiniExplorer.Installer.RegisterCassiniConfigApp()

at CassiniExplorer.Installer.Install(IDictionary stateSaver) --> The type initializer for "System.Net.IPAddress" threw an exception. --> The type initializer for "System.Net.Sockets.Socket" threw an exception. --> An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full, (NULL), (NULL), (NULL).

Data:

0000: 7b 34 30 32 34 37 41 41 {40247AA

0008: 43 2d 41 42 30 44 2d 34 C-AB0D-4

0010: 34 39 43 2d 38 38 32 46 49C-882F

0018: 2d 39 30 34 30 31 43 33 -90401C3

0020: 33 35 31 45 38 7d 351E8}

Hi there.

Here's what can lead to the problem. When your application gets upgraded, app's uninstaller usually unregisters the application, which tells UltiDev Cassini server to unload the app and release the IP port the app was bound to. The problem you've reported may be caused by one of two possibilities.

1. Attempting to register an application on the port that is already taken by another. This may happen if you run upgrade installation of your application, and uninstaller failed to unregister the previous version of application. To verify if this is the case, go to http://locahost:7756/ to see which applications are registered. If you see two instances of your application is being registered there on the same port, please let us know - we will help you straighten out your custom installer steps.

2. Sometime, even when app registration steps are written properly, this problem pops up on slow machines: either on old, low-memory boxes, or on virtual machines under MS Virtual Server and VmWare Server. As far as we can tell, this is the timing issue: when Cassini applications configuration changes, Cassini unloads all applications and releases IP ports, and then loads new configuration and proceeds to loading applications. The problem is that sometimes, even though applications are unloaded, IP port does not get released quick enough for the following re-loading of apps to grab the same port again. If this problem occurs rarely, then the workaround could be as simple as rebooting the machine where server runs. If this is impossible for any reason, another workaround would be to stop the Cassini service programmatically before registering the application, and the restarting it again. This can be done either using ServiceController class from .NET Framework, or by using net stop, net start command line. If you decide to go this route, please let us know - we'll provide more information on how to do this all.

Best regards,
UltiDev Team.

Hi there!

If you have UltiDev Cassini Web Server installed, you can point your browser to http://localhost:7756/ to access UltiDev Cassini Explorer showing all applications registered with UltiDev Cassini, including port information for each application. This way, if desired port is taken by another ASP.NET application running under UltiDev Cassini, you will be able to see which application that is. If the port in question is taken by some other process, you would need to use other means to find out who is using the port.

Please let us know if this information was helpful.

Best regards,
UltiDev Team.