Issue Modbus TCP/IP Server is not an option when programming a Modbus Gateway in an Xenta Server. Environment Xenta 913 Xenta 7xx XBuilder Cause There are only 3 Modbus Interface configurations for Modbus in an Xenta Server. Modbus RTU Client ("Master"), Modbus serial line master on a network Server ("Slave"), Modbus serial line slave on a network Modbus TCP Client ("Master"), Modbus TCP client to a server or router on a network Modbus TCP Server is not possible. Resolution Modbus TCP/IP can only be configured to be a Client (Master) in an Xenta Server. A solution if TCP Server is absolutely necessary would be to use an IP to 485 converter, such as an EGX100, and use the RTU interface.

Issue How to use values form a modbus device in a Xenta 7xx menta program Environment TAC Xenta 731, TAC Xenta 721, TAC Xenta 711, TAC Xenta 701 TAC Xbuilder Cause Need to bring in values from a modbus device to a Menta application in the Xenta server. Resolution Create a PVR (or PVB,PVI depending of datatype of the signal you are bringing is) and make it public in the Menta application. Create a connection object in Xbuilder, connect the "from" to the modbus signal, connect the "to" to the PVR block. Now the value from the modbus device will be represented in the Menta application by the PVR block.

Issue When using the IC_LON Plug-in, an error is reported: Unknown SNVT Type: nn This indicates that the SNVT (Standard Network Variable Type) is not supported by the IC3-LON controller. Product Line Satchwell BAS & Sigma Environment Sigma IC-LON Version 1.E Cause The Sigma IC3-LON controller is designed to work with LONMARK Resource Files Version 11. However, not all SNVT types defined in this version are supported by the controller.  Resolution To resolve this issue: Verify Supported SNVTs Refer to the IC3-LON Release Notes to confirm which SNVT types are supported. Avoid Unsupported SNVTs If an unsupported SNVT is required, consider alternative approaches such as: Using a supported SNVT with similar functionality. Reconfiguring the device or network to bypass the unsupported SNVT. Firmware Reference See the attached document: 📎 Release_Note_4-05 Firmware_IC3-LON.pdf

Issue Drayton Theta II ES Optimiser and EC Compensator datasheets and technical documentation Environment Drayton Cause Datasheets Resolution Drayton Theta II ES Optimiser Datasheets Drayton Theta II EC Compensator Datasheets For sensor information see What is the resistance for the DOC, DRC, DSC and DLC sensors for a Drayton Theta II EC

Issue When attempting to log on to an Automation Server with Workstation receive error: Can not continue because server is offline or temporarily unavailable. Product Line EcoStruxure Building Operation Environment Automation Server  StruxureWare Building Operation Workstation Cause This error message indicates that the Automation Server can not communicate with the Enterprise Server that it was associated too.  The Automation Server has been associated to an Enterprise Server where a new default (StruxureWare) domain has been added / created. The image below shows a second domain that has been created and been set as the default, this can be seen by the tick box on the second domain entry. When attempting to use the default admin account (by leaving the Domain blank) the Automation Server attempts to contact the Enterprise Server to authenticate the user.  If the Enterprise Server is offline or you are working with a database away from the Enterprise Server then you will receive this message. Resolution Two possible resolutions exist for this: Re-establish the communication for the Automation Server with the Enterprise Server to allow authentication for the user attempting to log in to be verified. Log on with a known "Local" domain or admin account.    Note: The domain name is case sensitive, even the Local domain. Make sure to type the name of the domain with appropriate capitalization. In this example, when trying to login to the Local domain, typing "local" fails to login, where typing "Local" logs into the AS correctly.

Issue Replacement battery for the DC1100 / DC1400 Product Line Field Devices Environment DC1100 DC1400 Replacement Battery Warning Electrostatic Discharge Required: Always discharge static electricity from your person by touching metal prior to handling any hardware. Failure to do so may result in damage to devices. Cause Controller battery has failed. Resolution The battery lifetime will vary over a very wide range depending on use and temperature so cannot easily be predicted, but about 5 years under normal conditions, would be a guide. The battery in a DC1100 and a DC1400 is soldered to the underside of the CPU PCB. It is a 3.6V 150mAh NiMH battery. The factory part number is S2218121100 and the manufacturer’s part number is Varta 55615 603 940. Please Note: - Good soldering skills will be needed to replace the battery. The battery can be sourced from CPC Farnell Varta 55615603940 details at CPC Farnell

