Showing posts with label IM service. Show all posts
Showing posts with label IM service. Show all posts

Sunday, August 13, 2017

Known issue: The service returns error #1053 on start attempt

There is a possible issue with starting the service module of Bopup Communication Server that can bring error #1053 and fail to start. This issue usually occurs after installing latest Windows updates upgrading OS to recent Windows 10 or Windows 2012. In most cases the service must be re-registered in the system again that fix the problem. The information below contains steps on how to do this.

1. Access the instalation folder from a command line interface. Open Command prompt (CMD command in Start menu) under Administrative rights and navigate into installation folder of the IM server. By default the service is installed to \Program Files (x86)\Bopup Communication Server. So the command must be the following:

cd \Program Files (x86)\Bopup Communication Server

2. Unregister the service module by executing the following command:

bcssrvc /unregserver

Then ensure that Bopup Communication Server has dissappeared from Services list in Windows.

3. Register the service again by using the following command:

bcssrvc /service

Check that the Bopup Communication Server has been added to the Services list.

4. Close the command prompt window, launch the Management Console of the communication server and start the service.



Sunday, March 26, 2017

New major update of Bopup Communication Server released

Our IM server application has been updated and it's version 5.1.0 has been released. This recent update of Bopup Communication Server comes with many new additions and changes, most of useful and important are described below.

What's new in Bopup Communication Server 5.1.0:

Added localization to Russian language
This release of the communication server added Russian translation including interface of the Setup Wizard, Desktop and Program menu shortcuts and the interface of Management Console. The localization also applied the IM Client Configuration Tool. This is the most useful and important update for our Russian customers and users.

Showing data from Messaging History is speed up
Management Console improved the speed of result list update showing data in Message History views. Prior versions could take a lot of time to refresh that lists if a huge number of messages and transfer have been selected. Now it should work faster and show up to 65,535 records instead of previous 10,000.

Management Console checks and registers IM service module if it is missing
Another annoying and common issue that our customers might face with is a sudden missing of Bopup Communication Server service from Services list. This could appear during Windows update or during a upgrade of the communication server software to a new version. Now the Management Console checks that the service exists in the system and registers it if otherwise.

Saving message logs to text files
The new version activates the option to save shown instant messages and file transfers in the Message History to a text file even no data is currently selected. In this case all shown data will be saved into a file. Otherwise only selected messages and transfers will be saved.

Fixed issues with upgrade previous versions
We noticed that sometimes new version 5.x of the IM server could not update an existing version 4.x correctly and interface of the Management Console started showing bugs like some resources missing. That could appear of the communication server was initially installed to a directory that differs from default location at "\Program Files\Bopup Communication Server\" (or "\Program Files (x86)\Bopup Communication Server\" on 64-bit systems) so some newly added resources of version 5.x still copied to default location. The version 5.1.0 fixed this.


Friday, September 16, 2016

Tips & Tricks: How to fix issue if Bopup Communication Server is not started

From time to time we are reported by our customers and users that the IM service of Bopup Communication Server stopped to working. It is shown as Stopped in Management Console and cannot be started no more. At the same time the console launches normally and shows no errors on startup. Commonly a reason of this issue is simple and can be fixed quickly. See the possible resolutions below.

Trial peroid or software license has been expired

The most common reason is that 45-day trial of evaluation period of the communication server expired. If the IM server is registered version check information about the license from Help->About dialog box. It shows details on the license including the number of supported IM clients and also an expiration date. In case of expired trial the 45-day trial expired caption will be shown. Same information is shown on the right top corner of Welcome page in Management Console.

Check that the IM service is still registered in Windows services

Another problem that could suddenly occur is missing of core service of Bopup Communication Server from Services list in Windows system. Open services panel in Windows from Control Panel->Administrative tools->Services. It is also possible to open that panel directly from the console by clicking "Open Services lists" link on Welcome screen. Check that Bopup Communication Server service is shown in the list and having Automatic startup type.

If there is no such service in the list that means that it cannot be started and the server will not be operated correctly including accept connections from instant messengers. It must be registed in Windows system by the following way:

1. Open Windows Explorer and navigate to installation folder of the IM server. By default the communication server is installed to "\Program Files\Bopup Communication Server". On 64-bit versions of Windows default directory is "\Program Files (x86)\Bopup Communication Server".
2. Click Start button on Task bar in Windows and then type "run" in search box. Thex select Run to show a launch dialog box.
3. Select "bcssrvc.exe" file in previously opened Windows Explorer window and drag-n-drop it to Run dialog. A full path to the file will be shown in command line.
4. Type /service parameter in the end of the path to the service module so a full command line has been changed to

"[PATH]\bcssrvc.exe" /service

5. Click OK to launch the command. Then refresh Services list and try to start the service.

Find out what happens with the service when it brings errors

If the communication service is not started due to some troubles with SQL database server, for example, then it is possible to discover that. Open Event Log viewer in Windows from Control Panel->Administrative tools->Event viewer or click "Open Event viewer" link in Management Console to open same window. Then click Windows logs on the left to expand it and select Applications. Scroll-down to find last messages from top sent by Bopup Communication Server service.

Normally only Start and Stop events must be present, it is events #100 and #101 respectively. If there are any other warnings or errors then copy event description and send that report to Support Team or via Live Chat function on bopup.com website or directly from the console.