Building Automation Knowledge Base

Issue When the Sigma client attempts to connect to the Sigma server it fails and reports an error "No Seats Available".  What is the maximum number of clients that can be connected to a server? Product Line Satchwell Sigma Environment Sigma version 4.08 Client connections Cause Sigma server is not licensed for the attempted client connection Resolution For a customers system check: 1.  The Sigma dongle is licensed for the number of clients to be connected.  From a working client see Help - About and the number of clients supported is shown in the brackets ().  The maximum allowed depends on the operating system where the OS itself limits the number of consecutive connections; Windows 2003/Windows 2008 server:  Maximum client connections is 10 Windows XP/ Windows 7:  Maximum client connections is 5 2. Run the file C:\Sigma\bin\Setupsvr.exe and check that if a local client (on the same PC as the Sigma server) that "My Computer" is ticked or for a remote client (not the same as the server PC) that the "My Computer" is un-ticked and the correct Sigma server IP Address is entered. 3. Also in the Setupsvr.exe for a remote client check that the HTTP Server Port is set the same as the Sigma server (default = 8080) 4. Close down another client to free up a seat 5. Purchase more licensed clients (seats) using ZSO_CLIENT-x (where x is the number of additional clients - max 5 for Windows XP/7 server and max 10 for Windows 2003/2008 server).  Must add the Dongle number to order.    For an engineers laptop (Local connection) running SigmaX check: 1. SigmaX 7.0.9 does not require an unlocking code, if your using an older version of SigmaX you will need to uninstall SigmaX and install SigmaX version 7.0.9. SigmaX 7.09 no longer unlocks Sigma (or BAS2800+). To unlock Sigma you will need to install the SBO (Verision 1.5, 1.6, 1.7, 1.8 or 1.9) or EBO license administrator (Version 2.0 or later) and unlock Sigma using the current EcoStruxure Building Operation Evaluation License. The evaluation license is available to download form the Schnieder Echange Extranet web site. Latest version of SigmaX download provides some information on the changes in SigmaX version 7.0.9 and provided a link were the software can be downloaded. 2. If the Ethernet connections have been enabled or disabled (i.e. laptop has been with IT or wireless switched off/on) then a new SigmaX code will most likely be required. 3. Run the file C:\Sigma\bin\Setupsvr.exe and check that "My Computer" is ticked.

Issue When using TAC Vista 5 Demo License and Site License at the same time, Vista returns “Your application was not able to obtain a license because the FLEXnet license server manager could not determine where to find the licensing data it needs. Please choose one of the following: Specify the License Server System Specify the License File Product Line TAC Vista Environment Vista 5.X.X with Site License and Demo License Cause Using Vista 5 Demo License concurrently with Site Licenses, or having an expired Demo License in the License File folder with Site License may cause Vista ignore the Site License or not fully read the Site License. Resolution Remove Demo License from the License File folder. Restart the computer. If the issue still exists, follow Switching from the Demo license to the site License in Vista 5.1.7 or older.

Issue Is it possible to configure Workstation so that certain users see certain alarm categories? Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation Cause There may be a need to restrict access to certain alarms on a site, if for example a site is comprised of two or more buildings, it may be appropriate for users in Building 1 to only see alarms from Building 1, and not the others. Resolution To achieve this filtering a workspace, alarm view and user group must be configured. Start by creating an Alarm View object in Workstation. Edit the Alarm view and set an appropriate filter i.e. the alarm priority to be displayed. Next create a new Workspace. Ensure that an Alarms Pane is added and that the Initial Path property is set to the Alarm View created in step 1.  Create a new user group and add the Workspace created in step 3 to the group's Selected Workspaces. On the Software Permissions tab for the group, give the group Read permission for the Alarm View created in step 1. Add other appropriate permissions as required. Lastly, create a user a make them a member of the User Group created in step 5. Log in to workstation with the new user. You should then only be able to see the filtered alarms and the user should not be able to change the filter. Also check out the SmartStruxure Software Permissions Quick-Help video on the Exchange.

Issue Is it possible to see how many users are logged in to Webstation? Product Line TAC Vista Environment TAC Vista Webstation 5.1.X Cause The number of users logged into Webstation at one time is limited by the number of available licenses.  Need to have a way to monitor this resource. Resolution There is no built-in function in TAC Vista Webstation to see how many users are logged in at a certain time. The only way to see how many users are logged in at the same time is to use the License Server Webpage. There it is possible to see how many Webstation licenses are in use. To access the License Server webpage: Open a browser and type in localhost:8888 Open the "Dashboard" and click on "Concurrent" See also Using Lmtools in Windows Vista/7/Server 2008 for Windows Vista/7/Server 2008 OS.

