Issue There are many situations that a remote computer wants to monitor and control local Vista values. C/S construction (Client/Server) and B/S construction (Browser/Server) are the two solutions for these situations. Environment Multi-PC environment Vista Cause In many cases this application is needed. Resolution The C/S solution for Vista is Remote Workstation and Vista Server. On the client computer, only the Vista Remote Workstation software needs to be installed. Then it can connect to the Vista Server on the server computer. The Remote Workstation software can be downloaded from here. The B/S solution for Vista is Webstation and Vista Server. On the server computer, Vista Webstation software needs to be installed. Then on the client there is no need to install any software. Just open the IE browser, and type the IP address of the server computer, all the content in the Workstation of server computer can be shown in the client computer. The Webstation software can be downloaded from here.

Issue After a new Menta application was downloaded through Vista the IO modules indicated offline with a fast flash of the green indication light. Environment Vista 5.x.x Cause The Xenta controller is using too much workspace memory. This can be seen from the memory allocation in Menta. Resolution The TAC Menta Technical Manual describes work area as the following: Work Area - Data created when executing the application program. For example, output status and time schedules.   Removing some of the time schedule holiday chart links will reduce the work area memory usage. Once this memory is in a positive free figure, the application can be downloaded and the IO will return to normal operation.

Issue How to find the IP address information on a PC? Product Line EcoStruxure Building Operation Environment Windows Operating Systems Cause Need to identify the IP address of the workstation (PC). Resolution For a Windows 95/98 PC, go to a DOS screen and run WINIPCFG. For a Windows including and after Windows7 run a COMMAND window and run IPCONFIG.  

Issue When the fan speed is set to level II on the STR the fan enable turns off on the 121 fc controller Environment 121 FC Firmware 1.26-11 Cause Some units of the STR106 and STR107 may have compatibility issues with the TAC Xenta 121-FC unit, concerning the manual Fan speed wheel function. bvfbfbanxdddcvSome units of the STR106 and STR107 may have compatibility issues with the TAC Xenta 121-FC unit, concerning the manual Fan speed wheel function. Resolution Upgrade the 121-fc to 1.26-14 or above. Here is the link with the upgrade files: Ecobuildings

Issue When opening an XBuilder project with Menta objects referenced to Menta Library objects, the references are lost and all Menta objects are showned as disconnected from the library. Environment TAC XBuilder 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. Cause For some reason, the library definition in the project has become corrupted. Resolution 1: Browse to the XBuilder project file (*.xbp*) 2: Edit the file with notepad or similar 3: Search the file for all instances of "MENTALIBOBJ" 4: If the node doesn't have anything in "GUID=" that's the problem 5: For all instances that are wrong, copy the "MentaObjLibId" value to "GUID" 6: Save the file, and reopen the XBuilder project

Issue TAC Vista SQL transaction log file is very large and won't shrink. Product Line TAC Vista Environment Vista 5.1.X SQL server 2005, 2008 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. Cause An SQL transaction log consists of a number of virtual files whose size is defined in the database's properties. Once the virtual file is full, the next virtual file in sequence is used. These files are an essential part of the 'rollback' functionality, allowing SQL to roll back a transaction if for some reason (i.e. disk space runs out)  it can't be completed. With the simple model, the virtual file will be marked as reusable once the transaction(s) contained within the file is complete. So a database may look like this, with the '2' in the status column indicating that the virtual file is still in use: With the recovery model set to a simple, a shrink operation will remove all the virtual files that aren't in use. With the full or bulk-logged recovery model shrink operations behave differently. A full description of this can be found here, but the most important point is that a backup of the transaction log must be made before any virtual files can be marked as reusable.  A shrink operation may not remove all virtual files straight away either so multiple shrinks may be necessary to remove all unused/expired  Resolution Run the following queries: DBCC loginfo This will show the file structure of the SQL log file. BACKUP LOG taclogdata TO DISK = 'c:\taclogdata.bak' Run DBCC loginfo again. Check to see if there is any change. Run a 'Shrink' command (via SQL Management Studio) and then run DBCCloginfo again. Check the size of the database: sp_helpdb taclogdata Keep repeating the process until the database logfile is as small as it can be.

