ROBOTILL Setup - Advanced tools

For normal installation or an upgrade, follow Install ROBOTILL. Use Advanced to change this computer's setup. For technical maintenance or recovery, ask your IT provider or ROBOTILL support for help.

Open Windows Start > ROBOTILL > Database Setup, approve the Windows prompt, then choose Advanced / support. The setup-change options appear first. Scroll down for database maintenance and other support tools. Settings are tested and saved by the selected operation; there is no separate Save button.

Change this computer's setup

Connect to another main computer: choose Choose setup file and select the file saved on the main computer you want to use. The old connection does not need to work. See connecting to a different main computer.
Set up a new main computer: install the database software and create a new database here. If moving your shop, back up on the old main computer first, then restore through ROBOTILL before trading. See changing to a new main computer.
Use an existing local database: switch back to a ROBOTILL 10 database already stored on this computer without a setup file. Enter the original SQL instance name (often SQLEXPRESS or ROBOTILL) and database name (usually redtill). Use an authorised SQL administrator connection, choose Reconnect to local database, provide a Manager sign-in for that local shop and confirm. Products, sales and settings are kept. This resets the application's connection password: close ROBOTILL on all computers using that database, then export fresh setup files for them. Restart ROBOTILL after reconnecting. SQL Server and the database must already exist.

Database maintenance and repair

Set up an existing SQL instance: use SQL Server you installed separately. Tick SQL Server is on this computer and enter just its instance name, for example SQLEXPRESS. Keep the database as redtill, select the authorised administrator connection, then choose Create new database. Setup creates restricted application access and saves the verified connection. This action refuses to replace a database that already exists.
Server name or address changed: enter the corrected address and choose Test and save server address. This keeps the existing application login and verifies that the database is the same installation. It does not use the administrator credentials. To connect a client to a different database, import that server's setup file.
Recreate database - start from scratch: select the existing database and choose Recreate selected database. All existing products, sales and settings will be deleted. Review the target, backup choice and typed REPLACE confirmation. This creates new application credentials; reconnect additional computers with a new setup file.
Restore Database from Backup: select the connection, choose a full backup and confirm the replacement. Current data is replaced with the backup's contents. Setup verifies the backup, backs up the current database, assigns a new restored-database identity and creates new application credentials. Export a fresh setup file for other computers. Always restore through ROBOTILL; direct restores with SQL Server tools or other software skip the required identity and connection updates. See Restore Database.

Choosing the SQL connection

When SQL Server is on the computer running Setup, tick SQL Server is on this computer. Enter SQLEXPRESS, ROBOTILL or your actual instance name; use MSSQLSERVER for the default instance. Setup uses local shared memory automatically. You do not need to type a prefix or port.

For a network connection, untick that option and enter a server address such as MAINPC\SQLEXPRESS or MAINPC,11433, using the port actually configured for SQL Server. SQL TCP access and the firewall must be configured. A named instance over TCP needs SQL Browser unless its port is supplied; do not assume that SQL Express uses port 1433.

Support may supply an explicit address: lpc:.\SQLEXPRESS uses local shared memory and tcp:MAINPC,11433 uses TCP. The local address cannot connect an additional computer to your server. Configure and verify a network address before exporting settings for clients from an IT-managed installation.

New database creation and recreation use a restricted SQL application login, so SQL Server must allow SQL Server and Windows authentication (mixed mode). The Windows administrator checkbox selects the administrator connection; it does not change the server's authentication mode. Setup checks this before creating or replacing data. Windows-only application access is a separate IT-managed option below.

Other support tools and administrator settings

Choose Other support tools for the maintenance operations below. Expand SQL administrator, ownership and encryption options when those settings are needed.

These settings select the server and database for the operation. Windows administrator authentication is selected by default. An IT provider can supply SQL administrator details when Windows authentication is unavailable.

Use the existing saved connection for this one migration only: uses the old connection to update an existing installation.
Exclusive ROBOTILL ownership: confirm this only when the SQL instance is managed by ROBOTILL and used by no other program.
Encrypt SQL connection / Trust SQL certificate: control connection encryption and certificate checking. Use the policy supplied by your IT provider or support.

A request for a ROBOTILL Manager sign-in means your existing Back Office username and password. The SQL administrator fields are separate. Follow each tool's prompts to close ROBOTILL on other computers before maintenance.

Tools

Tool	What it does
Migrate Existing Installation	Backs up and updates an existing database, then creates restricted application access and saves the protected connection. Additional computers must import a new setup file.
Configure Customer-managed Windows Authentication	Sets up restricted database access for a Windows group approved by your IT provider. Verifies an ordinary Windows account. The provider manages group membership and the SQL authentication policy.
Export Connection Settings for an IT-managed Installation	Saves a setup file for other computers. Requires a Back Office Manager sign-in and separate SQL administrator authority for an IT-managed installation. Keep the exported file private.
Upgrade Database on Server	Updates the database structure for the installed ROBOTILL version, with a backup and connection checks. Run on the main computer for a standard ROBOTILL installation.
Reset Application Connection Password	Replaces the password ROBOTILL uses to connect to the database. All computers need a new setup file. This does not reset a user's Back Office password or till PIN.
Finish Interrupted Credential Operation	Resumes a connection-credential change that was interrupted. Uses the saved recovery information; keep that information in place until recovery succeeds.
Confirm Managed Server Ownership	Confirms that the local SQL instance belongs exclusively to ROBOTILL and verifies independent Windows administrator recovery access. Network access and retirement of the old SQL administrator are separate steps.
Retire Legacy SQL Administrator	Changes and disables the old SQL administrator login after independent recovery access is verified. Use only for an exclusively ROBOTILL-managed instance, after all active computers use the new connection.
Allow Additional Computers to Connect	Enables local-network access on a ROBOTILL-managed main computer, configures its port and firewall access, and restarts the database service. Then export and test a setup file on an additional computer.
Review Old SQL Firewall Rules	Shows recognised old ROBOTILL firewall rules for review. A rule is removed only after confirmation. Test a connection from another computer after changes.
Allow Another Windows User	Allows another Windows account on this PC to read its protected ROBOTILL connection settings. The user may need to sign out of Windows and back in. This does not create a ROBOTILL staff account.

Other buttons

Back returns to the previous screen. From the advanced-tools list it returns to simple setup.

Save support log is available at the bottom of the advanced screens and after an error. It saves a text file with an action summary and numbered attempts, entered values, selections, confirmations, connection targets, steps and original errors. Timestamps include the local UTC offset. Passwords and connection credentials are redacted; shop records are not collected. Email the file to support@robotill.com; nothing is sent automatically.

Read the action summary first, then find the matching attempt in the timeline. Saved connection - reference only describes earlier settings; Operation connection identifies the connection selected for the action and does not itself prove success. Local SQL registry diagnostics describe configured settings, which may require a service restart before they take effect.

Back to installation and upgrade instructions