Issue When downloading a programmable controller with the Vista system plug-in, the process fails and reports the Error 80041195, Info: Communication port not connected. NOTE: Error 80041195 has also been reported when performing a commence communication command in the Vista system plug-in. Product Line TAC Vista Environment Vista Server 5.1.5 Vista System Plug-In 5.1.5 Cause Vista Server 5.1.5 is not communicating to the LNS server properly Resolution Vista Server hotfix 14 addresses this error within Vista Server 5.1.5. Download TAC Vista Server 5.1.5 Hotfix 14 from The Exchange Download Center. Run the TACVista515HotFix51514.exe file. Reboot the machine. This error has also been observed If the PC is running a a 64-bit operating system which is not supported for LonMaker or NL220. See Echelon LonMaker and Newron NL220 on 64-bit operating systems for more information.

Issue Commission and download command on a controller beneath a Xenta Server in a Vista classic network fails. Error: Completion event-failure, Info: $Address Product Line TAC Vista Environment Vista Workstation Vista classic network Xenta Server Cause This error does not indicate an error with the addressing of the controller.  What it refers to is the reading of parameters from the controller in an attempt to commission and download.  The first parameter it tries to read is the address, and if that fails, the $Address indicates which portion it failed on.  Since $Address is first, this indicates a complete lack of communication with the controller. If this issue occurs with a freely programmable controller (Xenta 280/300/401) under a Xenta Server (Xenta 5/7/913) it may be due to the Xenta Server firmware version not matching the Vista Server version. Resolution Go to the controller and look at it.  The green LED on the front should be solid green. Physically inspect the wiring of the controller.  A shorted LON, for example, would cause this error.  Make sure all wires are terminated firmly. For DDCs under Xenta Servers: Please refer to Xenta Server firmware versus Vista Server versions for the Xenta Server compatibility matrix with Vista Server. If a Xenta Server's firmware version does not match the Vista Server version then either uninstall Vista Server and reinstall the correct version of Vista Server or reload the correct firmware version to the Xenta Server.

Issue All MNB devices under the UNC-520 are offline and not communicating. Product Line TAC IA Series Environment MNB controllers connected to UNC-520 RS-485 port Cause The MNB-300 and MNB-1000 bias resistors (jumpers label 'MS BIAS') should be disabled by default as indicated in their respective documentation. However, it appears that the MNB-1000 bias resistors are coming enabled. As a requirement of EIA-485 network topology, an MS/TP network must have at least one set, and no more than two sets, of network bias resistors on each MS/TP network segment, preferably (but not required to be) in the middle of the segment. In MS/TP networks, this requires an MNB-300, MNB-1000, or UNC-520 with the appropriate jumper settings. UNC-520 bias resistors on its RS-485 ports are enabled by default. Resolution Ensure that no more than 2 sets of bias are enabled on the MS/TP segment. The bias on the UNC-520 is enabled by default and as such, there should not be more than 1 MNB controller with its bias resistors set enabled on the BACnet MS/TP segment. Refer to page 71 of the document ‘F-27360 IA Series Micronet BACnet Wiring, Networking and Best Practices Guide’ for further information. Also refer to Enabling MSTP bias resistors on a MNB-1000.

Issue A job site has several ENCs installed each doing a LON integration and a Schneider-Electric legacy integration (like ASD, GCM, DMS, or MS). Any ENC is currently licensed with the following filter: accept.wb.in="TAC". This only allows copies of Workbench branded as "TAC" to connect with it and perform tasks like data extraction and logic programming. Can an ENC's brand filter of "TAC" be changed to "*" to allow any company's copy of Workbench to access it? Product Line TAC IA Series Environment Niagara G3 ENC-410, ENC-520 Cause Sites may contain equipment from two Tridium integrators and the end customer wants one copy of Workbench to work with all equipment. A performance contracting company may also be Tridium integrators and want access to the ENCs with their own copy of Workbench. Resolution Typically, if the ENC does not have a Schneider-Electric legacy integration, an open branding of the license is allowable. However, for all requests to open brand a Niagara G3 license, contact Schneider-Electric's Regional Sales Manager (customer care can provide the contact name for your office) If this is a new order, an open branding of the license can be requested directly on the license order form. See Niagara G3 (NiagaraAx) Open NiCS (Niagara Compatibility Statement) for details.