Issue When many trend logs are linked to the same time object for emailing via a Receiver Group, some of the trend logs may not be sent. Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 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. Cause The Xenta Server cannot send more than approx. 50-60 simultaneous emails before some are lost.  The limit appears to be dependent on the size of attached trend logs and the number of addresses in the Receiver Group list. Resolution For a single email address, split the trend logs into groups of no more than 40.  Link the logs in each group to a different time object and stagger the times at which they are sent.  If the Receiver Group definition contains multiple email addresses, reduce the number of trend logs in each group accordingly.

Issue Trend logs are not being saved to SQL after upgrading the SQL database. There are no error messages and Vista can read old (pre upgrade) values from the taclogdata database. The insertlogvalues keeps growing. Product Line TAC Vista Environment Vista 5.1.X SQL 2005 or 2008 server with a database that has been upgraded to layout 2 (the new schema used from version 5.1.7). 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. Cause The database schema is out of date. The database schema is a blueprint of how a database will be constructed. Resolution Shut down Vista. Go to services and stop the TAC DSS writer service. Right-click on My Computer (Computer in Win 7 and Win Server 2008) and select manage. Locate services in the console that opens up. Locate the TAC DSS Writer service, select and then click on stop. This service is responsible for writing events and trend log data to the SQL database. Update the database schema. Open Vista sever setup and locate the SQL server tab. Click on the Custom radio button (if not already selected) and then change the name (e.g. add "_1" to the end of the current name) of the database in the SQL Server Name field. Click on Apply, OK and  then Yes to create the new database. Once complete, change the name of the database back to the original name (or click on the Typical radio button if using default settings) and click on Apply. A message will appear "Log database found but needs to be reconfigured. Reconfigure Log database?". Click on Yes. The database schema should now be updated. Right-click on My Computer (Computer in Win 7 and Win Server 2008) and select manage. Locate services in the console that opens up. Locate the TAC DSS Writer service, select and then click on Start. This service is responsible for writing events and trend log data to the SQL database. Check to see that the logs are now being written to the log database. It may take some time to process the backlog.

Issue How to restore and view a Log backup without overwriting current database How to view backed-up events without overwriting current database How to restore a SQL database  without overwriting current database Environment TAC Vista 4.3 and higher running a typical (not custom) SQL. 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. Cause The event and logs will be backed up as a SQL backup file. This means that restoring a backup on the same PC that it was made on replaces the SQL database.    Resolution To view old data, restore the log database backup file on a different PC that has the same TAC Vista database on it. Create a copy of the TAC Vista database (or make a backup) Copy / restore the database to a computer that is running the same version of TAC Vista Go to the Server application and log in Go to File > Restore Log Database Browse in the backup file, the path should be filled in automatically

Issue taclogdata_log.ldf file is too big Environment SQL 2005   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. Cause Fail to perform frequent SQL DB maintenance   Resolution To Shrink the LOG file (.ldf) follow the procedure. Connect to taclogdata.mdf using SQL server management studio. Run the following command: dbcc shrinkfile (taclogdata_log,100,truncateonly)   This will reduce the size (taclogdata_log.ldf) to 100 mb. Note : You can get the logical file name for the log by running the following select statement: (select * from sysfiles) The following are the query results: 1          1          6400    -1         6400    2          0          taclogdata         c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata.mdf   2          0          2624    268435456      1280    66        0          taclogdata_log  c:\Program Files\Microsoft SQL Server\MSSQL.2\MSSQL\DATA\taclogdata_log.LDF   If the database has the truncate log checkpoint turned off, then the transaction log file will be shrink to the target size only when the transaction log is backed up. OR If the truncate log on checkpoint is turned on then go to Enterprise Manager - all tasks - and click "truncate log". This will shrink the file down to the target size and will release all the unused space to the Operating System.

