About Central_Support

Intro If you want to get a reliable and safe working discussion system please keep both Windows and DICENTIS up dated! You need to enable  "update your Windows and other Microsoft products" under Advanced setting to get all necessary updates.   Schedule your Windows updates to run at a time when the system is not used. Updating during a meeting/conference could lead to a platform problems for our DICENTIS Software and as result to instability. If you schedule the update via the Windows Task Manager, you should also configure that it automatically reboots after the update, in case a reboot is required. DICENTIS should have the same publishing date as Windows Server updates. Means it is necessary if you plan to update DICENTIS always to update Windows before and then DICENTIS. Switch the Windows update function off if you operate with an offline system.   Step-by-step guide:   Update Windows Server (2016)   The following example below is showing how you should update Windows Server (2016). An internet connection is necessary on your server for that.   1. Click on the search button  Windows Update settings  and press enter. 2. Go to Advanced options. 3. Enable "updates for other Microsoft products…" as well as "Defer feature updates". 4. Now trigger the update with " Check for updates". At that point you should rethink how you can maintain 5. Please check before you update your DICENTIS Software if you have a valid SMA which you can look up in the DICENTIS Activation Tool on the server or with your Account on the System Activation Site. Software Page https://licensing.boschsecurity.com/software/html/pages/home/ System Activation Site https://licensing.boschsecurity.com/StartPage.aspx DICENTIS Software https://licensing.boschsecurity.com/software/DICENTIS/DCNM.iso Please don't forget to Update all Clients with the Windows and DICENTIS software as well.   6. With the Windows Event Viewer you can check for problems or errors. 7. For example you can check the MSSQL if it is working fine. ... View more

  Causes   In some cases it could be necessary that you need to maintain or repair the Microsoft SQL database which DICENTIS is using to save participants, user, seats and some settings.  An exact explanation can be found in the Configuration manual under chapter 14.x. The next steps I will explain some of the basics commands.   Solution   Initial   To do a Database update, backup or restore you need to open the Command Prompt. The initial steps will be shown here. 1. Before you change something with your Database please stop your Dicentis services. 2. Please enter via search and go to: C:\Program Files\Bosch\DICENTIS 3. Go to File 4. And open the Command Prompt as Administrator. 5. The DcnmDatabaseConsole.exe  has the following options.   Updating a database to the current Version   To update a database to the current version please run this exe. DcnmDatabaseConsole.exe This will be needed to execute if you have restored your database from an older database version or a backup.   Creating a clean database   If something went wrong in the Database and you need to start all over you can use this command: DcnmDatabaseConsole.exe -n But you will lose your Users, Seats, settings , and so on if you do this.   Deleting a database   Deleting a database will remove the database files as well. The system will not work anymore unless a new database is created or a previous database is restored. To create a new database use DcnmDatabaseConsole.exe or to upload and existing database use DcnmDatabaseConsole.exe -b This -x  function can be used to delete the database if you need to downgrade to a previous version. This is not recommended and only needed for special actions. DcnmDatabaseConsole.exe -x   The Conference Suite is frozen because the database is missing. After you create a new one or update a backup it will work again. DcnmDatabaseConsole.exe DcnmDatabaseConsole .exe -r "C:\Program Files\Microsoft SQL Server\MSSQL12.SQLDICENTIS2014\MSSQL\DATA\DcnmBackup\DcnmDatabase_v3.50.bak_20201021-052115.bak"   Backup your Database   If you want to backup your database type in the Command prompt "DcnmDatabaseConsole.exe -b" and press enter. If everything is all right you will get a "Success" prompt. DcnmDatabaseConsole.exe -b Next go to "C:\Program Files\Microsoft SQL Server\MSSQL12.SQLDICENTIS2014\MSSQL\DATA\DcnmBackup" select the latest file, in this case  "DcnmDatabase_v3.50.bak_20201021-052115.bak" and save it on a save location.   With our DICENTIS software version 4.10 we implemented an change from SQL Server 2014 to 2019 to follow up the Microsoft improvements. For that reason the file directory changed to "MSSQL15.SQLDICENTIS2019" C:\Program Files\Microsoft SQL Server\MSSQL15.SQLDICENTIS2019\MSSQL\DATA\DcnmBackup     Restore a Database   To restore your database type in the Command Prompt the following: DcnmDatabaseConsole.exe -r " where are your .bak files for restoring?" For example: DcnmDatabaseConsole .exe -r "C:\Program Files\Microsoft SQL Server\MSSQL12.SQLDICENTIS2014\MSSQL\DATA\DcnmBackup\DcnmDatabase_v3.50.bak_20201021-052115.bak"   Note: The Dicentis will always create a backup during an Update for example from 3.30 to 3.60 and this can be found here. C:\Program Files\Microsoft SQL Server\MSSQL12.SQLDICENTIS2014\MSSQL\DATA\DcnmBackup The restore command does not update the database to the current version! To update it to the current version you have to update you database with the DcnmDatabaseConsole.exe command as already described above. Once a while Microsoft is changing the Database like last time from SQL2008 to SQL2014. If your backup is in the  C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQLEXPRESS\MSSQL\DATA\DcnmBackup directory, an error notification will appear because the SQL2014 has no access to this SQL2008 database. Here is a work around to fix this. Please copy it to C:\temp. If everything is working good it will give you a "Success" prompt at the end. Next you have to update you database with the DcnmDatabaseConsole.exe command. After you have backup, restored or updated please don't forget to start the Dicentis services again.   Database related Problems (Microsoft .NET Framework)   An important point is that the Windows .NET Framework is up to date so that no mismatch between Dicentis and Windows is occurring. As example an old version was found in the logs extracted from the DicentisDatabaseBackup which indicates that some important  updates are missing.   Microsoft .NET Framework 4.8 online installation   Regular Window Update is explained in this article: https://community.boschsecurity.com/t5/Conference-Discussion/How-to-automatically-update-Windows-Server-2016-for-DICENTIS/ta-p/25896 Please don't to forget to set Advanced options to enable "updates for other Microsoft products…" as well as "Defer feature updates".     Microsoft .NET Framework 4.8 offline installer for Windows   https://support.microsoft.com/en-us/topic/microsoft-net-framework-4-8-offline-installer-for-windows-9d23f658-3b97-68ab-d013-aa3c3e7495e0 Normally you install the Framework with the regular updates. But some circumstances could lead that it has to be update offline. You can get the correct version on the Microsoft homepage. For this example I will go with this: https://go.microsoft.com/fwlink/?linkid=2088631   Problems during NET. Framework installation   If problems are occurring during NET. Framework manual update or you could not update to the current Framework version automatically it is recommended to recover your Dicentis Server and start with a clean system. This procedure is the fastest, structured and more rational way to get it fixed. The following explains some of the alternative problem solution regarding NET. Frame work errors. We have seen several reports of people having issues installing SQL on Essentials R2, for example: https://social.technet.microsoft.com/Forums/en-US/a08efd22-17ad-4920-8bc0-709fb18203df/sql-server-express-2016-on-server-2012-r2-essentials?forum=sqlexpress   September 2018: Latest recommendations I gave for TSEMEA-11950: This could be indeed a permissions issue, Though it looks like the permissions are correct. In order to make sure: Go to the MS SQL main folder (the parent of DATA) and right-click Properties Select Security & Edit For each user, give them full access permissions Go back and choose Advanced Select Replace all child object permissions... & OK Then run the MS SQL installer first (it's in a separate folder of the Dicentis ISO) Another thing to try if this doesn't help is to completely remove the current SQL install (this may be problematic if it was installed before, but good to try on a new install) Make sure all Windows updates are installed (this may require various reboots and re-checks; they seem to not all install at once unfortunately) Make sure .NET 3.5 is turned on (server feature), make sure .NET 4.7 is installed Re-try the Dicentis installation. Once more, trying the SQL installation separately first and then installing the rest may be practical in this case. We have also seen instances where the issue was caused by a faulty Windows profile (even on new installs strangely enough).  To fix the user profile that's causing the error, follow the steps listed KB947215. The main steps from KB947215 are summarized as follows:- Open regedit Navigate to  HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList Navigate to the SID for the corrupted profile To find the SID, click on each SID GUID, review the value for the ProfileImagePath value, and see if it's the correct account. For system accounts, there's a different way to know the SID for the account that failed: The main system account SIDs of interest are: SID          Name               Also Known As S-1-5-18 Local System NT AUTHORITY\SYSTEM S-1-5-19 LocalService NT AUTHORITY\LOCAL SERVICE S-1-5-20 NetworkService     NT AUTHORITY\NETWORK SERVICE   For information on additional SIDs, see Well-known security identifiers in Windows operating systems. If there are two entries (e.g. with a .bak) at the end for the SID in question, or the SID in question ends in .bak, ensure to follow carefully the steps in the KB947215 article. Reset the values for RefCount and State to be 0. Reboot. Retry the SQL Server installation.   Further information that could be helpful if all this fails is found in the following logs: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log - all logs are useful, but especially SUMMARY.TXT Windows Event Logs: APPLICATION, SECURITY & SYSTEM System info   When there are problems with SQL, the following logs can give insight: During installation: C:\Program Files\Microsoft SQL Server\120\Setup Bootstrap\Log - all logs are useful, but especially SUMMARY.TXT Windows Event Logs: APPLICATION, SECURITY & SYSTEM System info During operation: C:\Program Files\Microsoft SQL Server\MSSQL12.SQLDICENTIS2014\MSSQL\LOG - useful logs are the ERRORLOG and ERRORLOG.x where x in a number. Windows Event Logs: APPLICATION, SECURITY & SYSTEM System Info   Fix: reset the corrupt user profile   To fix the user profile that's causing the error, follow the steps listed KB947215. The main steps from KB947215 are summarized as follows:- Open regedit Navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList Navigate to the SID for the corrupted profile To find the SID, click on each SID GUID, review the value for the ProfileImagePath value, and see if it's the correct account. For system accounts, there's a different way to know the SID for the account that failed: The main system account SIDs of interest are: SID          Name               Also Known As S-1-5-18 Local System NT AUTHORITY\SYSTEM S-1-5-19 LocalService NT AUTHORITY\LOCAL SERVICE S-1-5-20 NetworkService     NT AUTHORITY\NETWORK SERVICE   For information on additional SIDs, see Well-known security identifiers in Windows operating systems. If there are two entries (e.g. with a .bak) at the end for the SID in question, or the SID in question ends in .bak, ensure to follow carefully the steps in the KB947215 article. Reset the values for RefCount and State to be 0. Reboot. Retry the SQL Server installation. ... View more

