[b]BCMS VU R2V4[/b]

[S8700Girl]

We have installed BCMS VU Server R2.4 on a computer. The program worked for a few weeks and then one day, someone tried to access the computer via the BCMS VU Client. They received a 8510 error stating that it could not access the share. When we logged into the BCMS VU Server program and viewed the sharing setup, the configuration share name and the configuration share path fields are blank. The database share name and database share path fields are fine. We have reinstalled this program 6 times on this particular computer. It works for awhile and then one day, we get either the 8510 or 8511 error. We looked up the Avaya documentation in regards to this problem, and we did what it says to do but it has not fixed the problem. I also noticed that when a client tries to access the server, it puts a separate file out on the C drive instead of in the BCMS VU folder on the C drive under program files. I talked to Avaya and they want to send me to Tier 3 to fix it but charge for it. We have 3 of these and this is the only one that is still having a problem. Has anyone experienced this problem? If so, what did you do to fix it? Our network people are stumped.

Thanks!

 

[YeOldPhoneGuy]

These are the notes I got form Avaya as to what the error may be. VuShare Errors: 8509 8510 8101 “...not accessible through the share.”

SYMPTOMS
BCMSVu R2 Client computer: User receives Error 8509 followed by Error 8510 when connecting to the BCMSVu
R2 Server computer. After clicking on the OK button provided with each error message, user can usually access the
real-time report forms with no problems. An Error 8101 is received when attempting to access historical reports.

BCMSVu R2 Server computer: The System Configuration display shows the remote client connected. The Error
Log has entries for the 8509, 8510, and possible 8101 errors related to the remote client.

SOLUTIONS
These errors were generated when user’s network login failed to access the BCMS share, called VuShare. This is
caused by a user login authentication failure (user-id or password) when the BCMS Client application attempted to access VuShare.

Check NTs User Manager utility for proper NT administration of user’s network login and password. Use one of
the following NT Administration procedures as appropriate, if the customer does not state a preference.

BCMSVuServer on NT4 Workstation or NT4 Server in a Workgroup
• Create Local User accounts for each BCMSVu Client using the NT User Manager utility.
a. Make the account name same as their network login.
b. Make the password the same as their network password.
• Create a new Local Group called BCMSVu Users using the NT User Manager utility.
a. Add the BCMSVu Client’s local user accounts to this new local group.
b. Add this new local group to the User Rights Policy: Access this computer from network

BCMSVuServer on NT4 Workstation or NT4 Server in a Microsoft Domain
• Create a new Local Group called BCMSVu Users using the NT User Manager utility.
a. Add the BCMSVu Client’s domain user account to this new local group.
b. Add this new local group to the User Rights Policy: Access this computer from network

Other situations to consider that may cause Error 8509 & 8510
• BCMSVuServer computer is in a different Workgroup than the BCMSVu Client computer.
• BCMSVuServer computer is in a Workgroup, the BCMSVu Client computer is in a Microsoft Domain.

Create a LMHOSTS file on the BCMS Client computer. The following example shows a BCMS Server computer
with a computer name of phone-nt and an IP address of 192.168.6.11.
192.168.6.11 <tab> phone-nt <tab> #PRE

The #PRE causes the IP address and computer name data to be preloaded in the name cache table with a timeout
value that never expires. After editing the LMHOSTS file, reboot the computer for the preload to take effect. Or
go to a DOS prompt and do the following.
• Type: nbtstat –R to purge and reload the name cache table.
• Type: nbtstat –c to display the contents of the name cache table.
• The BCMS Server computer name will be listed three times, each with a Life (sec) value of –1.
Example: PHONE-NT <03> UNIQUE 192.168.6.11 -1
PHONE-NT <00> UNIQUE 192.168.6.11 -1
PHONE-NT <20> UNIQUE 192.168.6.11 -1

Microsoft networking test methods to aid in troubleshooting Error 8509 & 8510
Method #1: Map a Network Drive from Windows
• Right-click Network Neighbothood, select Map Network Drive to map a drive letter to VuShare.
• In the Path box type: \\computername\vushare where computername is the netbios name of the
computer running the BCMSVuServer application.
• This usually results in a Windows Error box with a complete description of the error.

Method #2: Map a Network Drive Error from a DOS prompt within a MS-DOS Window.
• At a DOS prompt, type: net use w: \\computername\vushare where computername is the netbios
name of the computer running the BCMSVuServer application, and w: is an unmapped drive letter.
• This usually results in a text message with a complete description of the error.


Me

 

[rfarouk]

you have to keep contineous authenticatiion between the client and the server . im not so deep in how to do this with a network configuration . but i did it with mounting a folder from the server as a partition in the client . the problem stopped . also you can re- install the software after taking a backup of the data base files . i hope this could be useful for you.