Issue How to use L-IP in Vista Classic network. Cannot service pin controllers under L-IP in Vista Classic network. Values in Classic network under multichannel L-IP are showing "Invalid Address" and "No such entity" Product Line TAC Vista Environment TAC Vista Workstation L-IP NIC852 Cause LOYTEC L-IP needs to be configured as a server and into the smart mode in order to be used in the Classic network. NIC852 needs to be used with LOYTEC L-IP in the Classic network. Resolution Configure L-IP as a web server (How to Configure Lonworks Network Interfaces to Communicate on the IP to a Loytec L-IP Router using the Echelon driver).   Configure L-IP into Smart mode. There are two ways to configure L-IP into smart mode.  Flip the DIP switch or using a serial cable (RS232). Flip the DIP switch to activate the smart mode. The dip switch is at the side of the L-IP next to the Ethernet port. L-IP DIP switch has seven switches.  By default, DIP switch 3 is down and the rest switches are up. Flip dip switch 2 down to activate the smart mode.   Use RS232 serial cable to activate the smart mode. Read more information in the LOYTEC L-IP User Manual Chapter 4.4.2.2   Configure NIC852 Open LConfig and go to NIC852 tab (Start/All Programs/LOYTEC Network Interface/LConfig). NOTE:  LOYTEC Network Interface package can be downloaded from LOYTEC website, called NIC-LOYTEC Network Interface Software X.X.X Make sure “Enable device” is checked Click on “CNIP Configuration”. Under “Device IP Address” use computer's address and use 1628 as Port number. Under “Conf. Server IP Addr.” Use L-IP’s IP  address and use 1629 as Port number.   Click “OK”. Click on “Test Device”, and should return the serial number   Add LIP as a LTA in Classic network. Right click on the Vista Server and choose “New->Device->Communication Port-LOYTEC” Name the LTA (for example: LIP).   Edit LIP in Classic network. Right Click on the LOYTEC L-IP (in this example the LIP LTA) just added and choose “Properties”. Under Communication Settings, click on the arrow and select the available NIC852.   Commission the LIP in Classic network. Right click on the LOYTEC L-IP just added (in this example the LIP LTA) and choose New > Device > LonWorks Network Name the network (for example: LNS Right click on the LonWorks Network just added (in this example the LNS network) and choose “Commission and Download” Select the LonWorks Network (in this example the LNS network) and click the “Start the Selected Operation” button (up-down arrow button on the top) Click “Continue” when asking for “Continue operation?” Operation successful message should be displayed.   Refresh (F5) the tree in the left panel in TAC Vista Workstation. The L-IP LTA (in this example the LIP LTA) and the LonWorks Network (in this example the LNS network) should turn green afterwards. Now the L-IP is ready to communicate in the TAC Classic network.

Issue Communication failures between MicroNet View and MicroNet Manager Interface(MNMI) devices. Product Line Satchwell MicroNet Environment MicroNet View HMI MicroNet MI connected via ARCnet or NCP LAN Cause Incorrect bit switch configuration on the MicroNet MI device. Resolution Cold Starting the MicroNet MI ⚠️ Caution: This procedure will erase all configuration data from the device’s EEPROM and restore factory defaults. Steps: Power On the Device Ensure the RUN LED flashes approximately once per second. Disconnect Communication Ports Unplug any connections to 9-pin plug 3 and 9-pin plug 4. Reset Switches Set all bit switches (S1) to the OFF position. Initiate Cold Start Toggle bit switch 8 ON, then OFF. No visible change will occur at this stage. Configure for Xenta 555 Direct Connection Set only switch 1 to ON; all others must remain OFF. Toggle bit switch 8 ON, then OFF again. Verify LEDs RUN, WINK, and MODEM LEDs should light up for ~1.5 seconds. RUN LED should resume flashing once per second. Set switches 1 to 4 to ON for compatibility with NCP/ARCnet I/O Server (MicroNet View v1.0+). 🔍 Note: This cold-start procedure differs from that of a controller, which only requires toggling switch 8. Refer to data sheet DS10217A for detailed specifications.

Issue LDAP (Lightweight Directory Access Protocol) Integration of G3 (Niagara) Users with Active Directory Environment I/A Series G3 (Niagara) LDAP Cause None Resolution The Enterprise server or ENC must be part of the site domain before setting up LDAP.  If DNS has been configured proceed to LDAP Configuration Steps.  For further information consult docLdap_3_1.pdf