Issue Cameras have learned in successfully but live video shows as black or the Video Administrator shows the preview as black. Product Line Andover Continuum, Pelco Environment Continuum Endura Windows XP Windows Vista Windows Server 2003 Windows Server 2008 Cause Live video is showing black because of a configuration issue. Resolution There can be a number of reasons why live video is showing as black in Continuum. Here are some steps to correct or troubleshoot this: Time between devices is not synced. Verify that the controller(InfinintySystemVariable Date), Cyberstation(DateTime Date), and the Endura system(SM) time are all synced. Video Driver or Card. To allow for Sarix cameras in 1.92 changes were made that could cause a standard VGA driver to not display video. Update the standard driver or change the video card. (Test with a different PC which uses a different card) Multicast traffic. Check that the switches on the LAN are broadcasting traffic using multicast. Run the Sherlock utility which is a free codec utility to determine the codec on the Cyberstation and send the results to Product Support. It can be found at the following web site: http://www.free-codecs.com/Sherlock_The_Codec_Detective_download.htm Ensure that the cameras were renamed from the default name in Endura (defaults to camera, but it's actually a null). Ensure that each camera has its own unique non-zero input/channel number. Both of these two items can cause the Continuum camera learn to not be successful and cause issue when trying to access video. Video.log files. Configure the video.log files per How to create a log file for troubleshooting video integration issues in Continuum. Send these files to Product Support for analysis.

Issue During download to a b3 controller you may see the error: Unknown object Module: BACnet plugin Module code : 0 Technical info: BatchedWritePropertyError Product Line EcoStruxure Building Operation Environment Automation Server WorkStation Cause Binding sending data to a point during the download process Resolution This error is benign and can be ignored. Also check out the SmartStruxure - b3 Engineering Process - Part 6 Downloading Quick-Help video on the Exchange. NOTE The "BatchedWritePropertyError" may also be seen with "Property value out of range" rather than "Unknown Object", in this case check the properties/settings of the BACnet Object, the channel may be out of range or an Expansion Module may be required

Issue DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2 'Cannot open backup device ' C:\Users\Administrator\Desktop\20120919'. Operating System Error 5( Access is denied). [Microsoft][ODBC SQL Server Driver] [SQL Server] BACKUP DATABASE is terminating abnormally' Product Line TAC INET Environment I/NET loaded on Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2 Cause The cause is insufficient rights to perform this function based upon a local policy of not allowing users to see the 'C' drive. Resolution Although when Using a Network Administrator account or Administrator for the local machine, you cannot open backup to either the local machine 'C' drive or a network share, you should be able to backup to a thumb drive.  Go to local disk properties - security tab Users do not have permissions to modify or write to the 'C' drive. Windows UAC may over ride the administrator permissions. Check your permissions and make sure you have rights to a folder and perform the backup. Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.  