Issue Dependencies for Vista Server running as a service Product Line TAC Vista Environment Vista Server 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. Cause The Vista server can run into issues if it starts up before other services. Resolution Ensure that Vista Server does not start up before Aladdin Privilege Server by making some changes to the registry. Select the start menu, select run, and type “regedt32”. Once the program opens you should browse to the following path: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\TACOS\ The key named DependOnService should by default contain the value RPCSS. To add a dependency to this service just modify the value of the key and add the name of the service you wish to start before this one. In the case of Aladdin Privilege Server just add the text “Privilege Win32 Server” to the registry key. Close the registry editor and the dependency will be visible in the services properties window for TACOS. Note: If you need Vista to start late in the boot cycle but you do not have a specific service dependency, as explained above, then choose one of the services which startup last as the data value for the value "Depends on Service". Services commonly selected are Spooler and Messenger.

Issue A system Format of the file system will remove all files to return device to a factory condition. Product Line TAC Vista Environment TAC Xenta 5xx TAC Xenta 7xx TAC Xenta 9xx Xenta Server 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. Cause A need to reset to factory defaults exists Resolution These actions clears the filesystem and remove all files and information in it. Make sure you have IP and any other information you need to save from the file system. All files and configurations will be lost. Access Xenta using a serial interface via the RS232 port and a HyperTerminal program. obtain a connection to the dsh> prompt Type format. Wait for formatting to be ready , then enter command setip to enter DHCP enable ,ip-address , subnet mask , default gateway , DNS , local name. Default user/password will then be root/root. Remember to change password. Restart system to accept new ip-address. Install Xenta using the install kit. Use ftp transfer and alternative A (We have just formatted the system). Download WebTool project and user defined files. Update bindings using LonMaker.

Issue Downloading new NXE or APB files using NL220 Product Line TAC Vista Environment NL220 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. Cause Downloading new or old firmware versions into application specific controllers. Resolution Before performing this update, make a backup of the NL220 project. In case something happens and the configuration parameters are lost, there will be something to reference. Go to extranet and download the latest NXE and APB files. In NL220, right click on the controller to be upgraded and go to Network > Upload configurations. This will update the database with the current configuration in the controller.   Next, right click on the controller again and go to Network > Replace. A box will open that is titled Commissioning a node. The option "Upload configuration from old node if present" should be checked. This will insure that the values in database are current with the controller. Under Configuration download, "Download all known database values" needs to be selected. This will download the configuration parameters back into the controller once the update is complete. Finally under Template, "Download a program to the node" should be checked. The file that was downloaded off of extranet earlier can now be browsed in. Note: The option ‘Keep current configuration on node’ is misleading. By selecting this option it will not download parameters to the node. So when you download the new APB file, the controller will retain the configuration parameters found in the APB file not what was originally on the node.   Click Continue