Issue Converting I/NET Symbol Libraries to TGML Components Environment I/NET TGML Graphics Converter Cause Many users want to continue using the same graphic libraries they had in I/NET while in StruxureWare. The TGML conversion tool, will convert these libraries to TGML components. Resolution From Either I/NET or StruxureWare Workstation, open the I/NET graphics Conversion tool Select the Symbols check box on the right hand column Browse to the source and destination folders Select the files you wish to convert. Click Convert In Windows Explorer Browse to the destination folder. You can double click on each component to automatically add it to your "My Components" Component Library. NOTE: Be sure the TGML Editor is closed while you do this. Once you have finished this, open the TGML Editor and note that your My Components Library is now full. If desired, you can change the name of this library for sorting purposes or future exporting.

Issue Controller randomly goes offline and add entries in its error log indicating LAN_ERR_BUFFER_TOO_SMALL_ERROR and/or LAN_ERR_ALLOCATION_ERROR. Environment CX9680 ACX5740/20 Cause Typically this is caused by a problem with the link partner (hub or switch) or some kind of CAT5 issue. Resolution If you have other ACX controller on this switch that is working fine try swapping the ports (or move the controller to a different port) and see if the problem follows the port or the controller. If the switch is a smart switch that gives an error log, get the log from the switch and analyze it or send in for analysis. There is also a possibility that the NIC card in the controller is bad but that assumption can only be made after everything else has been eliminated.

Issue On December 13, 2012, the certificate verifying the authenticity of the Schneider Electric I/A Series G3 Workbench Applet (wbapplet) expired. Users will see the following error in their browser when accessing a station that is using a version of the wbapplet.jar with an expired code signing certificate: Environment Niagara G3 Cause When accessing an I/A Series G3 station through a web browser using a WbWebProfile, the web browser runs Workbench within a Java applet. To enhance security, this applet is 'signed' using a code signing certificate. This ensures that the applet has come from a reliable source and can be trusted to run with the proper permissions. Certificates used to sign applets are issued by a Certificate Authority (CA). Each code signing certificate issued by a CA has an established expiration date, with the maximum expiration being two years. Once this expiration date has passed, continuing to use a Java applet with an invalid certificate will result in warning messages within the browser. The applet will only be allowed to run after the user has acknowledged the warning and granted approval. Resolution An updated certificate is available in the new wbapplet.jar, available from The Exchange Download Center. This file will need to be added to the Enterprise Network Server, as well as on any ENCs that will be accessed from a browser. This file is for all released versions of TAC I/A Series G3 and is valid until March 30, 2015. Download wbapplet_March_2015.zip. Extract the wbapplet jar file  Click and Download The WbApplet Installation Guide. Note: Updated WbApplet files are available as part of upcoming Niagara 3.5 and 3.6 maintenance builds, as well as being from the Source website. In 3.7, wbapplet.jar is integral to the web.jar and contains an up to date certificate.;

Issue What is the limit of the number of Controllers that can be in a Continuum System? Product Line Andover Continuum Environment Continuum Cause Want to know the theoretical and practical limits to how many controllers can be on one system. Resolution There are certainly some logical limits to how your Netcontrollers are addressed and identified in the system but for all intents and purposes you are only restricted by the IP Address. Netcontrollers Logically, you can have Netcontrollers addressed from 1 - 190 - so the maximum you can have in a "logical" Network is 190 Netcontrollers. However, the number of Networks you can have in a Continuum Database is only restricted by the Database itself - effectively infinite. See the article below on logical Networks. How many logical networks can be created on a Continuum system? This restriction is only for Netcontrollers defined within the Infinity side of the Continuum Database and does not apply to third-party BACnet controllers. Field Controllers (b3 / i2) There is a definite limit to the number of subnet (Infinet or MSTP) controllers that can be strung off of a given bCX or Netcontroller. As a general rule, each comm port can support up to a maximum of 127 subnet devices. Of course this does depend on the device being used, the amount of nodes it is enabled for, and the physical installation. The number of nodes purchased does correspond to the total number of i2 or MSTP controllers that can be on that bus. Example: If you have a bCX1 with 32 MSTP nodes this means that a total of 32 MSTP devices can be on this MSTP network and the following architecture is valid. bCX1 with bLink; (segment1) node1 to node16. (segment2) node17 to node32. If we look at a Netcontroller or Netcontroller II, these controllers have two RS-485 comm ports that can be used to support Infinet subnet controllers, up to 127 on each port and a maximum of 254 off the one controller. Now the controller would need to have both ports enabled for 127 nodes and considerations made for the amount of traffic this number of controllers would require. Similarly, the bCX1 (BACnet) will support up to 127 nodes. One thing to note is that this also includes repeaters if they are used to extend your network or star the MSTP. The general rule for the number of devices on an MSTP segment is a maximum of 32 nodes, this dependent on the network complying with MSTP installation guidelines for termination, distance, cable type, and that each node is a full load RS-485 transceiver. In the case of our BACnet controllers, they use a 1/4 load transceiver so given perfect network conditions it is possible to have 127 b3 devices on the same MSTP network segment. Even though this is possible, it is always good practice to use a b-Link repeater and a max of 32 devices per network segment - this also helps to segregate the devices for troubleshooting as well. Total Point Limits Other than with a Cyberstation with an I/O limited Security Key, I'm not aware of any limits to the number of points that can be created in a Continuum Database; this would be limited to the size and resources of the Continuum SQL Database. Consult the following article that has a spreadsheet to help estimate the size of your Continuum Database. It could also help to estimate your SQL requirements: Continuum Database Sizing and SQL Server selection

