Showing posts with label database. Show all posts
Showing posts with label database. Show all posts

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 /unregserver parameter in the end of the path to the service module so a full command line has been changed to

"[PATH]\bcssrvc.exe" /unregserver

This will unregister the service from the system.

5. 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 website or directly from the console.

Wednesday, August 24, 2016

Known issue: An attempt to create a backup file gives SQL error #5

Many our users faced with an error on creation of a backup file from SQL database maintenance... dialog in Management Console. Once destination folder has been selected the console brings "Cannot open backup device. Operating System error 5" and no backup file is created.

This is a known issue of the IM server application but it does not relate to any error. Since backup files are created by Microsoft SQL Server directly then an account under which database service is running may not have appropriate write permission to chosen folder. Usually this error can occur when a target directory that has been chosen to save a backup file is located in current user's profile folder such as "My Documents", "Desktop", etc. In case of the error try to choose another location to create and save backup file.

We also updated and appended with this information our FAQ section available on the website that contains details on how to Create and restore backups of Bopup Communication Server.

Thursday, November 26, 2015

The IM server fixed issues with sending messages from command line

New version 4.4.2 of Bopup Communication Server has been released and is available for download. This is a minor update of the product that fixed errors with sending instant messages from command line interface using BCSCMD.EXE module of the communication server. Previously it brought errors related to SQL Server on Windows XP and 2003 systems.

Version 4.4.2 also includes the latest release of Setup.ini Configuration Tool that supports the option to show date of messages in client conversations.

Download Bopup Communication Server version 4.4.2 — Enterprise-level IM server for office and business use

Friday, June 20, 2014

The IM server improves the install of built-in MS SQL Server 2008

We released new update of the communication server that would be important to our new customers. Version 4.3.6 improves installation of built-in MS SQL Server 2008 R2 Express that is intended for install on latest versions of Windows including 8, 8.1 and 2012. We noticed that some users experienced issues and installation errors of the built-in SQL Server so we took some time to figure out what happened with it and fixed the setup.

Download Bopup Communication Server version 4.3.6

Tuesday, October 8, 2013

"User is typing message..." event is now supported!

We glad to inform our customers that new versions of Bopup IM suite are now available for download. Both the come with major versions because we did a lot of work, added useful improvements and fixed many issues. See what is new below.

User typing event
Firstly we need to say about very useful function. Maybe it is known from public messenger when users can see in their conversations that another one is currently typing a message or reply. Year, this adds interactivity interactivity and improves usability. When we see that the reply is being typed we do not close chat window immediately. And now our software provides that support too!

Download and update both the server and client parts in order to be able to use this function. The "User is typing message..." event appears every time in a conversation dialog of Bopup Messenger client. Delivery of this instant notification event is controlled on Bopup Communication Server and you can disable it from the Options dialog box by switching to Messaging tab.

Displaying a huge amount of messages on the server history
Management Console of the communication server fixes issues with showing a great number of messages and file transfers selected from a Message History. That issue also related to displaying some profile pages for account, group and/or news messages. Now data is displayed quickly and with no error even you select thousands records.

Fixed installation of the IM server with built-in SQL Server
Another important issue was installation of Bopup Communication Server with it's built-in database server on latest versions of Windows. Sometimes the setup fails to complete because no connection to the SQL Server could be established. That was a security problem because Windows requires a stronger password for built-in 'sa' account for Microsoft SQL Server 2005 Express that shipped with the IM server package. We did that.

Forget about duplicate versions of the messenger software in Add/Remove Programs panel 
Our customers that distribute and deploy new updates of the IM client using the communication server faced with the problem that previous version of the software might not be properly removed from Add/Remove Programs if the update was initiated under non-administrator user account in Windows. That was too old problem that we know about. Now the messenger software removes it's previous version during an upgrade with keeping all settings and message history.

Adding File Transfers to a messenger local history
Both Bopup Messenger and Bopup Observer clients fix error with adding and saving received and sent transfers to Message History. Now al file transfers are properly archived for a future review.