Issue The order of installation is dependent upon the SQL versions installed with Vista and I/NET. I/NET DBCreate does not open after installation is complete.  DBCreate application is not shown even though under Task Manager processes the application is active. Product Line TAC INET, TAC Vista Environment SQL MSDE Express Vista and I/NET Installed on the same PC Cause Vista and I/NET both use SQL databases for purposes of event and trend logging.  They must be installed in the correct order to coexist within the shared SQL installation. It can be confusing to know which software should be installed first on a certain installation because it is completely dependent upon both the I/NET versions and Vista versions.  Later versions are compliant with SQL 2005 Express while earlier versions must use SQL MSDE. Resolution If a previous installation has failed, it is best to start "fresh" before attempting a re-install. Removal of Vista instructions located here: How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Removal of I/NET instructions located here: Procedure for uninstalling I/NET Seven on a stand-alone host Empty Recycle Bin to remove evidence of previous installations.    Use the following guidelines to determine in which order to install I/NET and Vista: If the I/NET version is prior to 2.2.1, then I/NET must be installed before Vista, regardless of the Vista version. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 4.3.0 through 5.0.0, and the I/NET version is 2.2.1 or higher, then Vista must be installed before I/NET. These versions of Vista use TAC Config and SQL MSDE. When prompted during the Vista installation, allow a new SQL instance on the existing SQL MSDE that was installed with I/NET.   If the Vista version is 5.0.1 through to 5.1.6, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET. These versions of Vista use SQL 2005 Express.  I/NET versions 2.2.1 and higher have an option to install SQL 2005 Express. When prompted during the I/NET installation, allow a new SQL instance on the existing SQL 2005 Express that was installed with Vista.   If the Vista version is 5.1.7 and above, and the I/NET version is 2.2.1 or higher, it is recommended to install Vista before I/NET The default installation of this version of Vista uses SQL 2008 R2 Express.  When prompted during the I/NET installation, select Default Instance of either MSDE or SQL 2005. (Note that if installing on Windows7 operating system, MSDE option is grayed out and cannot be selected, as it is not supported on Windows7)..   If the Vista version is 5.1.7, and the I/NET version is 2.4.0 or higher, you can choose either one to be installed first. If Vista is installed first, by default Vista will install SQL 2008 R2 Express SP1. But I/NET 2.4x fails to recognize the instance installed by Vista, while also fails to create a default instance. So after installed Vista, manually create a default instance for I/NET, and then install I/NET. Refer to Item 1 in How to Troubleshoot on DBCreate on how to create it; If I/NET is installed first, you can choose Custom Installation for SQL during the installation of Vista. You need to manually enter the SQL instance name, SQL username and password when installing I/NET SQL. If you don't know the instance name, there is a quicker way to identify it: Open DBCreate of I/NET, and you can see the SQL server name for I/NET. Just copy and paste it here. Then you can finish the installation. For Vista IV installation, the correct procedure can be found here: TAC Vista IV and Peripheral Software Installation Outline

Issue Ports are required to be open for I/NET to communicate Need to know the UDP TCP/IP port settings for I/NET. File Equalization failure or NPR devices not coming online Some links (NPRs) are showing offline and can not be connected too, while others work fine. Product Line TAC INET Environment I/NET NPR NPR-527 Cause A Firewall may be blocking ports required for File Equalization and I/NET communication to occur. Resolution You will need to work with the IT department to verify these settings. I/NET communications occurs through port 50069. When using File Equalization you will also need to ensure that ports 1433 and 1434 are open as these are used by SQL. Integral DVR communicates to I/NET on port 18772 For systems with 527 devices or other Xenta servers, please review Ports used by TAC Vista System.

Issue Receive error stating that a Menta "File object is locked by another application" when trying to open it for editing. Product Line TAC Vista Environment TAC Vista Menta Cause There are several potential causes of this error: The Menta (.mta) file is already open locally or on a remote machine. The current user does not have the appropriate authority to edit the file. Menta crashes while editing a file opened directly from the Server. Each subsequent attempt to launch the Menta editor from Workstation will result in this error. When a "standard" Menta file is being used and the user attempts to edit the Menta file locally. For more information about this scenario, please see "Read-only because object refers to a standard file" when editing Menta from Workstation. Resolution The following resolutions correspond to the causes listed above: If an instance of Menta already has the file open, whether on the local computer or on a remotely connected computer, then it must be closed before trying to open and edit that particular Menta file again. If the current Vista user has only "User" privileges or is otherwise limited from editing Menta then a user with the appropriate authority should log in to open the Menta file for editing. Shut down then restart Vista Server and Workstation if the error was caused by Menta crashing. See the link in Cause D above.

Issue Where can I find datasheets, install guides and other documentation on the HID SmartID, iClass, HID Proximity and Indala Proximity cards and readers? Product Line Andover Continuum, Field Devices, TAC INET Environment Electronic Access Control cards and readers for Continuum and I/Net products. Cause Additional product information from HID may be required that is not available on Schneider Electric's own websites. Resolution Schneider Electric supply a subset of the full HID range of cards and readers and these are detailed in the Electronic Access Control Catalogue or see How to determine the part number for the card format required for part number information. For HID product information this can be directly downloaded from the HID Global website. This contains  datasheets, installation guides, application notes, feature lists, brochures and other documentation. HID also have a "Knowledge Center" website that allows you to search for product information and help: HID Knowledge Base. Information on the specific ranges can be obtained from the following links: SmartID: SmartID Cards iClass: iClass Readers iClass SE Readers iClass Cards HID Prox: HID Proximity Readers HID Proximity Cards Indala Prox: Indala Proximity Readers Indala Proximity Cards

