Building Automation Knowledge Base

Issue Using STR-350 Bypass button as On/Off button in Classic Network Product Line TAC Vista Environment Vista STR-350 STR-351 Cause Sometimes on/off function is needed when using STR 350/351 to start or stop a device. Resolution Following the steps below to realize this function in Classic Network: Create a Menta file and Click "Add STR Module" in the Device Specification. In the Bits field of HVAC settings, change the value of the last 3 rd bits of the first line from "0" to "1". This bit is to switch the using Bypass button as on/off function on. Create an STRIN and STROUT module. Bind the STRIN to OccManCmd variable, while bind the STROUT to EffectOccup. Connect the STRIN to an real DO point to control the start/stop of device. But an calculation is needed because when the button is off, the value is 2 while the button is on, the value is 3 instead of simple 0/1. Also connect the STRIN to STROUT to make the output synchronize with the input, like the program below. You can also download the sample from here. For the application used in the LNS network, refer to the Using STR-350 Bypass button as On/Off button in LNS Network.

Issue I/A Series G3 weather service will not connect - error indicates java.net.SocketTimeoutException: connect timed out.  A browser on the same computer is able to access www.weather.gov without issue.  The application director output window displays the following ... WARNING [12:56:28 05-Dec-13 EST][weather] Updating forecast failed for Battle$20Creek java.net.SocketTimeoutException: connect timed out at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(Unknown Source) at java.net.PlainSocketImpl.connectToAddress(Unknown Source) at java.net.PlainSocketImpl.connect(Unknown Source) at java.net.SocksSocketImpl.connect(Unknown Source) at java.net.Socket.connect(Unknown Source) at javax.baja.naming.BIpHost$SocketFactory.open(BIpHost.java:271) at javax.baja.naming.BIpHost$SocketFactory.open(BIpHost.java:264) at javax.baja.naming.BIpHost.openSocket(BIpHost.java:129) at javax.baja.net.HttpConnection.connect(HttpConnection.java:263) at javax.baja.net.HttpConnection.connect(HttpConnection.java:238) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java:76) at com.tridium.weather.nws.NwsForecastReader.getFeed(NwsForecastReader.java:55) at com.tridium.weather.nws.NwsForecastReader.getForecast(NwsForecastReader.java:135) at com.tridium.weather.nws.BNwsWeatherProvider.updateReport(BNwsWeatherProvider.java:450) at javax.baja.weather.BWeatherReport.doUpdateWeatherReport(BWeatherReport.java:269) at auto.javax_baja_weather_BWeatherReport.invoke(AutoGenerated) at com.tridium.sys.schema.ComponentSlotMap.invoke(ComponentSlotMap.java:1357) at com.tridium.sys.engine.EngineUtil.doInvoke(EngineUtil.java:49) Product Line TAC IA Series Environment I/A Series G3 Enterprise Network Server ENC JACE Cause The connection timeout may be related to the proxy server.  By default, the weather service driver contacts the various weather.gov sites (alerts.weather.gov, graphical.weather.gov, etc.) directly as opposed to routing through the proxy server.  The connection times out as the proxy server is unable to route the request. I/A Series G3 (3.4 and higher) provides a service that can be added to the station.  The HttpProxyServer service is used to configure the station so that outbound web services know how to get through an outbound non-transparent proxy server.  The HttpProxyServer service located in the net module. Configure this service to the proxy server that will be routing. The user guide states the following. All services that make use of the bajax.baja.net.HttpConnection class will automatically roll over to using the proxy server once the HttpProxyService has been configured and enabled. The Weather Service is one of the services that is affected by this feature. Resolution Verify the updated weather modules are installed, see Weather information provided through the weather module in I/A Series G3 is no longer updating. weather-3.4.67.3 or higher weather-3.5.39.5 or higher weather-3.6.37.4 or higher To use this component: Open the net (Network API) module in the Workbench palette. Add the HttpProxyServer to the Services of the station. Configure the following properties in the Property Sheet view as required.     Status - This display only property displays the status of the Http Proxy Service. Fault Cause - This display only property provides an error message that indicates the reason for a fault. Enabled - This property has a true (enabled) and false (disabled) option. Server - This property provides a text field for entering the address of the proxy server you are connecting to. Port - This property is for specifying the port number for communicating with the proxy server. Exclusions - This text field allows you to designate addresses that are allowed to be contacted directly, therefore “excluding” them from having to be contacted through the proxy server. The default addresses in the field are typical addresses followed by a slash (/) and the subnet mask designation. Authentication Scheme - This property provides the following two options:      None - no authentication is required at the proxy server when this option is set.      Basic - basic authentication is required at the proxy server when this option is set. User - This is the login name to be used when authentication is set to Basic. Password - This is the password text that is to be used when authentication is set to Basic.