Download Bopup Communication Server version 4.2, Bopup Messenger 6.3 and Bopup Observer 5.3

Monday, January 28, 2013

IM Server improves a restore of SQL backups and printing Message History

New version 4.1.4 of Bopup Communication Server has been released on January 27, 2013. It is a not mandatory update but it fixes and improves some useful features of the software.

What's new:

Added new option in the SQL Database Maintenance dialog to restore database backups created on another server

The SQL Database Maintenance dialog of the Management Console adds a new check box that says the console that a SQL database backup (that is intended for restore) was created on another SQL Server and/or another instance of the communication server. It is very important because in that case the backup will be restored with WITH REPLACE option.

Added UAC verification to control status of the IM service

Now the Management Console checks token of administrator account (UAC) under which it is running in Windows Vista and later. If there is no necessary rights to control the IM service from the Welcome page then appropriate message is shown and starting/stopping options for the service are unavailable. In order to control the service the Management Console must be launched with "Run as administrator" option selected from context menu in Windows.

Improved showing and printing Message History containing long messages

New version of Bopup Communication Server fixes issues with displaying and printing long text messages in Message History. We removed scrollbars in the edit boxes that contain the message text and now each conversation is shown and moved to a printing device in whole.

Download Bopup Communication Server version 4.1.4

Friday, April 13, 2012

Microsoft SQL Server 2012 is fully supported by Bopup Communication Server

We glad to inform our users and partners that the setup of Bopup Communication Server has been tested on Microsoft SQL Server 2012 Express edition. Since that is the latest version of the SQL Server software from Microsoft then it is important to ensure that the server is fully supported by our IM server. The setup went fine with no issues.

We also updated our Step-by-Step Guide to Install Microsoft SQL Server 2005/2008/2012 Express Edition as a Host Database Server for Bopup Communication Server and added SQL Server 2012 to the list of supported versions. The download links for SQL Server 2005 and 2008 were also changed and now point to Microsoft SQL Server 2005 SP4 and Microsoft SQL Server 2008 SP3 setup packages.

Sunday, November 13, 2011

Minor updates of the instant messenger software are available