In some cases the IVA tasks can get lost after firmware update. There are 2 ways. In both ways it's not guaranteed that all task shall work afterwards since new firmware version can contain a new IVA version with new features. So please double check afterwards. It shall at-least save some time instead of starting from scratch.   Step-by-step guide   Option 1: Via the Configuration Manager save your configuration and load it back afterwards   Option 2: Copy/paste the scripting text from "VCA Task Editor"   ... View more

Question   On which occasion does DIVAR recorder send the SNMP trap HDD_STATUS_CHANGE?   Answer   One of the possible traps  that DIVAR IP hybrid/network can send is HDD_STATUS_CHANGE. The HDD_STATUS_CHANGE is triggered when the status of the Hard Disk changes.  The HDD can have the status: OK BAD ERROR MISSING. So HDD_STATUS_CHANGE gets triggered when the Hard Disk stops working or when it gets physically removed. NOTE: List and details for the SNMP traps that a DIVAR hybrid/network can send out on event can be found in the MIB file of the device.    Nice to know: What should you know about SNMP and Bosch cameras SNMP support? How to activate the SNMP and configure sending SNMP traps from Bosch cameras? ... View more

To return or activate your DICENTIS wired License follow these steps. This short instruction will show you how to return and activate DICENTIS licenses with the old license model. It is capt for documentation purpose since some old license system are still in the market. This instruction is only meant for the old license model with DCNM-LSYS and single function licenses which we stopped selling in 2024 and must be changed at some point in time to the new license model if you want to have further updates of our software. We will make special offers after the SMA extinguished to our customers and we expect that most of them will be switching within 5 years to Premium or Ultimate our new participant based license system. The new license system does only work with >5.00 or higher wile the register function was already implemented in 4.40. The old license system is saved on the Server it self  while the new licenses system is saved and managed in the System Activation Site. https://licensing.boschsecurity.com/StartPage.aspx Adding and removing are done in the old licenses system on the server directly and with the new licenses system license will be added, removed or transferred on the System Activation Site. More detailed information can be found in our manuals. https://resources-boschsecurity-cdn.azureedge.net/public/documents/SWM_Configuration_Manual_enUS_72057607375843211.pdf https://commerce.boschsecurity.com/nlexp/en/System-server/p/F.01U.404.927/   The most common reasons for return in the old system is for example a hardware error. If it still possible to give it back you can give it back and assign it after the repair or exchange on the new DICENTIS system Server.  If you plan some maintenance, specially hardware replacements we advice to give back your license beforehand. If you missed to return the licenses or it was not possible due to a crash please contact the Technical Support for help. We can return them manually but it will naturally take some time to get this done for you. In general we would like to point out that a backup of your system is an important task which you should do on regular basis.   Notes: Windows Server 2012 R2 will reach the end of service date in some years and it is recommended to switch to a newer Windows System.    -Windows Standard support till 09.10.2018   - Windows Advanced support till 10.10.2023 Please note that we had discontinued the service for the Windows Server 2012 R2 for the DICENTIS Conference System software since V3.50. If you would like to use the newest version (added functionality and more software improvements) you should upgrade to Windows Server 2016, 2019 or at best 2022. But the new functionality since 5.00 (Media Gateway) also require faster and more powerful hardware and specially GPU power so we advice to change to a new DCNM-Server3 with Windows Server 2022 as well at some point in time. Also Windows Server 2019 and 2022 are not compatible with older version of the DICENTIS Software like V3.40 or lower and it may cause problems. Please keep in mind that you need a valid SMA (Software Maintenance Agreement) to install newer DICENTIS software. Please have a look in your DICENTIS Release Notes for more information. https://licensing.boschsecurity.com/software/DICENTIS/RLN_DCNM_en.pdf   Also the user which is registered at the System activation suite needs technical rights or else you can not change the license. The administrator of your account can grant you technician rights to your different accounts if needed.   Please find below the download link for newest Dicentis Software: https://licensing.boschsecurity.com/software/html/pages/home/   Overview of the licensing process with the old system:     Step-by-step guide   Let's start with the License Return:   First open the "DICENTIS Activation tool" via the Windows tab bar. Click on "Return fulfillments". If you have an "Online" connection to the world wide web go on with the following if not please skip to the point 12. were "Offline" activation is described. I would like to recommend to use online option because it is much faster. Online Return fulfillments: Select your Return Fulfillment tip in your User name and Password and click on "Return fulfillments". It is the same Login as on the "System Activation Site". Please find attached link below. System Activation Site: https://licensing.boschsecurity.com/StartPage.aspx?lang=en   If you have lost your password you can also change this over the "System Activation Site". At the bottom you will see the Progress of the the Return process and the site it will be automatically closed after it is finished. If some error occurred, the site will stay open and the program will give an error warning in this colum as well. Online Activate fulfillments:   To activate a license click on "Add fulfillment" in the "DICENTIS Activation tool" Enter your "Customer information". Add the "Activation ID:" and tip in your login data. The Progress column at the bottom of this site will show the results. Error will shown there as well. Please note that you will get a different Fulfillment number. Troubleshooting:  Please never use this signs in the "Customer information" columns!  <  >  &  "  $  #  ' Offline Return fulfillments:  Select "Offline" mark the license which you like to return and klick on "Create request".  Plug in a USB stick or any other data storage device and save the file on it. Change to a PCwhere you have internet access. Got to the "System Activation Site" and log in your account.    System Activation Site:   https://licensing.boschsecurity.com/StartPage.aspx?lang=en  If you have lost your password you can also change this over the "System Activation Site". Now select " Manage license" than click on "Browse… ,open the "ReturnRequest.xml" file and click on "Process". Save the "ReturnResponse.xml" file on USB stick and return to your Dicentis Server. Click on " Process response message" Now proceed as it's explained below and open on the USB Stick your "ReturnResponse.XML" file and start the " Process response message" Now your Fulfillment which you were chosen before is returned. Offline activate fulfillments:  To activate "Offline" a license open the Dicentis Activation tool and click on "Add fulfillment" Type in your "Customer information" and your "Activation ID:" press "Add" and select "Offline". After this click on "Create request"  Troubleshooting:  Please never use this signs in the "Customer information" columns!        <  >  &  "  $  #  '   Save the "Request.xml" on a USB Stick. Change to a PCwhere you have internet access. Got to the "System Activation Site" and log in your account.  System Activation Site: https://licensing.boschsecurity.com/StartPage.aspx?lang=en Select the Request.XML file via "Browse…" and press on "Process". You will get a "Response.xml" file which should be saved on a external USB stick. Now go to  the Dicentis Server and open this "Response.xml" with the  "Process response message" button. After you press on " Process respond message" your license will be activated and the page will be closed automaticly. Your new Fulfillment Number will be different from the last one. ... View more