Issue When proportional 0-10Vdc type valve actuators are used with a SE8000 room controller, the actuators behavior is inconsistent. Environment SE8300 SE8350 SE8600 SE8600 Cause Some valve actuators e.g. wax filled (thermic type) have a high input impedance e.g. 100 Kohms. When connected to a SE8000 room controller, the actuators operation may be sluggish or may never operate. The SE8000 has a maximum output of 5mA when set to proportional control, using actuators with high impedance, the SE8000 room controller fails to recognise there is an actuator and does not drive it. Resolution A burden resistor can be fitted to draw some current from the SE8000 room controller because the actuator's impedance is too large. The burden resistor needs to be large enough not to affect normal use, but small enough to draw a current from the SE8000 room controller. Using ohms law: Valve actuator @ 100 Kohm SE8000 UO output is 5 mA, maximum Vdc output is 10 Vdc. Minimum size of burden resistor: 10 Vdc/5 mA = 2 Kohm. It may be necessary to increase the size of the burden resistor e.g. 10Kohm. The burden resistor is then installed between the signal ground and the signal, either at the controller or the actuator end. Test the actuators for correct operation.

Issue Unit Conversion Exceptions Unit selection of 'bar' defaults to N/m 2 unit Units are not displaying unit as selected in the properties Product Line EcoStruxure Building Operation Environment StruxureWare Building Operation 1.2 and above Cause Building Operation supports both the SI metric system and the US Customary System for units of measurement. The operating system regional settings on which WorkStation is installed determine whether SI units or US Imperial units are displayed. The conversion between the two measurement systems is managed automatically. For example, the temperature 42,82 °C is stored in Building Operation. A WorkStation on an operating system with the US Customary System converts the temperature and displays it as 109.08 °F. To display the original unit of a value in WorkStation, open the Properties pane for the value and go to the Unit selection dialog box. As part of this process some units selected, default to a default display unit, and not what was originally selected.  For example, selecting the pressure unit 'bar' when configured in a SI regional setting will display by default the unit 'N/m 2 ' and not 'bar' as selected.  This functionality is as per design but can be altered by using the Unit Conversion Exceptions feature. Resolution First reference Adding a Unit Conversion Exception on the Building Management WebHelp site.    In the release version 1.2 and above there is a feature that allows the operator to create unit exceptions, called Unit Conversion Exceptions.  This is located under the Domain folder and allows various conversions for different domains.  The steps below indicate how this is achieved. Locate the Unit Conversion Exceptions under the required Domain The Unit Conversion exceptions are now displayed in the Workspace.  The Add remove buttons are located at the bottom of this workspace Add the Configured unit, which is the selected unit for the variable you wish to be converted Then change the SI Display Unit and / or US Display Unit to the desired unit you wish the configured unit to be displayed / converted too Save these changes and confirm that it is now displayed in the desired unit.  In some cases you may need to log out and then back in for the changes to be applied. Online Web Help is also available here: If your system is based in US region then you can default you measurement system to US as per Metric vs. English (Imperial) Operating System.