New versions of Bopup Messenger and Bopup Observer IM clients have been released which fix small issues with Message History interface. These updates resolve errors with saving text messages into local history db containg a single quote (') sign. Now all messages can be properly saved into the Message History and displayed from it with no issues.

Download Bopup Messenger version 6.0.1 and Bopup Observer version 5.0.1

Wednesday, November 9, 2011

Minor update of Bopup Communication Server. It's version 4.0.1 released.

A new small update of Bopup IM Server software is available for download.

New version 4.0.1 fixes issues that are affected to new users of the . Thus some bugs were resolved in the Setup Wizard of the communication server which does not open a link to our Guide on installing MS SQL Server 2005/2008 Express Edition instead of built-in MSDE 2000 software. Another important error in the installation was incorrect name of the SQL database written into system registry. If the setup package without MSDE 2000 software was used (bcserver.msi setup file) then that problem affects to all users that tried to set up the communication server version 4.0.0 using an existing SQL server.

Download Bopup Communication Server version 4.0.1

Friday, December 3, 2010

Guide on installing MS SQL Server 2005 has been updated and appended

Our Step-by-Step Guide to Install Microsoft SQL Server 2005 Express Edition as a Host Database Server for Bopup Communication Server that is available on our websites has been updated. This guide helps to install and setup MS SQL Server 2005 Express Edition on a computer in order to use it as a database server. Since MSDE 2000 software (shipped with the setup package of Bopup Communication Server) is not supported by latest versions of Windows then you cannot install and use it on Windows 2008/Vista/7 operational systems and higher. In order to run Bopup Communication Server on these systems you should install MS SQL Server 2005 Express Edition first.

This guide has been appended with information about SQL Server Browser service. This service, part of the SQL Server 2005, should be started if you plan to connect and manage the IM server remotely. It is also required if the communication server is installed on another computer, i.e. if both the SQL Server and Bopup Communication Server are running on different workstations.

Below is the information that has been added to the guide.

You need to configure a little SQL Server 2005 after it's installation will complete. You should enable TCP/IP protocol for it, start the SQL Server Browser service and add the SQL service to Windows Firewall exceptions list.

Start the SQL Server Configuration Manager from the "Start -> Programs -> Microsoft SQL Server 2005" menu. Then open the "SQL Server 2005 Network Configuration" and select the "Protocols" in the left tree. You must enable TCP/IP protocol and then start the SQL Server Browser service to allow connections from Bopup Communication Server to the SQL server and also to support remote connections to the database if you will install the Management Console of the communication server to administrate the IM server remotely. Select and right-click on the TCP/IP protocol in the list and select "Enable" item from the popup menu.

To start the SQL Server Browser service click the "SQL Server 2005 Services" in the left tree and double-click on SQL Server Browser, the Properties window will show up. Move to Service tab and change Start Mode to Automatic. Therefore, the service will be start automatically when the computer starts. Click OK to apply changes. Back to SQL Server Configuration Manager, right-click on SQL Server Browser on the right window and select "Start" to start the service.

Then restart the Microsoft SQL Server service from the console or reboot computer to apply changes.

Our guide on installing the SQL Server 2005 Express Edition is also valid and can be used for Microsoft SQL Server 2008. You can access the step-by-step guide at

Saturday, August 7, 2010

SQL database maintenance options added to the latest release of Bopup IM server

Version 3.3.17 of Bopup Communication Server adds new options to manage SQL database used by the IM server. The new version has added a new "SQL database maintenance" tab in the Options dialog box.

Now the Management Console includes functionality to backup SQL database to a file or restore the database from a previously saved backup file. A function to clean up the database has been also added. It deletes unnecessary data such as message and file transfer archives, user's session activities history that is older than 30 days. This function reduces a size of the SQL database that affects to a memory size used by MS SQL Server.

Sunday, July 25, 2010

Major update of Bopup Communication Server 3.3.16 is available

New version of the communication server has been released. Version 3.3.16 adds a lot of improvements and fixes amount of bugs.

Increased speed and performance of the server on MS SQL Server 2005 Express Edition.
This version adds "AUTO_CLOSE" option set to OFF for SQL database which increases a performance of the IM server because it tells the SQL Server to do not close the database if last connection has been closed. This issue appears only on MS SQL Server 2005 Express Edition that can be installed as a host database server using our guide at Step-by-Step Guide to Install Microsoft SQL Server 2005 Express Edition as a Host Database Server for Bopup Communication Server.

Fixed and improved option of rebuilding users' Contact List on the server.
If the server enables option to automatically rebuild Contact Lists for all users and there are several Organizational Units in which users are located then the service and console might bring an SQL error while rebuilding contacts. The new version of the communication server fixes this problem.

Fixed issues with stopping the service.
Sometimes the service could not be properly stopped and it stayed in memory. This caused a problem with starting the service again and the service's process must be removed from Task Manager (bcssrvc.exe module) first. We improved the code and now the service should be stopped without issues.

The Management Console added a section to view blog.
The console added a new item in the left tree called "Our blog at". That item opens and displays this blog and we hope that it will help our customers to stay updated and informed on our development process and news.

Update your Bopup Communication Server software by downloading new installation package from Download Center at

Tuesday, July 20, 2010

AUTO_CLOSE option for the SQL database should be turned off

New issue with MS SQL Server 2005 Express Edition has been discovered by us. We noticed that the SQL Server service logs a lot of "Starting up database bcs30" messages with event ID #17137 to Event Log. This occurs only on SQL Server 2005 Express Edition and may cause problems with Bopup Communication Server performance and stability. This issue doesn't appear if the communication server was installed with built-in MSDE 2000 (Microsoft SQL Desktop Engine).

We found that in order to avoid closing and starting up the database we must use AUTO_CLOSE option set to OFF. This bug fix will be included to the next release of Bopup Communication Server.

More information on this issue: SQL Server Best Practices: AutoClose Should be Off