Issue Failed to read events from the event log database. Product Line TAC Vista Environment TAC Vista Workstation 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. Cause This error is sometimes displayed upon login to the TAC Vista Workstation. It indicates there is a problem with the connection between the Vista Server and the SQL database that stores event data. Resolution Before making any further tests, make sure you have MSXML 4.0 SP3 installed and then check if it works. It can be downloaded here: https://www.microsoft.com/en-us/download/confirmation.aspx?id=15697 The first thing to check is the SQL connection. Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab In the lower right-hand corner of the tab, press the Test Connection button. If it pops up a window that says "Connection test succeeded!" then your SQL connection is okay. If it fails the connection test, check the instance name. If you are using default settings it should be: SQL Server name: PCname\TACVISTA or (local)\TACVISTA Log database name: taclogdata If these are set correctly and the connection still fails, one method for reestablishing the connection is to uninstall/reinstall the Vista software. Make sure SQL Server Agent is running. Right-click on My Computer and select Manage Navigate to Computer Management (Local) > Services and Applications > Services Find SQL Server (TACVISTA) -- assuming the default SQL instance is being used. Make sure the service status is running.  Start the service if needed. If there is no problem with the SQL connection, check the Server object's Network Master. In Vista Workstation, right-click on the Vista Server object and select Properties On the General tab, in the Network pane, check the Master: name In a one-server network, the Network Master must be set to the Server object name. Check for queued files in the $queues folder Navigate in a Windows Explorer window to the Vista Database. (If you are unsure of the location, you can verify it in the TAC Vista Server Setup Vista Database tab). Go to the $queues folder Look inside the insertevents and insertlogvalues folders. Are they empty or are they consistently growing with files? This is where data is stored temporarily before it is written to the SQL database. Having queued files is not necessarily a sign of a problem. However, if there is a connection problem, these folders will continually grow in size without older queued files being written from the folder. In the case of the error "Failed to read events from the event log database", it is possible that a queued file is causing the error prompt and that deleting it will fix it. If the data is not of dire importance, delete all the files inside both of the $queues folder. For more information see An efficient method for deleting all queued files in the $queues folder. Reconfigure the log database Open the TAC Vista Server Setup In version 5.1.3 and prior: Start > Programs > TAC > TAC Vista Server X.X.X > Server Setup In version 5.1.4 and later: Start > Programs > Schneider Electric > TAC Vista Server X.X.X > Server Setup Go to the SQL Server tab Change SQL configuration from Typical to Custom Change the Log database name Hit Apply. It will warn you: "TAC Vista integrated SQL backup/restore function will not be available in custom configuration." Hit OK. It will then warn you: "No log database was found on SQL Server. Create and configure a log database?" Hit Yes.   At this point, if no backup features are necessary, and the error has cleared, this is a viable solution. It is not, however, recommended to maintain a site without any log backups. The next step would be to switch the Vista Server Setup SQL configuration back to Typical. Hit Apply. You will be warned: "Log database was found but needs to be reconfigured. Reconfigure log database?" Hit Yes.   After reverting to typical SQL settings, the error should clear. If it has not, it may be time for some database management. Performing Database Maintenance Follow the steps in the article Performing database maintenance with Vista 4.5.0  to set up a log and event backup and to clean up old data. Schedule a backup to occur (now or soon after) The next time you log into Vista Workstation, the error should be cleared. If the error is sporadic, it could be the event viewer has too many events If the error only occurs when logging in to Vista Workstation, and doesn't happen every time, it could be that too many events are being brought into the Event Viewer on login. All events specified in the filter for the event viewer are uploaded to the Workstation. If too many events are specified, problems occur. In Workstation, go to the root TAC Vista folder Right-click $Eventview and select properties Go to the Date and Time tab Set the Time period to Last 1 Hour(2) instead of Last 1 Week(s), which is default Check the Windows Event Log If all else fails, check the Windows Event log for more information about the error. Checking this may provide you with the answers you need, or at least give you more information to provide to Product Support if you need further assistance. Instructions available in Viewing, Saving, Sharing Windows Event Logs for Troubleshooting Purposes. Right-click on My Computer and select Manage Browse to Computer Management (local) > System Tools > Event Viewer > Application Look for Type Error events with Source Vista. This may help you determine the source of the error.

