Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Wallboards / IP view application keeps “sticking” 1

Status
Not open for further replies.

Firebird Scrambler

Systems Engineer
Apr 7, 2003
7,199
GB
One of my customers has had a fault develop over the last weekend whereby the Wallboards / IP view application keeps “sticking” and not refreshing. They have rebooted the BCM 400 v4 and RCC Server etc. The customer has also updated the IP view software version on the Agent computers as there was a mismatch.

He has checked the "ping" replies to the RCC server in case it was a delay in the network. It's a little strange.

It's fairly up to date with patching System = 028 and Desktop is one release behind the latest issue.

Has anyone come across this one before?.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
it's can be ip configuration on lan network with BCM and Rcc server
 
SOmebody statically assigned the same ip address as the host PC?
 
Hello Guys. It's now beginning to look as if System patch 028 was the cause as this patch did install last weekend. I've since found out that any sites with RCC will have problems and I don't recommend anyone to update to 028. Previously the site had 027 for over 6 weeks without any problems. The latest Desktop 017 was applied OK a few weeks ago, so it can't have been anything else!.

System 028 is fine for non RCC BCM systems, so please be careful!.

We may have to reimage the whole BCM as the patch 028 is non removeable.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
Sorry for the late reply, but this problem has been interesting for my colleague who was on site.

I visited another of the customer,s BCM sites and checked the current patching level. I could see that System patch 028 WAS going to be applied, but got deleted. It was never installed!.

To make matters worse, my colleague had installed Element Manager on the same RCC to access the BCM system and he could only see old patches installed such as System 024 etc. It was only when he connected using his own laptop to the same BCM via LAN2 that he could see the latest System 028 etc!.

I decided last week to load in System 028 via the customer's network on the Element Manager that I was using and I had scheduled it for last Monday morning.

The patch was applied and no problems reported except for the continuning slow IP View and Wallboards etc.

Please read my colleague's next course of action as we now know it to all be down to the customer's RCC.

I think he has done a very useful guide?.

Hi all

After numerous attempts to get this working I am glad to say that it all up and working ok at present.

A few bits of information regarding this.

It looks like when the uninstall of files from the folders i.e. Nortel and SQL were removed some of the information tended to stay in the computers registry so every time an install was attempted there were conflicts with this which was a difficult issue to pinpoint.

When I loaded BCM Element Manager from the BCM onto the RCC server I could open it and see different information via this one from when I connected directly via the BCM. The information when I connected directly to the BCM was accurate as opposed to that on the RCC. I was using the same version of Element Manager on both the RCC server and the BCM along with the same version of Java. This was confusing to start with but was eventually what led me to think there was an issue on the RCC server itself and not the BCM.

The BCM is currently patched up-to-date with the latest service update, the latest desktop patch and the RCC/Ipview are running the latest versions also.

All information was loaded onto the RCC server i.e. the users, settings etc manually, but as the PC was old and very slow to download and run anything took ages. The database was still downloading when. I left site and only on 46% after 2 hours, this will take several hours via this pc.

The Ipview needs to be removed from each of the users pcs and re-installed with the latest version, this I have not done

The old RCC server needs to have the hard drive formatted and then rebuilt if it is to be used as an RCC server again,. I would recommend another newer pc be used as the RCC server and reloaded on again as the current working one is not really up to scratch and very slow, I can see issues with this if it is not replaced in the near future.

When removing RCC to do a FULL install there are a few things that should be done.

Automatic updates should be manually disabled and left in this state.

Login and disconnect from the network, stop print spooler services, stop RCC launcher.

Uninstall – Java
Uninstall – Ipview
Uninstall – RCC
Uninstall – SQL server 2005 (this will also uninstall MYSQL4 and the database)
Uninstall – BCM Monitor if present
Uninstall – BCM Element Manager if present

No files or folders should be deleted until the uninstall programs have been run, completed, and a reboot of the pc done.

Re-boot

Empty Internet temporary files and Internet offline files, no need to delete cookies or browsing history. after this any folders/files can be deleted.

Reboot while connected to the network then check the services are up ok, print spooler should be disabled while installing RCC, check all files/folders have been deleted again.

If possible and the network allows a registry cleaner may be advisable. Preferably any Antivirus, Firewalls should be disabled while downloading and installing RCC.

If loading onto a new pc ensure correct I.P. address is set on the server and that IIS components are installed.

Download RCC (preferably save into a folder created on the RCC server) and install from here, SQL server should also install and numerous reboots will be required.

RCC install verifier runs and will ask you to reboot or continue while going through the install of SQL server, Files, Database. Java, Reporting, BCM settings etc .

When RCC server is fully loaded and if needed the final reboot has taken place the database will download from the BCM and this can take a long time.

While database is downloading you can check RCC settings, IP addresses, skill sets, ports etc and if Ok then add the users etc.

Download Ipview (preferably save into a folder created on the RCC server) install from here, this can be run while the database is downloading.

When installed ensure IPview is set to echo.

Enable Antivirus and Firewall if applicable.

If all ok and database has fully downloaded reboot for the last time.

Check services and restart print spooler if it did not auto start, check RCC launcher and MYSQL4 have started.

When you are happy all is working OK the final thing is to go round each PC that uses IPview and uninstall it and reinstall it with the latest version.


I hope that you will find this to be useful?.

All the best

Firebird Scrambler
Meridian 1 / Succession and BCM / Norstar Programmer in the UK

If it's working, then leave it alone!.
 
I used to support and specialise in RCC (before the layoffs).

Few things:
1) Review the wallboard configuration on the RCC server itself and ensure all PING test successfully. The RCC application will only respond in a timely manner if it doesn't have to deal with lots of wallboards which are configured however not working. Remove any ones that do not repond and are definately not required.
2) To help further isoloate, run the wallboard locally on the RCC server itself - does this show a fault? Also do the real time displays update correctly (the wallboards are based on the real time displays, so the question is do the real time displays show the delay too).
3) To help further isolate, review the wbdrv.log on the RCC server, you should see regular sends to the wallboards, including the IP addresses/host names. Do you? use wordpad to open the log file.
4) Do NOT enable echo on wallboards. All wallboards should be driven from the RCC server itself, where system limits allow. If a wallboard is echo'd - the RCC server maintains no logging information, so will be impossible to troubleshoot. The only way of analysing an echo'd wallboard is via a lan capture, so don't use them.
5) Ensure the latest voicemail patch/system update has been applied already, as well as the corresponding RCC version.

Good Luck.

regards
paul
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top