Issue Is there a template to help create the custom AccessFormat array? Product Line Andover Continuum Environment Creating a Custom Card, Access Format array for non standard Wiegand formats Cause As there is sometimes confusion on the way that the bits are counted from 0 or 1 and how to use a Plain English program to initialize the array an easy way to lay out the data would be useful. Resolution The attached Excel spreadsheet works as a template to enter the Access Format data. Click here to download Format Template.xls. Enter your required Wiegand format bit definition in the box at the top, then this will allow you to define the numbers to go in the AccessFormat array lower left, which automatically fills in the example program on the right. Also see: Setting up a custom Wiegand format access cardfor information on setting up an AccessFormat array. Determining Custom Card formats on Deciphering Custom Card formats. What is the range of Wiegand Card numbers and Site Codes I can use on Continuum? on maximum card numbers.

Issue TAC Vista SQL maintenance repeatedly fails. Not just once or twice, but on every attempt. Microsoft Management Studio View of error Vista Workstation view of error Environment TAC Vista 5.1.7 or newer. Cause The SQL maintenance feature was added to Vista in version 5.1.7, to regularly database defragment the database and prevent the follow-on effects of a fragmented database. This scheduled maintenance can fail for a number of reasons. Resolution Start by  taking a DSS writer server log using TACOS Tweak. Follow the steps below to do this. Goto the TAC Vista installation folder (C:\Program Files (x86)\Schneider Electric\TAC Vista 5.1.9 by default on 64-bit machines). Locate TacosTweak and double-click on it. Click on the "Category" drop-down box and select "DSS (Registry)". Locate the "DSS Server - Log Level" entry and increase the log level to "7" by entering the value in the value field and clicking the "Set" button. Locate the "DSS Server - Log file" entry and chose an appropriate path. Launch "TAC Vista Server Setup" and go to the SQL maintenance tab. Locate the "Run SQL Maintenance now" checkbox and check it. Click on "OK" or "Apply". Locate the DSS server log file and open it with a text viewer/editor. Search the log file for the following text "Maintenance Task - Starting" and check that the date time stamp is approximately when the "Run SQL Maintenance now" button was pressed. Examine the file carefully and follow the file line for line from this point until you reach "[ERROR] Fatal error : SQL Exception : Incorrect syntax near '('. NOTE: Contact Product Support Services if you are unable to interpret the log file or see another type of error than that described above. Once confirmed, launch Microsoft SQL Server Management Studio and follow the steps below: Locate the "taclogdata" database. Right-click on it and select "Properties"  Locate the "Options" tab and set the compatibilty level to SQL 2008 (or SQL 2005 if that is the installed version). Don't forget to set the DSS Server log level back to "5"!   A tool to simplify this process can be found here. Please note that this is not an official Schneider Electric utility.  

Issue How to place an order for more LNS credits to allow LNS plug-ins to work and to be able to commission more devices. Product Line TAC IA Series, TAC Vista Environment LonMaker NL220 LNS Cause There are two types of credits: Product specific credits like LonMaker and NL credits LNS credits   LNS LNS credits are assigned to the PC and when they reach zero, the LNS Server license goes into deficit mode. After 14 days the deficit mode will expire, at which time no LNS tools will be able to be used on that PC. To reverse the lockout, enough LNS credits must be ordered to cover the deficit and any additional nodes that need to be commissioned. Backing up, sharing, and restoring LNS databases can sometimes corrupt these LNS credits, which then prohibits you from launching any LNS plug-ins. For more help with corrupt LNS credits see Corrupted LNS Credits. LonMaker LonMaker credits are assigned to the PC. Both LNS and LonMaker credits are required, however when commissioning devices in LonMaker, LonMaker credits are consumed but LNS credits are not. Even though LNS credits are not consumed in LonMaker they are still necessary because certain LNS applications (i.e. TAC Vista System Plug-in) require them to operate. NL220 Each time a node is commissioned in NL220 it requires a NL credit and a LNS credit. NL credits are assigned to the NL220 dongle and can be used on other PCs in "MOVED" mode. LNS credits are also necessary in NL220 to operate certain LNS applications such as the TAC Vista System Plug-in.   To order more Echelon LonMaker credits see Ordering more Echelon LonMaker credits. To order more Newron NL220 credits see Ordering more Newron NL220 credits. Resolution To check the amount of LNS credits remaining on a PC go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard and look for Credits Available.   To order more LNS credits: Go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard In the box named Credit Order, type in how many credits to order, then click Next. Following the instructions at the top of the window, Click the Copy to Clipboard button to copy the PC key generated by LNS Server License Wizard. Click Cancel. Compose a new email and paste the PC key into the body of the email. Address the email to credits@echelon.com or your local Schneider Electric Buildings Business order department so they can place the order. Follow the instructions at the top of the email making sure to fill out all required fields. Once Echelon or the local Schneider Electric Buildings Business order department sends back an Application Key, go to Start > All Programs > Echelon LNS Utilities > LNS Server License Wizard. Click next and paste the application key into the field titled "Application Key". Click Finish.