Issue TTS 100 Series Thermistor Sensor Environment I/NET Seven Site Cause Conversion coefficient is for a Thermistor for a particular controller, and can it be used with the new controllers such as MRs/Motorola and HID/Dorado card readers Resolution TTS100 SERIES THERMISTOR SENSORS Dale 1M1002-C3 Curve 1 Product Support Services continues to get calls asking what the conversion coefficient is for a Thermistor for a particular controller, and can it be used with the new controllers such as MRs. Therefore we have consolidated into this Tech Tip the variety of ways the Thermistor Series Temperature Sensors can be used with Schneider Electric's current family of controllers, including wiring, controller input range and conversion coefficients for both degrees Fahrenheit and Celsius. It makes for a great quick reference. Keep it handy.   MR123-210(A), 430(B), 032(C), 400(D) "I/STAT PORT ONLY" MR88 (F), MR632 (G), MR160 (H), MR88R (K) "I/STAT or UI Inputs" Resolution Counts Input Range Read Range M Slope B Intercept Temperature Range Span 0 - 255 0 - 5 vdc 0 - 5 vdc 0.018 -148 -40 - 176°F Normal   0.01 -100 -40 - 80°C Normal 102 - 204 2 - 4 vdc 2 - 4 vdc 0.018 -148 32 - 90°F Narrow   0.01 -100 0 - 32°C Narrow   MR55 / 55X (J) Resolution Counts Input Range Read Range M Slope B Intercept Temperature Range Span 0 - 255 1.5 - 4 vdc 1.5 - 4 vdc 0.018 -148 25 - 113°F Normal   0.01 -100 -4 - 45°C Normal   Look-up Table #1 if wired to the I/STAT Port Look-up Table #2 if wired to one of the Universal Input -Plug a 10K in B slot Red - Signal In, Green - Ground I/NET 7700 SERIES CONTROLLERS   Accuracy: +/- 0.2 DegC @ 25 DegC, Nominal Resistance: 10,000 Ohms @ 72 DegF Operating Range: TSS100WJ, D1, D2, I1, I2, S1, S2,SP, SS: 32 to 158 DegF ( 0 to 70 DegC) TSS100OA: -4 to 158 DegF ( -20 to 70 DegC ) TSS100W: 32 to 122 DegF ( 0 to 55 DegC) Power Requirements: 5 Volts excitation via 10K Ohm Resistor Negative Temperature Coefficient ( Dale 1M1002-C3 Curve 1 )   *7716 PCU, 7718 PCU, 7728 I/SITE I/O, 7756 PCU (Upper Board Only) Resolution Counts Input Range Read Range M Slope B Intercept Temperature Range 0 - 4095 0 - 5 vdc 0 - 5 vdc -0.1 300 -40 - 230°F   -0.05 150 -40 -110°C   819C/V (10K in B slot) Red - Signal In, Green - Ground, DegF / DegC - See LUT Chart *7716 PCU Rev. J boards ONLY   7756 PCU (Lower Board Only) Resolution Counts Input Range Read Range M Slope B Intercept Temperature Range 0 - 32767 0 - 10 vdc 0 -5 vdc 0.018 -148 -40 - 230°F   0.01 -100 -40 -110°C   6553.5C/V (10K in B slot) Red - Signal In, Green - Ground, DegF / DegC - See LUT Chart Thermistor Sensors Look-up Table Chart   7716, 7718, 7728, 7756 (Upper Board) Fahrenheit Thermistor   Celsius Thermistor # Count Adj Count   # Count Adj Count 1 153 521   1 153 601 2 344 1062   2 344 1202 3 816 1604   3 816 1804 4 1245 1875   4 1245 2105 5 1827 2146   5 1827 2406 6 1914 2182   6 194 2446 7 2003 2218   7 2003 2486 8 2048 2236   8 2048 2506 9 2093 2254   9 2093 2526 10 2183 2290   10 2183 2566 11 2274 2326   11 2274 2606 12 2366 2361   12 2366 2646 13 2457 2397   13 2457 2686 14 2548 2433   14 2548 2726 15 2637 2469   15 2637 2766 16 2725 2505   16 2725 2806 17 2812 2541   17 2812 2845 18 2897 2577   18 2897 2885 19 3209 2756   19 3209 3084 20 3577 2934   20 3577 3283 21 3923 3293   21 3923 3681   7756 (Lower Board) Fahrenheit/Celsius Thermistor # Count Adj Count 1 128 32846 2 2048 20039 3 4096 17584 4 6144 16185 5 8192 15180 6 10240 14373 7 11264 14016 8 12288 13681 9 13312 13363 10 14336 13058 11 15360 12191 12 16384 12474 13 17408 12191 14 18432 11910 15 19456 11629 16 20480 11346 17 21504 11058 18 22528 10762 19 23552 10455 20 24576 10132 21 28624 9412 22 28672 8514 23 30720 7161 24 32640 2438