Issue When doing a LonMaker resynchronization, the operation fails on a certain subsystem or when doing a commission on a controller in Lonmaker an error is displayed: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102) Environment LonMaker 3.X 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. Cause If re-commissioning or downloading and commissioning a controller in LonMaker fails or times out, this issue may crop up. LonMaker assigns the desired neuron ID to a temporary device while performing either of these commands, and if the operation fails, that temporary device will get stuck in the database with the same neuron ID as the controller the user was working on. A successful resynchronization will bring this "phantom device" to light where it can be deleted, but if it is the resynch that is failing, the steps below detail how to remove a neuron ID from a device in the LNS database so it can be deleted. Resolution Try to do a resynch command in LonMaker to get the temporary device to show itself on the Visio drawing. If this works, then the temporary device will show up with a randomly generated alpha numeric name on the same page as the controller you were trying the commission or download. After the resynch completes, delete the device from the page and repeat the commission or download. If the resynch operation fails with: Attempt to assign a neuron ID that is already in use by another device. (Subsystem: LNS, #102), continue. Because the temporary device is in the LNS database, but not on the LonMaker Visio drawing, manual manipulation of the LNS database is required to remove this object. This is done with the LNS Object Browser. First, shut down LonMaker, then click START and chose RUN in Windows and type lnsobjectbrowser and click ok. The Startup Preferences are shown. Set the Client/Server Communication to Don’t change and the Local Network Access to Engineering Mode and then click Ok. After choosing settings in the Startup Preferences menu, the LNS Object Browser is displayed. Press F8 to take the object browser out of read only mode. Browse to the following: ObjectServer/Networks/Your_Network_Name/Systems/ Your_Network_Name/Subsystems/All/AppDevices. Note: Double-click to open each object. Within the APPDevices menu you will see the temporary device with the large alpha-numeric name. Double-click this device to get its properties in the right hand window. Double-click on the NeuronId line in the properties pane of this device and manually set the Neuron Id to 000000000000 (12 zeros) and click Ok. Exit out of the LNS Object Browser and re-open the LonMaker database. Perform another resynchronization of the database, and the suspect temporary device should now show up on the LonMaker drawing. Then, delete that device and re-attempt your work on the original controller.

Issue TAC Vista stopped trending or cannot read trend value. SQL reaches 4GB or 10GB limitation (depending on version, Vista 5.0.1 - Vista 5.1.6 supports up to 4 GB and Vista 5.1.7 and newer support up to 10 GB) $queues folder keep growing Product Line TAC Vista Environment TAC Vista 5 Logging errors SQL data Log full, shrink 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. Cause The SQL 2005 Express version that come with Vista 5.0.1-5.1.6 has a 4GB limitation and the SQL 2008 Express version that comes with Vista 5.1.7 and newer has a 10GB limit. Once the SQL database reaches this limitation, Vista will not be able to read/write data from/into the SQL database. To fix this issue, the SQL database needs to be purged and a new SQL database needs to be created, or the SQL server needs to be upgraded. Once the SQL database is full, log data will be stored in the $queues folder wanting to be written into the SQL database. If the $queues folder gets too big that even creating a new SQL database with the same size limitations will not allow the Vista Server to run then data in the $queues folder will need to be removed or an upgrade to a version of SQL with larger size limits will need to be performed. Resolution Note: In deciding which resolution below will be most appropriate, consideration should be given to how quickly the SQL database is growing and how long it took to fill up initially. When the SQL database fills up it is a perfect time to carefully look at the various trends and alarms that consume space in the database and consider what if anything might reasonably be removed. Also, note Vista 5.1.7 and newer include SQL Express 2008 which has a 10 GB storage limit. This is 2.5 times greater than the SQL Express 2005 version that was included with earlier versions of Vista 5 and is a free upgrade from any Vista 5.1.X versions.   Please find the scenario that matches your issue and read the resolution section accordingly.   Scenario A Scenario B Scenario C Scenario D Data in "$queues" folder Not needed Needed Not needed Needed Data in SQL Db Not needed Not needed Needed Needed NOTE:  Administrator rights on the computer and to the SQL database is required in all scenarios in order to resolve this issue. In order to prevent the same issue occurring again, a log backup should be performed regularly.  Refer to Performing database maintenance with Vista 4.5.0 for additional information. Additionally, consideration should be given to whether an upgrade to full version of SQL should be installed to best suit the needs of the system.   Scenario A: Data in the $queues folder and SQL database are not needed. In this scenario, empty the $queues folder and create a new SQL database is the resolution. Please follow the steps below: Empty $queues folder Go to database folder. Its path can also be found in TAC Vista Server Setup (start->all programs/Schneider Electric/TAC Vista Server5.X.X. For TAC Vista 5.1.3 and prior, go to start->all programs/TAC/TAC Vista Server5.X.X instead).  Under “Vista Database” tab, the path is listed in the “Database folder path” textbox.   Delete everything in the $queues/insertevents folder (NOTE: don’t delete the folder). Delete everything in the $queues/insertlogvalues folder (NOTE: don’t delete the folder).   Delete taclogdata. Go to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data (default path). Delete “taclogdata.mdf” (default name, or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name). Delete “taclogdata_log.LDF “ (default name,  or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name).   Open “Server Setup” (start->all programs/Schneider Electric/TAC Vista Server5.1.X. For TAC Vista 5.1.3 and prior, go to start->all programs/TAC/TAC Vista Server5.X.X instead) and select “SQL Server” tab. Under “SQL configuration”, choose “Custom”.   Under “Custom connect using”, make a new name to “Log database name” (example:  change “taclogdata” to “taclogdata2”). NOTE: DO NOT change the user name and password.   Click Apply Click “OK” for “TAC Vista integrated SQL backup/restore function will not be available in custom configuration”.   Click yes at the prompt that says “No log database was found on SQL Server. Create and configure a log database?"   Click OK. Issue should be resolved at this point.   Scenario B: Data in the $queues folder is needed, but SQL database is not needed. If $queues folder is too big, need to upgrade to a full version of SQL database in this scenario.  $queues folder can be found inside the Vista database folder (refer to Scenario A step 1 for how to find the $queue folder). If $queues folder’s size is not too big do the following: Leave everything in the $queues folder. Data will be written into SQL database automatically after a new SQL database is established. NOTE: depends on the size of the $queues folder, it may take hours to transfer all data from the $queues folder into the SQL database.   Follow Scenario A steps 2-3 to purge the SQL database and create a new one. Issue should be resolved at this point.   Scenario C: Data in the $queues folder is not needed, but SQL database is needed. If the SQL database is needed, it can be removed from the Microsoft SQL Express folder and stored somewhere else. However, an upgraded version of SQL server is needed in order to view the old SQL database.  If the Vista version is <5.1.7Please follow the steps below: Follow Scenario A step 1 to empty the $queues folder.   Move taclogdata Go to C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data (default path). Move “taclogdata.mdf” out of the folder to somewhere else (for example: Desktop). NOTE: taclogdata is the default name, or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name. Move “taclogdata_log.LDF “out of the folder to somewhere else (for example: Desktop). NOTE: taclogdata is the default name, or go to Vista Server Setup and find the SQL name under SQL Server tab, Log database name.   Follow Scenario A step 3 to create a new SQL database. Issue should be solved at this point.   Scenario 😧 Data in the $queues folder and SQL database are both needed. If the SQL database is needed, it can be removed from the Microsoft SQL Express folder and stored somewhere else. However, an upgraded version of SQL server is needed in order to view the old SQL database. Versions of Vista between 5.0.1 and 5.1.6 (which include SQL Express 2005) can be upgraded to Vista 5.1.7 or newer (which use SQL Express 2008).  This will upgrade from a 4 GB database size limit to a 10 GB limit and is a free upgrade for and version of Vista 5.1. (Note that it is a paid upgrade from Vista 5.0.X.) In scenarios where SQL Express 2008 is already being used and is full or where 10 GB will not be an adequate upgrade for SQL Express 2005 then a full version of SQL Server will need to be purchased and installed. If $queues folder is too large, it will be necessary to upgrade to a full version of SQL server in this scenario.  $queues folder can be found inside the Vista database folder (refer to Scenario A step 1 for how to find the $queue folder). If $queues folder’s size is not too big do the following: Leave everything in the $queues folder. Data will be written into SQL database automatically after a new SQL database is established. NOTE: Depending on the size of the $queues folder, it may take hours to transfer all data from the $queues folder into the SQL database.   Follow Scenario A steps 2-3 to purge the SQL database and create a new one. Issue should be resolved at this point.

Issue How to uninstall and completely remove TAC Vista 4.3 to TAC Vista 4.5 Product Line TAC Vista Environment Microsoft Windows OS Vista 4.3 to Vista 4.5 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. Cause Occasionally it is beneficial to be able to remove a TAC Vista installation completely, removing any indication it was ever installed. Resolution When using SQL 2000 or enterprise version not administered by TAC Vista: Backup SQL database named "taclogdata." Use the backup function in SQL Server manager. Save the database outside of the Microsoft SQL Server and TAC root directory (usually C:\Program Files\TAC and> C:\Program Files\Microsoft SQL Server). When using SQL MSDE administered by TAC Vista: Backup TAC Vista log and event database using backup function in TAC Vista. Backup TAC Vista database using backup function in TAC Vista. Stop SQL manager, Task manager/processes – stop sqlserv.exe and sqlagent.exe if running. Remove TAC Vista Config1.x using the uninstall program in Control panel Add/Remove programs. Remove all TAC Vista hotfixes. Remove TAC Vista Server 4.x.x using the uninstall program in Control panel Add/Remove programs. If additional TAC programs like TAC ToolPack, TAC XBuilder etc. are installed remove them as mentioned before. Remove SQL (Microsoft SQL server desktop engine) using the uninstall program in Control panel Add/Remove programs. Save off a customer's license (.lic) file to another location.  Delete remaining uninstalled TAC folders (usually C:\Program Files\TAC). Delete remaining files in C:\Program Files\Common Files\TAC Shared. Delete remaining uninstalled SQL (Microsoft SQL server) folders (usually C:\Program Files\Microsoft SQL Server) Check to see if TAC needs to be removed from the registry – Start, Run, REGEDIT. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\SharedDlls Remove all keys containing "TAC Shared," e.g. C:\Program Files\Common Files\TAC Shared\TACADDON01_ENG.dll. If applicable - Remove SQL from registry under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL server Go to user profiles delete the profile Computername\TACA_Computername (Versions of Vista <5.0) Go to My computer, right click manage, local users and groups, users, and delete user account TACA_Computername and TACM_Computername. Reboot. Reinstall desired version. See How to uninstall and completely remove TAC Vista 5 for steps on removing TAC Vista 5.

Issue Not possible to see live values in a Xenta 700 Menta program from web interface or TAC Vista Can't see Menta online values in Xenta Server Control Applications graphical view The Menta application displays fine, but it's not possible to see the live values (true/false et c) Product Line TAC Vista Environment Xenta 731 Xenta 711 Xenta 721 Xenta 701 Xbuilder Menta 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. Cause This is an uncommon error and the cause is not known, however it may occur when copying a HFB block within or between X700 Menta applications. Resolution In the Xbuilder projects folder, find the file [project name]\TargetImage\configdb\menta\mentablocks.xml and open it in Internet Explorer. Search for Menta blocks that have CodIndex='0' and note (copy) the GUID of those (for example 3C02F735-E375-45d0-99A8-6CFC402DE5D0). Now open the file [project name].xbp518 (in the project's root folder) with notepad or similar and search for these GUID(s). Note the Menta block(s) name (before the GUID) and the menta block type (just after the GUID), for example HFDI. Close all previously opened files (no save). Open the Xbuilder project normally, and open/edit the troublesome MTA. Search for the menta block(s) name and check that it also is the same block type (most likely a HFB block), then delete it. Create the block again with the same name (no copying from similar blocks!). Save and download the project to the X700. Now it should work fine viewing the live values in Control Applications. If still same issue, redo step 1-7, there may be other blocks with CodIndex='0'.   Note: If you can't see the Menta application at all it's likely a different error, see Can't see the Xenta Server Menta program online in the browser.

Issue Software installation problems with Windows 7 OS and above Configuration problems also known as UAC / User Account Control These problems occur when you receive an error message stating that you do not have the correct administrative rights to continue. Product Line Andover Continuum, EcoStruxure Building Expert, EcoStruxure Building Operation, Satchwell MicroNet, Satchwell Sigma, TAC INET, TAC Vista Environment Windows 7 Windows 8 8.1 Windows 10 Server 2012 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. Cause Windows 7 and above user administrator privilege settings (UAC) Resolution The solution to this issue is to turn off the user admin settings before the software is installed by following these instructions: Go to Start > Control Panel. Set the view to "small icons" to show all Control Panel icons Click on "User Accounts." Make sure that the account used for installing the software is a full admin user. On this page, click on "Change User Account Control settings", a slider bar that starts with "Never notify" up to "Always notify" by default will be set to "Notify me only when programs try to make changes to my computer" Set it to "Never notify." This will disable all the admin blocks that pop up in installing and configuring software Once set, restart the PC and then continue with your software installation and configuration Once all is installed and working, the feature may be turned back on if required. Additional requirements for Windows server 2012 and Windows 10. Please note: this process may open the "Windows 10 Firewall up" For Windows Server 2012 and Windows 10, additional steps are required to disable User Account Control. Although the slider bar can be set to “Never Notify”, the User Account Control does not disable completely. The User Account Control can be disabled for any user by setting the system registry value “EnableLUA” to zero in the system registry under the registry key “HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\policies\system”. A Windows registration file has been included in the Continuum 2.01 release in order to expedite these additional steps. Or the attached file EnableLUA.zip can be used, unzip and execute.  Supplement: Using the right click "run as administrator" instead of this is not the same. The right click will only run that .exe as an administrator and not the whole install/configuration package, i.e. SQL2005 manager will fail to run if you do not do as instructed above. You will always get an error stating that you do not have permission to run this program.  Alternate Windows 10 Admin. to User privilege for I/Net Seven:   Go to this path: C:\Program Files (x86)\ Inet Seven 1) Rename and move to a new folder these files.       A) INetIoSrv.exe.manifest       B) INetW.exe.manifest       C) If there is a file equalization client, then there is INetEqzMerge.exe.manifest to do this change on as well.  2) Change the DbCreate by doing this:       Another problem for non-admin users will be logging into and using DbCreate. A work-around for that would be to create a new login into the SQL database that could be shared among all DbCreate users and would provide the necessary rights.       Alternate Windows 7 Admin to User privilege for I/Net Seven:  See the attached Document and Manifest Files  

Issue Some objects are protected by default in Vista requiring that changes be made to the authorities of the object in order for it to be deleted. Protected database objects will be in gray text whereas unprotected objects are in black. Additionally, the Delete option when right-clicking a protected database object will be grayed out. Text on protected database objects is gray   Text on objects that are not protected are black Environment Vista Workstation 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. Cause Even though administrators have full control to read or write any database objects, some objects are protected so that they are not accidentally deleted. An administrator must remove the protection before deleting the object. Resolution Ensure that you are logged into Vista as an administrator then perform the following steps to delete a protected database object: Right click the protected database object and select Authority. In the Authority dialog box check Change access level on subunits and Change access level on existing objects. The two check boxes for Require signature on database object change and Protected database object at the top of the dialog box will likely change from check marks to dark boxes. Click on these boxes until they are empty.   Click OK.   Refresh the window by pressing F5 or clicking the refresh button. The database object should now have black instead of gray text and can now be deleted.