Order T1 Lines New Jersey

Authorized Avaya Business Partner


 

Special
Internet Marketing Services

VoiceMail Pro Home


Phone Manager Index



Avaya Conferencing

Access Levels
Address Book
Setting up a Bridge Number
Conference Failure Route

Conference Finished Route
Conference Full Route
Configuring Manager
Configuaration Tab
Configure Conference Center
Configure VM Pro
Conf. Not Started Route
My Contacts
Database Backup
Conference Details
Email Notifications
Add Contacts to Conference
Failure Routes
Administer Web Client
Installation of Conf. Center
Installation Options
Join a Conference
Manage Profile
Overview
Participant Details
Pending Conferences
Reports

Conference Resources
Schedule New Conference
Conference Scheduler
Conference Set Up Options
Software Upgrade
Speak Capability

Conf. Template Overview
TroubleShoot
Update a Conference
User Accounts
Voting Web Conferencing
Web/ Internet Conference
Web Participant Status/ Info

Anonymous Status/ Whisper

IP Office Tek Tips

Phone System Quote









 

 

Troubleshooting

This section is intended to aid in the installation and administration of Conferencing Center should any of the following issues are encountered.   

Problem/Symptom

Suggested Solution

Running ASP.NET on a Domain Controller - By default, the worker process for Microsoft® ASP.NET (Aspnet_wp.exe) runs under the local machine account to restrict access to domain resources and provide a more secure environment. This will cause an error if you try to run or debug an ASP.NET application on a domain controller or a backup domain controller. On a domain controller, all user accounts are domain accounts and not local machine accounts, so Aspnet_wp.exe fails because it cannot find a local account named "localmachinename\ASPNET".

 

Create a "weak" account with the correct permissions:

  1. Create a user account on the computer and add this user account to the Users group.

  2. Grant this user account the Log On as a batch job right. Do the following:

    1. Click Start|Settings|ControlPanel|Administrative Tools. Double-click Local Security Policy.

    2. Within the Local Security Policy window and under Security Settings, double-click Local Policies|User Rights Assignment.

    3. In the list of policies, right-click the Log on as a batch job policy and click Security.

    4. If the new user account does not appear in the Assigned To list, click Add to add the new user account.

    5. Select the Local Policy Setting check box next to the user account name and click OK.

    6. Restart the server, if necessary.

Note: This process may need to be repeated for the Domain Controller Security and Domain Security policies.

  1. Grant the new user account write access to the \WINNT\Microsoft.NET\Framework\V1.0.XXXX\Temporary ASP.NET Files\ directory. This will allow the Aspnet_wp.exe process to write temporary files and classes to this directory. Do the following to grant write access to the necessary directory:

    1. Navigate to the \WINNT\Microsoft.NET\Framework\V1.0.XXXX\ directory in Microsoft Windows® Explorer and right-click the Temporary ASP.NET Files icon.

    2. Click Properties and then click the Security tab.

    3. Select the user account from the list and select the Allow check box for Write permissions.

    4. Click OK.

    5. Make sure that the new user account has access to all other files and directories that are necessary to serve ASP.NET pages.

  2. Grant the new user account write access to the \WINNT\TEMP\ directory. If you are running XML Web services, this will allow the Aspnet_wp.exe process to write temporary files and classes to this directory. Do the following to grant write access to the necessary directory:

    1. Navigate to the \WINNT\TEMP\ directory in Windows Explorer and right-click the TEMP icon.

    2. Click Properties and then click the Security tab.

    3. Select the user account from the list and select the Allow check box for Write permissions.

    4. Click OK.

    5. Make sure that the new user account has access to all other files and directories that are necessary to serve ASP.NET pages.

  3. Specify that the ASP.NET worker process will run under the new user account.

    1. Open the \WINNT\Microsoft.NET\Framework\V1.0.XXXX\Config\Machine.config file.

    2. In the <processModel> section, change the userName and password attributes to the name and password of the new user account. For example: userName="DomainName\ASPNETUSER" password="ASPNETUSERpassword".

    3. Save the changes to the Machine.config file.

 

Problems Accessing Web Sites - Although on the local PC http://127.0.0.1/AVECS and http://127.0.0.1/AVECSWEB both load their respective pages correctly, http://pc_name/AVECS and http://pc_name/AVECSWEB does not load.

 

Ensure that the name of the PC does not contain an underscore or any other non-standard characters prohibited from the standard PC naming conventions.  Permissible characters include: a-z, A-Z, 0-9 and hyphens (-).

Maximum Logon Attempts Exceeded - When the AVECS page is loaded, a grey error message is loaded, clicking Refresh loads the page successfully.  However, after logging in, a message stating that the maximum logon attempts have been exceeded is displayed.  

 

Check that the user ASPNET exists on the local PC. If the user does not exist, create the user by going into the Local Users and Groups setting via My Computer.

NT Authority\Network Service Error - The error displayed on the grey background refers to NTAuthority\Network Service and is followed by the Max logon attempts error.

 

Similarly, if the error states NTAuthority\Local Service, the corresponding procedure will need to be followed.

 

If this is running on a Windows 2003 Server, the following settings should be verified:

IIS Manager | Local PC Name | Application Pools | DefaultAppPool

- Select Properties.

- Select Identity and ensure Local System is set.

Emails not sent from the Conferencing Center Server: Mail is not being received correctly to either the mailbox or the Drop directory.

 

 

 

 

 

 

 

 

 

 

On machines with IIS5, mail sent from the Conferencing Center Server will collect in .../InetPub/mailroot/Drop. If a POP3 Server has been installed on the PC, it will be taken from the Drop directory and delivered to the appropriate mailbox.

 

On machines with IIS6 installed, provided the POP3 Server  has been configured (this ships by default with Windows 2003), mail from the Conferencing Center Server will be routed correctly to the mailbox.

 

It may be necessary to configure the SMTP Mail in IIS.

  1. From the Control Panel, open Internet Services Manager.

  2. Expand the tree and expand Default SMTP Virtual Server.

  3. If the domain name is not in the format X.X

    1. Right click, select  New | Domain.

    2. Select Alias and enter a name in the format X.X (e.g. PCSServer.Avaya.com).

 

AVECS Blank Page - When the AVECS web page is loaded, it is blank.  When the AVECSWEB web page is loaded, a single line of text is displayed.  

Verify that there is a .aspx extension listed in IIS Manager.  IIS Manager can be accessed by doing the following:

  1. Right click on the default web site.

  2. Select Properties.

  3. Click Home Directory.

  4. Click Configuration.  The .aspx entry should be listed there.

If not, it is likely that .NET 1.1 was installed prior to the installation of IIS.  In this case, all of the system updates required have not been carried out.  From Add/Remove Programs, remove .NET 1.1 and re-install it.  No separate steps need to be taken if .NET 1.0 is also listed, because the process for .NET 1.1 will resolve the issue.

 

1-800-429-0077 ::: Fax 1-732-751-8811
5133 West Hurley Pond Rd., Farmingdale, NJ 07727
Contact us
Copyright 2008 CarrollCommunications.com, All Rights Reserved.