Issue When installing Building Operation software i.e. License Administrator, Workstation, etc. the following error may show: "This software requires .NET Framework version 4.7.2" Product Line EcoStruxure Building Operation Environment Building Operation installers Microsoft .NET Framework Cause Building Operation requires .NET Framework 4.7.2 or greater to install and function Resolution Most Windows machines have the latest version of Windows installed and updated for security reasons. If for some reason an older version of Windows hasn't been updated then it may show the error until .NET has been updated.   Here is a Microsoft article that shows how to determine what version of the .NET Framework is installed on the Windows PC. How to: Determine which .NET Framework versions are installed There are several methods, this is the registry method:   Windows 10 version 20H2 includes 4.8 as part of its default components. It is recommended to upgrade Windows to this version or greater.   Once the version of .NET Framework is upgraded, the error dialog will no longer appear

Issue How to use the Continuum Report object Product Line Andover Continuum Environment CyberStation Cause Instructions are needed to use the Continuum report object Resolution CyberStation provides a graphical suite of features, called Reports, that allows you to gather, view, compare, and distribute point-object data values, locally or remotely, manually or automatically, from virtually anywhere in your Continuum system.  Using CyberStation Reports, you may collect and filter data from a multiple number of dynamic building-control data sources (including extended logs) then instantly display this data in graphical bar charts, pie charts, trend charts, or columned text charts. With reports, you can: • Display report data using one of several data formats • Display two or more reports simultaneously • Modify report configurations on the fly while viewing them • Schedule reports to run automatically at a specified time • Save a report to a file, manually and/or automatically • Email a report, manually and/or automatically • Print a report   Basic Report Example   1. Create a Report  In Continuum Explorer, right-click on a folder or device, and select New, then Report, from the popup menu.     Type in a Report name and Select the Create button   2. Source Page a. Select a Data Source from the drop-down (Tables from the database)  b. Select a Report Type - these change based on the data source c. Select a Chart Type   3. Configure Columns Click on the Configure Columns button in the middle of the Source Page   a. Select the Columns needed in the report b. Use the drop-down to select how the report will be sorted   4. Filter Tab From the Source Page, select the Filter Tab a. The Log Filter and Time Interval options allow for Time filtering b. Member Objects - Click Add to specify which Fileds/Attributes will be included on the report   5. Output Tab From the Source page select the Output Tab The settings on the Output Tab will reflect how the report appears and how it is to be viewed   For detailed instructions for standard(Not Add-On) Continuum reports, see Chapter 14 Reports in the Continuum Configuration Training Manual. This manual is not available online, it is distributed as part of the Continuum training courses.

Issue Unable to open servers in PCT from Webstation. Product Line EcoStruxure Building Operation Environment Building Operation Project Configuration Tool (PCT) Cause The incorrect IP address or ports used in the browser. Resolution Select the server from a project. Expand the Properties tab from the right-hand sidebar Record the Engineering IP address and HTTPS port number Open a browser and enter "https://{IP address}:{port}" or ""http://{IP address}:{port}"  

Issue Error: 8000401a Retrieving the COM class factory for component with CLSID {2B768E20-89F2-11D2-99FD-00104B6D2299} failed due to the following error: 8000401a.Server process could not start because the configured identity is incorrect. Check username and password. (Exception from HRESULT: 0x8000401A).Code: -2147467238 When starting Vista Server, a fatal error happens: TACOS: COM Initializing failed, error code: -2147417831 Product Line TAC Vista Environment Remote desktop TAC Vista Windows 2008 Server or Windows 7 Cause When using Remote Desktop with a Windows 2008 Server and disconnecting, the TACOS process may end up in a "sandbox" and can not be reached by other people trying to log in remotely. Or, the Vista Server can't be started. Resolution The attached Tacos RDP Disconnect contains scripts that will disconnect a Remote Desktop session back to the physical session if tacos.exe is running. If tacos.exe is already running on the physical session or is not running at all, nothing happens.