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
After clicking to install something from the main menu, there is a brief delay before a language choice window opens. If you don't wait and click the button to install a second time, the main window will hide the Language Choice installation.
Solution: Hit the Escape key on your keyboard to see the Language Choice menu and begin the installation. - Updated: February 4, 2005
You must first install the "Norstar Prerequisites" before you install Console.NET Solution: Restart the installation of Console.NET and select "Norstar Prerequisites" from the menu choices. Install both CTE and CTA then reboot computer and restart the installation of Console.NET. - Updated: February 14, 2006
Possible reason: In order for ConsoleNet to properly install, special security settings must be applied to the ConsoleNet folder. If you were not logged on to your computer as “Local Machine ADMINISTRATOR”, the security setting may not be applied properly. Being logged in to a Domain or as a “User” with “Administrative rights” is not sufficient. Solution: • Log in with the name “Administrator” and if there is a choice, choose “Local Machine” instead of a user on a Domain. You may require an Administrator password from your Network Administrator. • Proceed to install ConsoleNet. ************************************************** Possible reason: If you are installing on a Windows Operating System other than the English language, manual security settings may be required. Solution: • Browse to InetPub/ wwwroot, right click on ConsoleNet folder and select “Properties”. • Select the “Security” tab. • Under “Group or User names” look for “Everyone”. If it is not there, click “Add” and type the name “everyone” in the box and hit “OK” *NOTE*: You must type the name “Everyone” as spelled in the language of your Operating System. For example; Everyone in French is “Tout le mond” • Select all check boxes under “Allow” • Apply settings. ************************************************** Possible reason: You may be trying to activate a License that is no longer valid. You may be trying to activate a License that was downloaded as a 30 day trial that has expired. You may be trying to re-install a license after installing a new OS or computer. Solution: • A new License is required for product that is installed on a new computer or a computer that has significant changes such as a new Operating system. Contact sales@convertecinc.com ************************************************** Possible Reason: If you are upgrading Console.NET from versions below 2.1.0, the old license will not work, a new license is required. Solution: • Call or e-mail sales@convertecinc.com to obtain a new valid License **************************************************
Possible Reason: The Norstar CTA drivers have not installed properly. Soultion • If the drivers are installed, uninstall saying yes to remove all shared files, reboot and re-install from the Installation main menu “Norstar Prerequisites”
• If the drivers are not installed, install them from the ConsoleNet Installation main menu “Norstar Prerequisites”
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 port 80 & 9000. Port 9000 is only important if you are monitoring remote phone systems. ************************************************** 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: March 14, 2007
Possible Reason: Internet Information Services (IIS) was not installed prior to Microsoft Framework.Net. Solution: • Make sure that IIS is installed. • Go to “Add/Remove Programs” and remove “Microsoft Framework.Net” • Go to “Add/Remove Programs” and remove “ConsoleNet” • Re-install ConsoleNet following the instructions carefully. *Note* When you re-install ConsoleNet, Framework will be installed again. This is OK since it is now in the proper order. ************************************************** Possible Reason: You were not logged in as Local machine Administrator during the installation. Solution: • Remove and re-install ConsoleNet as “Local Machine Administrator” **************************************************
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 ************************************************** Possible reason: You may have attempted to install a new version or a patch without being logged in as administrator. Without being local Administrator, some security rights are not properly set in the Console.NET folder. Solution: • Browse to InetPub/wwwroot/ • Right Click on the “Console.NET” folder • Select “Properties” • Click on the ‘Security” Tab • Make sure that the “Group or User Name” box contains the name “Everyone”. If “Everyone” is not there, click the “Add” button and type the name “Everyone” and select “Ok” to all prompts. • Once created, make sure that all “Permissions for Everyone” are set to “Allow”
Possible reason: A component of our software called “PBX Service” is either not installed or not functioning properly. Solution: • Open “Control Panel / Administrative Tools / Services”. • Scroll to “PBX Service”, right click and select “Start” • If “PBX Service” is not there, un-install ConsoleNet, reboot and run the ConsoleNet installation again. When prompted to install “PBX Server” click“Yes”. ************************************************** Possible reason: You may have altered the default IP address when configuring the Server. Solution: • Click on “Config” button • Select Server/ Configuration • The TCP Address should be: 127.0.0.1 and the port should be 9000. The only time this would change is if you are adding a second switch to monitor at another location running “Remote PBX Server” ************************************************** Possible reason: (BCM only) A firewall setting on the network or server is blocking port communication of Lan CTE. Solution: • Consult your network administrator to check that access to port 80 and 9000 are open. ************************************************** Possible reason: The connection to your phones switch via CTA or Lan CTE has failed. Solution: • If your system is Norstar, verify that the Nortel CTA (Computer Telephony Adapter) is powered and that the serial cable is attached. If so, reboot computer and check status again. If it still fails to Connect, the Norstar Phone system may require rebooting. • If your system is a BCM, check that you can ping the IP address of your BCM from the ConsoleNet server computer (computer administrator may be required). If the network is ok, reboot the ConsoleNet server computer. If that fails, uninstall and re-install Lan CTE client and verify that the correct IP address is used. As a last resort, reboot the BCM. **************************************************
Possible reason: This is normal and can be from 30 sec to 5 minutes depending on the amount of telephones being monitored. If the display does not change to “Connected, Ready” ConsoleNet and the Phone System are unable to communicate for some reason. Solution: (For Norstar Phone Systems) • Verify that CTA (Computer Telephony Adapter) device is connected to the Computer ConsoleNet is installed on via Serial cable. Verify that the RED power LED is lit. Verify that the CTA is connected to a functional Norstar Phone jack. • Verify that “Add/Remove Programs” contains “Nortel CTE Toolkit” & “Nortel CTA Driver. If either of these two drivers is missing, run the installation again and select “Norstar Prerequisites” from the main menu to install them. • Reboot the computer. ************************************************** Solution: BCM (For Business Communication Manager) • Verify that “Nortel LAN CTE Client” has been installed on the Computer that ConsoleNet software is installed on. Control Panel / Add / Remove Programs/ • Verify that the BCM has a Lan CTE license enabled and available. If you are familiar with the BCM Unified Manager, login to Config. Go to Services/ Lan CTE Configuration. Select the licensing tab and view desktop licenses available compared to active. Contact your Phone System dealer if you require assistance. • Verify that you can “PING” the BCM Published IP Address from the computer that ConsoleNet is installed on. • If necessary, uninstall LAN CTE and re-install to verify that you have entered the correct Published IP address of the BCM. • If all the above is confirmed, you may require a “SOFT BOOT” on the BCM. **Warning** during a soft boot, you will be without Voice Mail and Call Center for about 10-15 minutes
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.
Possible reason: Your network security settings are blocking traffic on port 2000. Solution: • Ask your network administrator to open port 2000 or manually send the “Product ID” to support @convertecinc.com. We can e-mail you back the License file.
Possible reason: The shortcut for a link to open internet explorer is an unrecognized format Solution: • You can open Internet Explorer and type the following http://localhost/ConsoleNET/Login.aspx. Now create a shortcut for this in your favorites or links.
Possible reason: The CTE (Norstar) or LanCTE (BCM) is not properly installed. Solution: • Reboot the computer and try the installation again. • Norstar customers should re-install the CTE toolkit from the CD under Norstar Prerequisites. After installation reboot the computer. • BCM customers should download & re-install the Lan CTE client from the BCM. Reboot after install.
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: September 10, 2004
