Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error

New Topic Post Reply
Installation, Operations, Troubleshooting
Ultidev Team
#1 Posted : Saturday, August 20, 2011 10:50:44 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,067

Thanks: 28 times
Was thanked: 35 time(s) in 34 post(s)
Installation

  • UltiDev Web Server installer requires Administrative privileges (and Elevated access on Windows 7, Windows 8, Vista and 2008/R2).
  • Software requirements: .NET Framework 2.0 SP2 or later, and any Windows version starting with XP Service Pack 2, both 32- and 64-bit. Compared to Cassini, support of Windows 2000 and XP before SP2 is dropped. Windows 8 (on Intel CPUs) is supported. The best approach is to install all latest Windows updates before installing UWS.
  • Hardware requirements are not of much importance: we tested it from Intel Atom to Intel Core, although the more memory, the better.
  • Installation requires no parameters or changes.
  • If UWS installer finds Visual Studio 2010, 2008 or 2005, it will add itself as a redistributable component.
  • UWS creates an exception for itself in Windows software firewall settings. 3rd party software firewalls must be configured manually to let UWS accept requests.
  • Hardware firewalls may need to be configured to allow http traffic to reach UltiDev Web Server.
  • If legacy UltiDev Cassini for ASP.NET 2.0 is installed before UWS installation, Cassini replaced with UWS, but Cassini application configuration remains intact. If UWS not working out, it can be uninstalled and UltiDev Cassini can be installed back without affecting registered Cassini applications. If legacy UltiDev Cassini for ASP.NET 1.1 is installed, UWS will stop its Windows service and make its start-up type "Manual". After UWS is uninstalled, UltiDev Cassini for 1.1 Windows service may need to be restarted and its start-up setting re-set to "Automatic" manually.
  • Applications that get registered programmatically with UWS using "Port:0/find free TCP port" option will be placed on the same TCP port if the application was uninstalled and now gets re-installed/upgraded, provided that previously-used port is available.
  • UWS gets installed into "%ProgramFiles%\UltiDev\Web Server" folder.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Ultidev Team
#2 Posted : Sunday, August 21, 2011 4:15:24 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,067

Thanks: 28 times
Was thanked: 35 time(s) in 34 post(s)
Usage, Operations.

UltiDev Web Server is a freeware. It's completely free of charge, and can be used for any purpose, including bundling and redistributing it with products and services even if you charge for them.

Here's what is prohibited:

  • UWS cannot be distributed on its own without written permission from UltiDev.
  • If you redistribute UWS with your applications, UWS can be installed only using its original, UltiDev-made installer. Creating custom installers to install UWS components is not allowed.
  • After UWS has installed, its brand item (menu items, icons, file names, service name, etc.) cannot be altered or hidden by programs.

Security

Unlike UltiDev Cassini, UltiDev Web Server Pro can be used for hosting Internet-facing sites and applications. To do that be sure to register an application using UWS Explorer console with a host process "Network Service" user context.
Quote:
"Local System" account should not be used for hosting Internet-facing sites. "Local System" hosts should not be used in other environments where potential of hacking/security threats is high.
Running UWS Explorer requires administrative/elevated privileges.

Interactive Web Server, which can be used to temporarily host sites and applications for debugging and testing purposes, does not require administrative/elevated privileges. However, when UWS Interactive Server is running under administrator/elevated user account, it will listen to external IP addresses, in addition to loopback addresses used while running under non-admin/non-elevated user accounts.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Ultidev Team
#9 Posted : Sunday, August 21, 2011 4:36:51 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,067

Thanks: 28 times
Was thanked: 35 time(s) in 34 post(s)
Troubleshooting

If UWS was working and then stopped, please run UWS.Reg.Repair.exe utility located in "%ProgramFiles%\UltiDev\Web Server" folder. If that doesn't help, please use Windows Restore Point to restore your system to working state.

Bug Submission