Issue Effects of leap year with schedules and BMS Product Line Andover Continuum, TAC INET Environment I/NET Site Continuum Site Time, calendar, Gregorian Calendar Cause Leap year adjustment in calendar Resolution I/NET: I/NET will not be affected by Leap Year occurrence if DST and Time Sync is correct in the host computer. For Time Sync errors, please refer to Time Sync Error, Daylight Saving setup, please refer to Configuring Daylight Savings Time. Continuum: Continuum will not be affected by Leap Year occurrence to controllers or scheduling if the Cyberstation has the correct time. There have been no incidents in the past with regards to leap year. Leap year is no different than some months having 30 days, others having 31. More information on time sync of controllers check Time sync controllers to workstations. To sync Continuum to an external time clock read Synchronize Continuum system to external time clock.

Issue When opening LonMaker the LonMaker Menu list is not shown in Visio. Product Line TAC Vista Environment Echelon LonMaker 3.xx Microsoft Visio 2002, 2003, 2007, 2010 Microsoft Windows XP SP3 Cause Echelon LonMaker was not installed with Administrator rights or some of the default security settings have been changed. Resolution Older versions of Visio - Check the File Paths and Security Settings Open up Microsoft Visio on its own. Go to Start > Programs > Microsoft Office > Microsoft Visio. (Do not open up Visio by opening up the LonMaker project) Go to the Tools menu > Options and then select the Advanced tab. Click the File Paths button. (For LonMaker 3.1, go to Tools > Options > File Paths) In the Add-ons field make sure that the file path starts with DRIVE:\LONWORKS_PATH\LonMaker. The default path is C:\LonWorks\LonMaker. The path in the Templates and Stencils fields should DRIVE:\LONWORKS_PATH\LonMaker\Visio. The default is C:\LonWorks\LonMaker\Visio. The next setting to check is the Macro Security. Go to the Tools menu > Options > and then select the Security tab. Make sure that all of the below options are selected. Enable Microsoft Visual Basic for Applications Enable Microsoft Visual Basic for Applications project creation Load Microsoft Visual Basic for Applications projects from text Enable COM add-ins Enable Automation events   Newer versions of Visio - Check the File Paths and Security Settings Open up Microsoft Visio on its own. Go to Start > All Programs > Microsoft Office > Microsoft Visio. (Do not open up Visio by opening up the LonMaker project) Select "Options" on the left hand side of the window. Click on the "Advanced" section and scroll down to the bottom. Verify that the "Enable Automation events" box is checked. Click on "File Locations..." In the Add-ons field make sure that the file path starts with DRIVE:\LONWORKS_PATH\LonMaker. The default path is C:\LonWorks\LonMaker. The path in the Templates and Stencils fields should be DRIVE:\LONWORKS_PATH\LonMaker\Visio. The default is C:\LonWorks\LonMaker\Visio. Uninstall LonMaker and reinstall with the administrator account used to log into Windows. The following articles have information about another problem that can cause the same issue: Visio menu not displaying properly after installing Lonmaker 3.1 with Visio 2002  Visio will open but LonMaker menu is missing from the toolbar, the features are unavailable, or Error: "unable to launch visio with file lonworks.vst"  There are two other things you may try before uninstalling, that have solved the issue in some cases: Right-click any toolbar, Choose Customize > Toolbars tab, Choose the Menu Bar, Choose Reset Remove all registrations in the Tools menu, click Options, and then on the Advanced tab, click File Paths.

Issue Enabling XDriver on the first generation of controllers, 9200, 9400, 9940, 9900 including the enabling of TCP/IP Product Line Andover Continuum Environment Older Continuum sites Cause Connectivity to third Party devices using the old NCI or First Generation Controllers requires an updated file. Resolution For 1st generation controllers, a .upd file is needed to turn on the bit for the Comm port. There is 1 bit per port to enable X Driver then a second bit to enable IP X Driver support required for the Modbus TCP/IP driver. The same principle applies to the generation1, 9200, 9400 controllers.   These controllers have flash memory just for things like the Serial number, model num, & X Driver settings, even though the controllers have EEPROM's for the firmware   As far as loading these drivers using hyperterminal, apart from firmware, one can load the X Driver file/ code through hyperterminal if required, but easier to do through Cyber'.   These files which enable the Xdriver for the Comm port, and TCP/IP are available by filling out the Driver Request Form, then they will be emailed directly to the customer from the factory in U.S.   X Driver list (Search for 'Third Party Driver List') and Order Forms (Search for 'xdriver order form') are located on the Exchange Download site  Difference between first and second generation controllers, visit What is the difference between 1st and 2nd Generation X Drivers. For information on Physical Ports, visit What controller ports and physical standards are supported by the Modbus X Drivers?  For Second Generation Controllers, visit How to order a controller with or upgrade a controller to have XDriver support.

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