Issue Alarms stops coming into Vista from Xenta 280/300/401 in the Lonworks network under a Xenta 913 or a Xenta 701. Xenta 280/300/401 controller goes offline/online in Vista. Unable to disable an alarm from a Xenta 280/300/401 that are under a Xenta 913 running as Xenta Server in Vista. Product Line TAC Vista Environment TAC Vista TAC Xenta 913 TAC Xenta 701 TAC Xenta 401 TAC Xenta 301 TAC Xenta 302 TAC Xenta 281 TAC Xenta 282 TAC Xenta 283 Cause There is no support for adding Xenta 280/300/401 to the Lonworks network under a Xenta 913/Xenta 701 running as Xenta Servers in Vista (even though if it is possible to do it in the software). Resolution Use a different Xenta Server that supports adding programmable Xenta controllers in the Lonworks network. Please see the table in chapter 1.1 of the TAC Xenta Server - Networks Technical Manual or Xenta Server version 5.1.5 and after Major Features.

Issue Gets error message "GCM Not responding" when he attempts to make a connection to a device on the ASD bus under the UNC. Product Line TAC IA Series Environment I/A Series R2 UNC I/A Series R2 TunnelAX jar file, version 2.301.534a or later I/A Series ibsASD jar file, version 2.301.534a or later I/A Series G3 Serial Tunnel 2.0 Client Cause Misconfiguration of tunnel name Resolution Before attempting to configure the AX Tunneling, verify that the correct versions of the R2tunnelAX and ibsAsd jar files have been installed as documented in How to install an I/A Series R2 JAR File. Tunnel Name in AX Tunnel Client must match the Tunnel Instance name in the ASD Service. When you add the AxSerialTunnel to the ibsAsdService, the identifier is automatically assigned based on the port defined in the communications configuration of the IbsAsdService itself.  This name is displayed under the Status tab of the AxSerialTunnel: Figure-1 When configuring the "Niagara AX Serial Tunnel 2.0", the following window is displayed. Figure-2 The tunnel name (See Figure 2) entered in this window must match the port identifier shown in the AxSerial Tunnel definition (See Figure 1).  If these identifiers do not match, the Ax Serial Tunnel Client will not be able to connect to the tunnel in the I/A Series R2 station. NOTE: When installing the I/A Series G3 Serial Tunnel 2.0 Client, no control panel applet is created as with the earlier version of the I/A Series R2 Serial Tunnel Client.   To configure the I/A Series G3 Serial Tunnel 2.0 Client,  run the program C:\niagara\VserAx\vseraxConfig.exe.  If you need to frequently reconfigure this client, you can create a Window Start Menu shortcut or Desktop shortcut pointing to this file.

Issue Managing the address table in a Lonworks device Product Line EcoStruxure Building Operation, TAC IA Series, TAC Vista Environment I/A Series MNL TAC Xenta Third-party LON devices Building Operation Automation Server Cause A LonWorks device contains an Address Table which will hold a maximum of 15 addresses. Once this table is full, all bindings will only be able to use the broadcast setting which is not desirable. A Xenta 200,300 or 400 controller will have its first 2 address tables used with TAG 0 and TAG 1 binding. This leaves only 13 addresses for user bindings not the 15 addresses like other LonWorks devices. Resolution ​When you create a binding in LonWorks, you decide its behavior by selecting a binding profile. You either select a binding profile, or you use the default profile. There are basically three types of binding profiles: Acknowledged profiles Unacknowledged profiles Broadcast profiles Using an Acknowledged profile will consume one of the 15 available address table addresses on both the sending and the receiving device. The Unacknowledged profiles will only use one Address on the sending device's address table. Broadcast binds do not use an address but are not recommended. Use an acknowledged binding profile when the sending device should receive an acknowledgment from the receiving device indicating that the value of the bound variable was successfully sent. Binding profile Transmit timer Retry count Acknowledged Profile 96 ms 3 Acknowledged, Tx tmr 256, 3 retries 256 ms 3 Acknowledged, Tx tmr 256, 5 retries 256 ms 5 Acknowledged, Tx tmr 1024, 5 retries 1024 ms 5 Be careful of creating large, acknowledged fan-out bindings because they generate a lot of traffic, especially if the device of one of the recipients is offline.  Use an unacknowledged binding profile when the sending device should not receive an acknowledgment from the receiving device. Use this type when the value being sent is not critical and is of low importance to the control logic. Binding profile Repeat timer Repeat count Unacknowledged Profile   0 Unacknowledged Repeated Profile 48 ms 3 Unacknowledged Repeated, 5 repeats 48 ms 5 Use a broadcast profile when you do not want to use up an entry in the address table. The device address table has 15 available entries for bindings but the first entry is a reserved broadcast entry that all broadcast bindings can share. Binding profile Repeat timer Repeat count Broadcast Profile   0 Broadcast Profile, 5 repeats 48 ms 5 If no binding profile is selected, a default profile is used: Point-to-point bindings use the Acknowledged profile as default. Fan-out bindings use the Unacknowledged Repeated profile as default. Building Operation uses the broadcast profile as default when the device address table has run out of entries. If a point-to-point binding is changed to a fan-out binding, the binding profile is automatically updated to an Unacknowledged Repeated profile. If a fan-out binding is changed to a point-to-point binding, the binding profile is automatically updated to an Acknowledged profile.  This and other information about lon bindings is available on the online help guide Using a Lon Binding in StruxureWare Building Operation More information on the different tables used by each LON device

