Although we do not officially support an installation of Console.NET on 2003 server due to complexity of securities and policies, it can be configured to work.
Issue #1) Installation fails due to ASPNet not having user rights. Solution: Open "Add/Remove programs" and seelct Window Components. Browse to IIS and view the details of items included in installation. Be sure that "ASPNET" client is selected.
Issue#2) After installing, web page cannot be displayed 404 error. Solution: In IIS, open the "Web Service Extensions" folder. On the right side, Web Server Extensions are listed and specify whether the yare prohibited or allowed. ASP.Net and Active Server pages must be in the list and set to "Allow".
Issue#3) Permissions on the Console.NET folder and sub folders are not sufficient. Solution: - Browse to the Console.NET folder under C:\Inetpub\wwwroot\ConsoleNET - Right Click on the folder and select Sharing & Security - Select the security tab then "Advanced" button at bottom of page. -On the Permissions tab, click on the column titled "Permissions" in order to sort by Full Control - The following names must be present with Full Control: ASP.NET machine account, IIS_WPG, System. Once the above items are confirmed, click on check box at bottom of page "Replace permissions on all child objects...." and click Apply. - Updated: August 4, 2006
Question: After launching the installation, why is a message displayed stating that this product requires Microsoft Internet Information Services verion 4.0 or higher.
Answer: As stated in the Installation menu, the Microsoft Windows Component "Internet Information Services" (IIS) is a prerequisite that must be installed. Locate your Windows Operating System CD and add Windows component IIS.
Solution • Follow the support document for Installing IIS located in the “Support” folder
Question; After installing and trying to launch ConsoleNet, Internet Explorer gives the message “Page Cannot Be Found”.
Answer: Possible Reason: Internet Information Services (IIS) default web site may be stopped. Solution: • Open Control Panel/Administrative Tools • Open “Internet Information Services” or “Internet Services Manager”. • Expand the “+” sign until you see “Default Website” • Right Click on “Default Website”, if available select “Start” • Close IIS and try logging in again. ************************************************** Possible Reason: If you have a Proxy Server configured, you must use “Bypass Proxy Server for Local addresses” in Internet Explorer. Solution: • Open Internet explorer • Click on “Tools”, “Internet Options” • Select the “Connections” Tab, Select “Lan Settings” • Place a check mark in the box “Bypass proxy server for local addresses” ************************************************** Possible Reason: There may be a firewall blocking client connections to the ConsoleNet Website. Solution: • You must disable firewall on the server/client or open HTTP Port 80 ************************************************** Possible Reason: The default Website port may have been changed from port 80 to something else. Advise your IT department to change the port back to the default port 80 or redirect the login request to open Console.NET to the new port. Solution: • Open IIS (internet Information Services)from Control Panel|Administrative Tools. • Expand the tree on the left window pane until you see "Default Website". Right click on Default Website and select "Properties". Take note of the assigned port • After trying to launch Console.NET, a web page will start to open, hit "ESC" on the keyboard and change the address to reflect the new port by inserting ":xxxx" where x represents the port assigned to the default website. Example: http://localhost:xxxx/ConsoleNet/ http://{server ipaddress}:xxxx/ConsoleNet/ http://{server name}:xxxx/ConsoleNet/ ************************************************** - Updated: June 8, 2009
Question: After installing and trying to launch ConsoleNet why is a message displayed stating “Server Error in Application /Configuration error'
Answer: Possible Reason: The Virtual directory in IIS did not get created properly. This may be due to previous attempt to install and or un-install ConsoleNet. Solution: • Browse to Control Panel / Administrative Tools • Open “Internet Information Services” or “Internet Services Manager”. • Expand the “+” sign until you see “Default Website” • Under “Default Website”, right click on “ConsoleNet” and select “Properties” • Click on the “Create” button on the mid right side. Click “OK” • Close all screens and login to ConsoleNet
Question: After logging in to ConsoleNet the main window displays “Not Connected, Initializing” What is wrong?
Answer: Possible reason: ConsoleNEt login was attempted while the service is not running on the server and the website may have a hung user session preventing it from re-initializing.
Solution: From the server PC Click on Start | Run followed by typing in the word "iisreset" without the quotes and hit the key. Login to ConsoleNET, if the problem is not solved, exit ConsoleNET from the “Exit” button and continue to next solution
Solution: Open ConverTec Communication Manager from the desktop shortcut located on the server and do one of the following; >If Service(s) is/are stopped, click on the service line and select the "start" button. >If Service is "In Service", click on the "Stop" button and then after the service indicates "Stopped" click on the "Start" button. After performing one of the operations, wait approximately 1-2 minutes (BCM) or 3-5 minutes (Norstar) before attempting to login to ConsoleNET again. - Updated: June 8, 2009
Possible reason: “Login.aspx” in IIS was not configured properly during the installation. Solution: • Make sure that you can ping the server from each computer and they are all on the same subnet mask. • Browse to Control panel/Administrative Tools/ • Open Internet Service Manager (IIS). Expand the plus sign • Expand “Default Website” • Right Click on “ConsoleNet” and select “Properties” • Click on the documents tab • If “Login.aspx” is not in the window, select “Add” and type “Login.aspx” then select “OK”. Move it to the top of the list with the arrows.
A: Disable Inernet Explorer "Pop-up Blocker" and Disable Windows "Firewall Settings". The decision to disable "Pop-up Blocker" and "Firewall" should be made by your network or computer administrator. This solution is offered for the immediate use of ConsoleNET until a network administrator can configure excepions that will allow the features to remain on. ************************************************** Solution: To disable Pop-up Blocker open "Internet Explorer" - Click on Tools/ Pop-up Blocker/ Turn Off Pop-up Blocker. ************************************************** Solution: To disable windows "Firewall" Goto Start Menu/Programs/Accessories/System Tools/Security Center -Click on "Windows Firewall", select the "Off" button and save. - Updated: June 8, 2009