Before you send us a problem reports, please consider the following:

  • Providing steps to reproduce the problem is everything! If you do not provide detailed steps to reproduce, it's very hard for us to understand what is failing, and although we will sympathize with your plight and feel bad about the job we've done, it won't help with fixing the problem. To provide good steps to reproduce please try to test the problem on at least two different systems and let us know whether both of them have the problem or if not, what is the difference between the two.

  • UWS has lots of diagnostic logging built in. Most important logs are Windows Event Log and "UWS.Installer.log.txt", "RegRepairTrace.txt" and "AppRegTrace.txt" files in the "%ProgramFiles%\UltiDev\Web Server" folder.

  • Also, before sending us a bug submission, please do the following if possible:

  1. Clean Windows Event Log (Application) and delete above-mentioned files.
  2. Reproduce the problem.
  3. Export Windows Event Log (Application) as an EVT(X) file.
  4. Take a snapshot (Alt+PrtScn) of the error message screen, or whatever problem manifestation is, and then paste it into MSPaint.exe and save it sa PNG.
  5. Pack all the files mentioned above into a ZIP file (better password-protected ZIP file; use 7-ZIP for that), and attach the archive to a forum post containing steps to reproduce the problem.
  6. If you used password to encrypt your ZIP file, please contact us and send us the password along with the link to the forum post.
  7. Please attach error screenshots to your forum posts - a picture is worth 1000 words.

If necessary, we may later ask you to enable additional logging by uncommenting and editing <trace> sections in XXX.exe.config files.

If you follow steps above you are likely to be pleasantly surprised how quickly the issue will be resolved.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Ultidev Team
#11 Posted : Sunday, August 21, 2011 5:00:55 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,067

Thanks: 28 times
Was thanked: 35 time(s) in 34 post(s)
UWS Brief Architecture and Component Overview

All files mentioned below are located in the "%ProgramFiles%\UltiDev\Web Server" folder, unless stated otherwise.