Issue Automation Server CPU usage goes between 80-100% even with few programs, trends or alarms. Product Line EcoStruxure Building Operation Environment AS Automation Server Cause Cause 1: BACnet into AS uses a lot of resources Cause 2: The AS has bindings from a point to a variety of places Also check out the AS CPU and Memory Loading Quick-Help video on the Exchange. Resolution Example Resolutions in order: The issue described is Functions as Design in StruxureWare Building Operation. The AS results with high CPU percentage with just one point from BACnet interface loaded; however, it had no effect on AS performance. Check the propagation of values. An example would be a Space Temperature which is required by the field bus, the BACnet interface, LON interface, etc. Make sure to properly disseminate this value so to avoid overloading the CPU.

Warning Potential for Data Loss: The steps detailed in the resolution of this article may result in a loss of critical data if not performed properly. Before beginning these steps, make sure all important data is backed up in the event of data loss. If you are unsure or unfamiliar with any complex steps detailed in this article, please contact Product Support Services for assistance. Issue 1. Cyberstation PC Windows Application Event Logs showing SQL errors about being unable to allocate space for each of the event tables. Similar to the below errors. Could not allocate space for object 'dbo.AlarmEvent'.'PK_AlarmEvent' in database 'ContinuumDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Could not allocate space for object 'dbo.ExtendedLogReservation'.'IDX_EXTENDEDLOGRESERVATION' in database 'ContinuumDB' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. 2. Controllers are online but unable to modify existing objects or create new ones. In addition; all events were not being logged to the database. This was seen by reviewing the AlarmEvent, ActivityEvent, AccessEvent, AlarmEvent, and ExtendedLog tables not having any new events being recorded at all. reviewing the distribution properties after performing tasks in Continuum showed no entries at all. Normally, user events initiated from the Workstation are shown in the distribution properties window as they occur. Product Line Andover Continuum Environment Continuum Cyberstation SQL Server Cause 1. One of the Database files is set to not grow with Autogrowth set to none. This stops any new data from being able to be entered into the database. One example of this is when the ContinuumDev file was modified by the end-user to inhibit its growth by changing this setting to none. Check all of the following databases files (both the DEV and LOG file) to ensure that they are all set to either autogrowth or to an adequate restricted value so that they are able to write new entries. ContinuumDB MSDB TempDB   2. The disk where the database resides does not have enough available disk space. Resolution 1. Change this database file growth setting to "by 10MB, unrestricted growth" or to an adequate restricted value. Use SQL Server Management Studio Express, see Move / Backup / Restore a database on a Single User SQL2005 Express system on where to get this if it is not already installed on your SQL Server. It is highly recommended to backup the ContinuumDB before attempting any changes to the database, steps on how to do this are in the above article. Start up SQL Server Management Studio, or in my example, Management Studio Express. Log in with your SQL SA password or windows administrator. Expand the server tree, expand the Databases tree. Right-click on ContinuumDB and select "Properties" from the menu; this will show the Database Properties window. Select the Files tab on the RH side of this window and you are now where you need to be to check the Autogrowth setting.   2. If the problem is due to disk out of space your options are; a) Make room on the disk, b) Shrink the ContinuumDB,  c) Install a larger disk in the machine.