As with many software programs there are a number of factors which may prevent a program from opening as expected. This article provides solutions to some of the common issues which may prevent Remote Programming Software from opening.
Some common causes for RPS failing to open are:
Anti-Virus Software running while RPS is installed.
Anti-Virus software is designed detect the presence of malicious files or scripts and to prevent them from running. Important files or scripts may be deemed malicious and blocked during the install and cause RPS to fail to open. Verify any Anti-Virus software is disabled before installing RPS.
Firewalls running while RPS is installed.
Firewalls are designed to protect the computer by blocking unauthorized access to or from a private computer network. This may block normal operations of RPS such as connecting to the database. Verify any firewalls are disabled before installing RPS.
Missing read/write permissions in folders created during installation.
Read/write permissions are required in to allow reading and writing to database tables during normal operation. Verify the Windows user performing the installation has administrative privileges required for granting read/write permissions to folders.
Extracting the installation files to the desktop and then executing the installation.
File names may exceed the character limit for file names when the installation files are extracted to the desktop. It is recommended to extract the RPS installation files to a folder at the root of the local hard drive. This reduces the number of characters in file names by eliminating the operating systems path to the user’s folder. For example;
Path to user’s desktop folder: C:\Windows\Uses\User-name\Desktop\ RPS6.08.200\install files
Path from root of local drive: C:\ RPS6.08.200\install files
Use a unique name for the folder at the root of the local drive. Avoid naming the folder name ‘RPS’ as a folder with the name RPS is created during the install of RPS.
RPS Installs but fails to connect to the database:
When Remote Programming Software opens, a secure connection is made to the database which is located in an instance of SQL. An error such as Database connection failed is an indication that connection to SQL was not successful or the database was not accessible.
See the article: How to troubleshoot Database Connection Failed error when opening RPS. https://community.boschsecurity.com/t5/Security-Intrusion/How-to-troubleshoot-Database-Connection-Failed-error-when/ta-p/10290
... View more
The Bosch Account Assistant is a programming tool used to simplify configuring B Series control panels with Remote Programming Software. When a panel account is opened in the Account Assistant view, a step-by-step programming guide is started to configure the most commonly used RPS parameters. Advanced users may prefer the Panel View over the Account Assistant View when programming control panels.
The default account view is set as Account Assistant when creating new users. Use the following steps to select Account Assistant View or Panel View.
1. Select Operator List from the front page of RPS.
2. Right-click on the operator and select View.
Figure 1 Right-click the user from the Operator List
3. Select Edit and then select the Default Account View as Panel View or Account Assistant as needed.
Figure 2 Modify Default Account View
4. Select OK to accept changes.
... View more
When Remote Programming Software opens, a secure connection is made to the database which is located in an instance of SQL. If the connection to SQL is not successful or the database is not accessible, the Database connection failed error will display (see figure 1).
Figure 1 Database connection failed error
This article discusses some possible causes for the database connection to fail, select Details for more information.
Some common causes for the database connection to fail are; failure to connect to the SQL Server, failure to open the database or failure to authenticate the user (see figure 2).
Figure 2 Three common causes for the database connection failure
Review the information displayed in details, then select OK to open the Database Settings Page (see figure 3). This page may also be accessed by selecting Config and System from the front page of RPS.
Note the following settings which are applied during a basic installation of RPS;
SQL Server Name: The Computer Name followed by back-slash [\] and the name of the SQL instance where the database is located, e.g. [computer-name\SQL Instance Name]. The default SQL instance name is BOSCHSQL.
SQL Database Name: The name of the database used by RPS. The default database name is RPSDB.
Authentication: The method for authenticating the database connection. The default entry is SQL Server Authentication.
User Name: The user to be authenticated when using SQL Server Authentication. The default entry is sa (system administrator).
Password: The password used to authenticate the user when using SQL Server Authentication. The default password is RPSsql12345.
Figure 3 System Configuration Page
1. Failure to connect to the SQL Server. Details displays:
“A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. (Provider: SQL Network Interfaces, error: 26 – Error Locating Server\Instance Specified).”
In this case the connection to the SQL Server has failed causing the database connection to fail. Press OK and return to the Database Settings page. Troubleshoot using the following steps;
Check for a correct SQL Server name entry with the following format; [computer-name\SQL Instance Name]. Be sure that a backslash [\] is used between items.
[Computer-name] represents the name of the computer with SQL installed.
[SQL Instance Name] represents the name of the SQL Instance where the RPS database is located. Note that there may be more than one instance of SQL on the PC. The correct instance name must be entered here.
Open Computer Services using the steps below to verify; 1) SQL is installed, 2) the correct instance name is entered in Database Settings, and 3) the related service is running.
Right-click on This PC or Computer and then select Manage and Computer Management opens.
Select Services and Applications and then select Services to open Computer Services (see figure 4).
Figure 4 How to access Services and Applications
A list of computer services displays as in figure 5. Identify the SQL Server service with the RPS database, e.g. SQL Server (instance-name) from the list. Verify this instance name was entered correctly in the Database Settings page under System Configuration (see figure 3). If the service is not listed, then the instance is not installed on this PC.
Figure 5 Locate the SQL Service
Note the Status and Startup Type for the Service. If status does not display Running, right-click on the service and select Start. If the Startup Type does not show Automatic it must be changed from the properties page. Access the properties page by double-clicking on the SQL Server service. Select Automatic from the drop-down list in the properties page as displayed in figure 6.
Figure 6 Verify the Service is running and Startup is Automatic
Verify Microsoft SQL Server Native Client is installed on the PC running RPS. Microsoft SQL Server Native Client can be downloaded from the link: https://www.microsoft.com/en-us/download/details.aspx?id=50402
Beginning with version 6.07, RPS makes an encrypted connection to SQL, therefore TLS 1.2 must be supported on the computer. The following links may be used to verify encryption is supported;
Note that encryption must be supported on both the Client and Server PCs when SQL is located on a remote computer.
Verify a functional network connection between the Client computers to the Server computer when SQL is located on a remote computer.
2. Failure to open the database. Details will display;
“Cannot open database “[database name]” requested by the login. The login failed. Login failed for user ‘sa’”.
In this case the database failed to open after the connection was made to SQL. Press OK and return to the Database Settings page. Troubleshoot using the following steps;
Verify the Database Name entry is correct.
Navigate to the following path and note the name in brackets and verify it was entered correctly in Database Settings;
C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.BOSCHSQL\DATA\[database name]
Press Upgrade Database. This updates the database tables as well as verifies correct ability to ‘write’ data to the database.
Verify the RPS installation was executed by right-clicking on the installation file and selecting ‘run as administrator’ (see figure 7 ). This permits the system to make required changes to the registry as well as grant read/write permissions to files & folders where needed.
Figure 7 Install with Administrator Privileges
Attempt to create a new database. As a possible last resort, this will validate that the login method had the ability to create a new database and has write permissions to update tables.
3. Failure to authenticate the user: Details will display;
“Login failed for user sa”.
In this case the RPS uses SQL Server Authentication to authenticate the database connection, using the user/password entered in Database Settings. The problem may be caused by an incorrect password or one which doesn’t meet domain restrictions for complex passwords. Press OK and return to the Database Settings page. Troubleshoot using the following steps;
Manually enter the default user name and password loaded with a basic install of RPS; User Name: sa and Password: RPSsql12345. Change Authentication from SQL Server Authentication to Windows Authentication in Database Settings. If the connection fails proceed to the next step.
Use Microsoft SQL Server Management Studio to verify a correct password is used, or to create a new password which satisfies the domain requirements for complex passwords. Examples are;
Minimum number of characters.
Upper case characters.
Lower case characters.
Numbers between 0-9.
Non-alphabetic (special) characters (for example, !, $, #, %)
Download and install Microsoft SQL Server Management Studio (SSMS).
Go to the SSMS installation page in a browser with the following link: https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15
Figure 8 Download SSMS
Click the Download SQL Server Management Studio link.
Right-click the downloaded SSMS setup file and select Run as Administrator.
Follow the on-screen prompts to install SSMS.
Figure 9 Welcome to install screen
Figure 10 Select Restart
Select Restart to complete the installation(see figure 10).
Figure 11 Open Management Studio
Open SQL Server Management Studio (see figure 11).
Figure 12 Log in using Windows Authentication
The Connect to Server dialog opens. Select Windows Authentication and then select Connect to log into the server's dashboard (see figure 12).
Figure 13 Object Explorer
SQL Server opens to the Object Explorer page with configuration options (see figure 13).
Figure 14 Object Explorer Security expanded
Double-click on Security or click on [+]to expand the folder (see figure 14).
Figure 15 Object Explorer Logins Expanded
Double-click on Logins or click on [+]to expand the folder and then double-click on the user; sa (system administrator) to open the Login Properties page (see figure 15).
Figure 16 Login Properties sa password
The login properties for user: sa opens to the General page.
Enter the default password RPSsql12345 in Password and again in Confirm Password.
Select OK at the bottom of the page.
Note that the overall settings in Microsoft SQL go beyond the scope of this article. The assistance of a qualified SQL administrator may be needed when the steps in this article have not resolved the "Database Connection Failed" error.
... View more
Opening Remote Programming Software initiates a connection with the database it uses, located in SQL. This connection is normally authenticated using SQL Server Authentication, and with the user name [sa] and default password [RPSsql12345]. If this password needs to be changed, for example to meet a domain’s requirements for a more complex password, SQL Server Management Studio is used to make the change. The following steps may be used to change the System Administrator (sa) password in SQL.
1. Download and install Microsoft SQL Server Management Studio (SSMS).
Go to the SSMS installation page in a browser.
Click on Download SSMS (SQL Server Management Studio).
Right-click the downloaded SSMS setup file and select Run as Administrator.
Follow the on-screen prompts to install SSMS.
3. Open SQL Server Management Studio.
4. The Connect to Server dialog opens. Select Windows Authentication and select Connect to log into the server dashboard.
5. The Object Explorer opens. The SQL Server Instance name opens and several options should expand below it. If the list doesn’t expand, click on the [+] icon to expand it.
6. Click on the [+] beside Security to expand the folder.
7. Click on the [+] beside Logins to expand the folder.
8. Double-click on the user login; [sa]. The properties window for the login [sa] opens.
9. Enter the new password and enter again to confirm.
10. Press OK.
... View more
Access to doors is controlled by a Security Level selection in the user’s authority, assigned to the area where the door is assigned. Depending on the security level, access is granted when the area is armed, disarmed or not at all. It is selected in the same location as all user permissions and may be different from area to area if different authority levels were assigned to each area. For example, a user may be permitted use keypad commands in two areas but door control in only one and still limited to the current arming state.
Security Level Options:
[A] All On: Users have access rights for this area in any armed state.
[P] Part On: Users have access rights for this area when armed Part On or disarmed, but not when the area is armed All On.
[D] Disarmed: Users have access rights for this area only when it is disarmed.
[ -] No Access: Users do not have access rights to this area.
Figure 1 Security Level selection in the Authority Level
Disarming after access is granted while an area armed: Because access may be granted to open a door while an area is armed, a method of disarming must be considered in order to prevent false alarms. Disarming may be performed at a nearby keypad or automatically when access is granted. A selection for Disarm Level is also made in each authority level along with Security Level and other permissions. Depending on the selection the area may be either disarmed or reduced from All-On to Part-On Instant, thereby maintaining a level of protection for occupants in the area.
Disarm Level Options:
[ I ]: When the area is armed All-On Delay (or Instant) and access is granted, the armed state is modified to Part-On-Instant.
[D]: When the area is armed All-On Delay (or Instant) or Part-On-Delay (or Instant) and access is granted, the armed state is modified to Disarmed.
[ - ]: The area arming state remains unchanged when access is granted during any arming state. Figure 2 Disarm Level selection in the Authority Level
How to prepare a site to grant access to only selected doors for different levels of users.
Determine the types of users operating on the site and which doors each type will need access to. Examples of user types could be managers, cash-room workers, general workers and possibly a cleaning crew.
Divide the site into the areas normally accessed by each type of user. Examples could be main area, cash-room and manages office. Managers may need full access to doors in all areas where cleaning crew may only access the main entrance.
Figure 3 Example with Multiple Doors and Areas
Assign each access door to an area according to the site floorplan determined in step 2 above.
Create authority levels to be used by the types of users using each particular areas.
Select E for the general panel operations to be permitted by the user.
Select Security Level= [A], [P], [D] or [ - ] to determine the maximum arming state when the user will be granted access.
Select Disarm Level= [ I ], [D] or [ - ] to determine if the user is permitted to modify the arming state when access is granted. If the area arming state should not be modified, select [ - ].
How to use schedules to restrict when access credentials may be used to control doors.
Create an Access Control Level Sked ON time.
Go to Schedules > Skeds and select an available Sked.
Double-click on Function and select Access Ctrl Level.
In the Functions dialogue Parameter1 select ON.
In the Functions dialogue Parameter2 select the level to be controlled and OK.
Double-click the Time selection, uncheck Disabled and enter the time when the selected Access Level turns on.
Select the week days when the sked will execute. Note that Date selections override days of week.
Create an Access Control Level Sked OFF time.
Repeat steps 1a and 1b.
In the Functions dialogue Parameter1 select OFF.
Repeat steps 1d thru 1f.
Door Control Features (controlled in Access programing):
Auto Door: (default=No). Controls the door locking state according to the area armed state.
YES: The door locking state follows the assigned area’s arming state. When disarmed the relay is activated to unlock the door, when armed the relay is always deactivated to lock the door.
No: The door state is not affected by the area’s arming state.
Note: Intrusion panels always automatically lock any previously unlocked access door when the assigned area is armed.
Fire Unlock: (default=No).
Yes: Fire or Gas alarm activates the output to unlock the door and shunts the door point.
No: Door remains in its current mode upon a Fire or Gas alarm.
Disarm on Open: (default=No). Determines when the area disarms after access is granted. Note that this setting only pertains to users with permission to disarm.
YES: Users with disarm permission will disarm the area only after the door point is faulted by opening the door.
NO: Users with disarm permission will disarm the area immediately upon access granted.
Deactivate On Open: Determines when the output deactivates to relock the door after access is granted.
YES: Output deactivates to relock the door when the door point is faulted (the door is opened) after access is granted.
NO: Output remains activated for the programed strike time whether the door is opened or closed.
Notification when an access door is left open: When a door is left open after the Shunt and Extend times expires, keypads can sound a warning tone and display Close Door when programed. Additionally, the point assigned to the door indicates a Trouble, Alarm, or Fault at the keypad. To configure in programming select;
Extend Time: (default=10) Selected in the Access area, enter the amount of time (1 to 30 seconds) to prolong strike, buzz, and shunt activation when the shunt time expires and a door remains open.
Close Door Warning Tone: (default=Yes) Selected in Keypad Assignments:
YES: Keypads sound a warning tone and display Close Door when the access door is held open past the Shunt and Extend Time.
No - this keypad does not activate a warning tone or show Close Door.
... View more