FAQ 3 – old
Q. While installing CashView services, the installer fails with an error relating to SQL Server or appears to ‘hang’ whilst displaying “Starting SQL Server” – What should I do?
A. This situation can occur if installing CashView on a PC which already has an existing SQL Server installation. In this case the existing SQL Server setup is using the default network port (TCP 1433) which conflicts with the SQL installation being performed by CashView. To resolve, you can set the CashView SQL Server to use dynamic ports. This requires a change to the SQL Server configuration and to the CashView configuration:
|Leave the CashView installation running.On the Start menu, click All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager.||The SQL Server Configuration Manager window is displayed similar to the following:|
|Expand the item SQL Server 2005 Network Configuration and click on Protocols for VOLUMATIC where VOLUMATIC is the named instance of SQL Server. (If this is an upgrade to an earlier CashView version the instance name may be SQLEXPRESS.)||The SQL Server Configuration Manager window changes to display similar to the following:|
|Right-click on the TCP/IP protocol entry and select Properties from the menu.In the dialog displayed, click the IP Addresses tab. Scroll to the bottom of the list of properties and make the following changes:
Clear the TCP Port property.
Set the TCP Dynamic Ports property to 0.Click OK. You will be prompted to restart SQL Server for the changes to take effect. We’ll do this next.
|The TCP/IP properties window is displayed similar to the following:|
|Click on the item SQL Server 2005 Services. In the right-hand pane, find the service named SQL Server (VOLUMATIC). Right-click on the entry and select Restart.The SQL Server service will restart with the configuration changes. Ifthe CashView installation is still in the “Starting SQL Server” state it
will now complete successfully. Otherwise, restart the CashView
services installation and proceed as before.
Important note: SQL Server will assign the dynamic port
once it has restarted successfully. To obtain the new port number, go
back into the TCP/IP properties screen as described in the previous
steps and refer to the TCP Dynamic Ports property value.
|The installed SQL Server services are displayed similar to the following:|
|Proceed to the FAQ item entitled “How do I use a custom SQL Server port when configuring CashView services and client?“|
A.CashView will use the appropriate SQL Server port supplied to it in its configuration. This is best achieved in the centralised services configuration so that connecting CashView clients pick up the new configuration automatically. See the following steps:
|Let’s configure the gatherer service first:On the Start menu click All Programs > Volumatic > Services > Configure Cash View Services.On the Service tab, scroll down the list of Service settings until you find the SQL Port property. Enter the required SQL Server port number and click Apply.
the change(s) to take effect the CashView Gatherer service will need to
be restarted. Click to select the gatherer service entry in the list
above followed by clicking Restart, or refer to the CashView Administrator Manual for more details.
|The services configuration screen is displayed similar to the following:|
|Now that the gatherer service has been setup, let’s change the client configuration. If all client(s) are getting their configuration from the configuration service (enabled by default) this is the only change that will be needed.On the Client tab, find the Data Source property. The data source property can be specified as follows:sqlserver.domain[,sqlport]
Where sqlport is optional. So, if your SQL Server port is 1818 and your SQL server is named bob-sql, set the property to:
Click Apply or OK to save changes. Clients will now connect with the new settings.
|The client configuration screen is displayed similar to the following:|
Q. How do I force the CashView client to update its cached server information (This info includes: License entitlement, SQL server location and authentication method)?
A. Delete the following file on the client PC. Depending on your OS the file can be found in the following location:
On Windows XP or Server 2003: C:\Documents and Settings\<user>\Application Data\Volumatic\Cash View\clientconfig.dat
On Windows 7, Server 2008 or later: C:\Users\<user>\AppData\Roaming\Volumatic\Cash View\clientconfig.dat
Now restart the CashView client.
A. Error codes and messages are typically displayed in an error message window similar to the screenshot below:
A list of error codes and their descriptions are shown below:
|1000||A serious internal error occurred whilst generating the report. This error will occur if CashView was unable to contact the connected printer device or if the Operating System reports an out of memory error.|
|1001||The requested report was unable to be completed due to a lack of data from the connected CCi(s). Refer to this FAQ for more details.|
|1002||The requested report was completed with one or more warning(s). A warning is typically included in a report for one of the following reasons:The report time span was near to or beyond the current time, therefore not all data may have been retrieved for one of the selected device(s);Device(s) could not be contacted by CashView at the time the report was generated, therefore the report may not accurately reflect the content of the device.|
|10000||Retrying a firmware update to a device failed. Typically caused by a loss of contact with the device.|
|10001||Unable to assign new database id to device. Either the device id was invalid or the device is not in the correct state to have its database id changed.|
|10002||Unable to begin device firmware update. Typically caused by a loss of contact with the device.|
|10003||License error: Adding an additional CashView client would exceed the license allocation limit. Refer to this FAQ for details on removing unused client entries.|
|10004||Error occurred whilst cut and pasting device(s) from one plan page to another.|
|10005||Error occurred whilst loading copied plan.|
|10006||Error occurred whilst saving changes to a copied plan.|
|10007||Unable to start report generation. This error will occur if CashView was unable to contact the connected printer device or if no default printer was set up.|
|10008||The report was aborted during generation. This error will occur if the Operating System reports an out of memory error or a problem occurs with the selected printer driver.|
|10009||Unable to load the selected plan. Either the defined plan was invalid or the database connection was lost during plan load.|
|10010||The plan was loaded but not all devices on the plan were displayed. Check that the CashView user has permission to access each of the locations from which CCi(s) on the plan are located.|
|10011||License error: The number of CashView clients on the system exceeds the license allocation limit. Refer to this FAQ for details on removing unused client entries.|
|10012||The command timed out whilst waiting for a response. For example, this error can occur if the CashView server took too long to receive a new firmware file uploaded by the client.|
|FFFF0000||A serious internal error occurred.|
|FFFF0001||The command completed successfully, an OK result was returned for the specified operation.|
|FFFF0002||Timeout occurred whilst waiting for the command to complete.|
|FFFF0003||User timeout occurred whilst waiting for the command to complete.|
|FFFF0004||Authentication failed or the current user was not permitted to perform the selected operation. For example, a supervisor-level user attempting to delete an existing user account will raise this error.|
|FFFF0005||The requested command does not exist.|
|FFFF0006||A record with the same name or id already exists. This error can occur if attempting to create a user with the same id as an existing user or when saving a plan with the same name as an existing plan.|
|FFFF0007||An invalid parameter was specified.|
|FFFF0008||Unable to complete action as the client has no connection to the database.|
|FFFF0009||The client configuration was either incomplete or invalid.|
|FFFF000C||License error: The number of CashView clients on the system exceeds the license allocation limit. Refer to this FAQ for details on removing unused client entries.|