UWS Components and Utilities

  • UWS Explorer (UWS.Explorer.exe) is a Windows UI utility allowing end users to manage applications hosted by UWS service. UWS Explorer is a primary tool to manipulate UWS application configuration file, "UWS.Configuration.xml" file located in "%programdata%\UltiDev\WebServer". Also, UWS Explorer displays state of other components, like UWS service and UWS host processes.

  • UWS Monitoring service, (service name "UltiDev Web Server Pro", file name "UltiDev.WebServer.Monitor.exe") is similar to IIS service: it does not host applications itself, but rather monitors health and manages life cycle of external UI-less processes that do actual applications hosting. When service is shut down or restarted gracefully, it will also shut down and restart all host processes. If service crashes, the system will make several attempts to restart it. After getting restarted service will reconnect with host running processes without any impact on the uptime. "UltiDev.WebServer.Monitor.exe" can be started as a regular program for troubleshooting purposes. To run "UltiDev.WebServer.Monitor.exe" in interactive mode please stop "UltiDev Web Server Pro" windows service, uncomment <trace> section in the "UltiDev.WebServer.Monitor.exe.config" file and run "UltiDev.WebServer.Monitor.exe" as Administrator/Elevated program.

  • UWS host processes (UWS.AppHost.ClrX.XXXX.exe) are programs started by UWS service and where applications are loaded and where incoming requests are received. Host processes differ by CLR version and bitness. Host processes will exit if UWS service has not communicated with the host for some time, but normally hosts stay running in memory for very long time. When host is recycled from the UWS Explorer, a new host process gets spawned, the old one stops listening to inbound requests but finishes serving received requests, and new host starts listening to the inbound requests. Multiple host processes of the same CLR and bitness may be started under different user security accounts, to host one or more application each. Running fewer applications per host means better application stability due to their independence from misbehaving applications, but it also means higher memory usage, as .NET Framework is loaded in each process.

  • UWS Interactive Server (UWS.InteractiveServer.ClrXXXX.exe) are regular Windows programs that can be started from Windows Explorer or from a command line, and play a role of an interactive host process running in the security context of the currently logged in user. It is intended to be used for application debugging and testing purposes, and not for permanent hosting. When run by non-Admin/non-elevated user, Interactive Server can only listen to loopback IP addresses, like 127.0.0.1, [::1] and localhost. However, when started by an Administrator/Elevated user, Interactive Server can accept external requests.

  • Configuration repair utility (UWS.Reg.Repair.exe) can be used to repair UWS after it stopped working due to some external factors, like other programs and components being installed or changed. It can also be used to add UWS as an installation prerequisite component to Visual Studio and InstallShield if they were installed after UltiDev Web Server Pro.

  • Application command line registration utility (UWS.RegApp.exe) is to be used primarily by installers of applications bundled with UWS. It registers applications with UWS Service the same way they are registered manually with UWS Explorer or programmatically using .NET or COM API.

  • Application Locator/Redirector web application (Redirector folder, http://localhost:7756/) is a web application hosted by UWS that allows redirect to any application hosted by UWS, using application's ID. Application Locator determines application address and port (even for ports assigned by UWS upon application's installation) and redirects to the application. Application Locator/Redirector could be used via links like "http://JohnsDesktop:7756/GoToApplication.aspx/A90312B2-B322-48b3-8A40-34745EF11676", where the last part is application ID.

  • UWS Application Configuration API has .NET and COM interfaces. .NET API assembly can be added to Visual Studio projects by looking for UWS.Configuration assembly in the Assemblies list. COM API can used by either by adding reference to "UltiDev Web Server application configuration API for .NET and COM clients" type library, or by instantiating an object of "UltiDev.WebServer.MetabaseComServer.1" ProgId.

  • Visual Studio web server replacer utility (WebDevReplacer.exe) allows replacing and restoring default internal Visual Studio debug web server (Cassini/WebDev.WebServer) with UWS Interactive Host. Next time you hit F5 in Visual Studio, UWS Interactive Host will run.

  • Static file extension to MIME type map (UserFileExtMimeTypeMap.example.txt, SystemFileExtMimeTypeMap.txt) provide mapping of static file extensions to MIME types. The effective map is the combination of the two. Please only modify "UserFileExtMimeTypeMap.example.txt". UWS service needs to be restarted for MIME type changes to take effect. If you have added something to UserFileExtMimeTypeMap.example.txt, please let us know so we could update the MIME type map for the next release of the product.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Ultidev Team
#12 Posted : Tuesday, September 20, 2011 3:18:56 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,067

Thanks: 28 times
Was thanked: 35 time(s) in 34 post(s)
If your web application does something unexpected

If your application behaves differently in UWS compared to IIS or Cassini, here's how you can help collect necessary information for us to analyze. Having HTTP trace from Fiddler gives us tons of information about what's going on and makes it much easier for us to help you resolve the issue.

  • Install Fiddler on the same box where your client (browser) is. Fiddler is an amazing HTTP interceptor. Every web application developer should have it and use it to understand what's going on when requests come in and response are returned to the client.

  • Run Fiddler.

    1. Clean up Fiddler's left panel by hitting Ctrl+X.
    2. Run your web application (without SSL/HTTPS) and be sure that you see your application's trace in the left panel of the Fiddler. If you don't see the trace there, access your application using machine name or actual IP address, instead of localhost or 127.0.0.1.
    3. Execute failure scenario and stop Fiddler tracing by hitting F12 on the keyboard in the Fiddler.
    4. Delete all irrelevant trace items (google, hotmail, and all other non-application traces) from Fiddler's left panel.
    5. In Fiddler, please do File | Save | All Sessions | Save as type: Password-Protected SAZ.
    6. Attach your SAZ file to your problem report forum post.
    7. Contact us and send us the password to your SAZ file, along with the link to your forum post.
Ultidev Team attached the following image(s):
Ultidev Team attached the following image(s): Fiddler.png
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Ultidev Team
#14 Posted : Monday, April 9, 2012 10:18:40 PM(UTC)
Ultidev Team

Groups: Administration
Joined: 11/3/2005(UTC)
Posts: 2,067

Thanks: 28 times
Was thanked: 35 time(s) in 34 post(s)
Limitations

  • ASP.NET apps hosting WCF services with non-basicHttpBinding (like wsHttpBinding) work only in ASP.NET 4 with <serviceHostingEnvironment multipleSiteBindingsEnabled=”true”/>, but not ASP.NET 3.x. It's due to a design bug in WCF 3.x: when it's hosted in an ASP.NET application, it assumes it's either secure IIS/WAS, or unsecure Cassini/WebDev. It can't do secure and non-IIS. The error looks like "No protocol binding matches the given address 'http://machinename/WebApplication35/Service1.svc'. Protocol bindings are configured at the Site level in IIS or WAS configuration."

  • If WCF Data Services (which include WCF RIA Services) return 401 "unauthorized" HTTP result under Anonymous authentication, please set <authentication mode="None" /> in web.config.

  • Applications requiring scripts to be in "/aspnet_client" folder should not have a virtual directory other than "/". In the future UWS applications non-root, virtual directories will have access to the "/aspnet_client" folder.
Please donate at http://www.ultidev.com/products/Donate.aspx to help us improve our products.
Guest
#15 Posted : Monday, August 25, 2014 2:25:50 PM(UTC)
Groups:

Message was deleted by a Moderator.
Quick Reply Show Quick Reply
Rss Feed  Atom Feed
Users browsing this topic
Guest (2)
New Topic Post Reply
Forum Jump  
You can post new topics in this forum.
You can reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You can vote in polls in this forum.