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

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

Issue Lost the password to login to the different media I/NET, SQL, SAV Environment I/NET site Cause Lost Password Resolution I/NET login: Please send the database with version number and SQL version used to ProductSupport.BMS@schneider-electric.com. SQL login: Please see Loading I/NET on a PC that has full SQL and the Password is not known and Changing the MSDE SQL Server Sys Admin account password is not supported by the I/NET Seven DbCreate Utility. DCU login: Please see Recover an I/NET Controller's DCU Password.

Issue Using I/NET trends in StruxureWare Building Operation Product Line EcoStruxure Building Operation, TAC INET Environment I/NET StruxureWare Building Operation 1.3 Cause Ideally trends should reside in the controller rather than at the sever level as this prevents sample data loss due to communication errors. Resolution Before you begin, ensure that all I/NET trends are set up correctly and trend data is visible. For assistance with this see Setting Up I/NET Seven Trends. Ensure that messaging is working so that SmartStruxure receives I/NET messages, and ensure that all controls have points to be trended, are already added to the I/NET Interface. NOTE: For the Enterprise Server level integration, the I/NET Trend Object must be configured as a Seven Trend. For the Automation Server level integration, this is not required, therefore skip to step 3. In I/NET, Select Trends>Data Inquiry/Edit View the trend you wish to see in SmartStruxure and verify that it has data. Open StruxureWare Workstation Refresh the system tree and upload any I/NET controllers that do not show a green dot. Right click on the I/NET Interface and select New>Value When the "Create Object" Window appears, name the value and click "Create" The Value will appear in the I/NET Interface Right Click on the newly created Value and select "Properties" Locate the "Point to Trend" Field Click on the "..." and select the point object you wish to trend Click the select button Verify that the Point to Trend field is correct and Click OK Wait enough time for several samples to populate. Right click on the Value object in the I/NET interface and select View>Trend log lists>New Trend log list The New Trend log List should open and values should visible. The Trend Value object under the I/NET interface will now function the same as a trend object in StruxureWare. If you wish for the I/NET trend to show up as part of an Energy Report, you will need to Ensure that the Extended Trend Log is referenced in a Meter's "Meter Trend Log" property NOTE: For the Enterprise Server Level Integration, In order for the initial connection between the StruxureWare Value Object and the I/NET Seven Trend to be enabled, the following conditions need to be true: The Controller with the I/NET point being trended must not require an upload The Controller with the I/NET point being trended must have a current save file The Controller with the I/NET point being trended must be online The I/NET workstation located on the Enterprise Server must be masked to receive data from the trend log on the controller to the Seven Trends Definition For the Automation Server Level Integration, In order for the initial connection between the StruxureWare Value Object and the I/NET Seven trend extension to be enabled, the following conditions need to be true: The Controller with the I/NET point being trended must not require an upload The Controller with the I/NET point being trended must be online The I/NET trend object and point object must have some level of masking so that the data will leave the controller.

Issue IDWorks 6.x (on a Remote Client) does not connect to the SQL with Windows 7 64 Bit. Product Line TAC INET Environment Datacard IDWorks 6.x Windows 7 64-bit I/NET 2.43 and above Cause You have to manually install a 32 Bit ODBC connection for this to work correctly. Resolution To resolve this issue, start the EXE file located at: C:\Windows\SYSWOW64\odbcad32.Exe. NOTE: This is NOT the ODBC that is in the Control Panel on the PC. Once you start the EXE file, set this new ODBC Connection up by following the steps that are listed in Setting up ID Works on a Remote Client PC.

Issue There appears to be a low battery on the control board. How can the NiCAD Battery be tested on the controller to see if it needs to be changed? Product Line TAC INET Environment I/NET Seven Cause Possible low battery on control board. Resolution There are some checks you can make regarding the battery condition. The battery has a design life of 7 years and sometimes lasts much longer. With power applied to a controller for at least 72 hours, take a DMM and measure the DC voltage across the battery. It should be in the neighborhood of 4.2-4.3 vDC. Remove power from the controller board and take the same measurement again. The beginning voltage should still be between 4.1-4.3 vDC and should start slowly tapering off (a tenth of a volt over a period of minutes would be normal). When the battery voltage reaches 3.6 vDC this is the threshold at which the battery can sustain the RAM memory. Any voltage below this value will subject the RAM memory to loss of data (+ - a tenth or two). If the initial voltage with power applied to the controller is less than 4.0 vDC after 72 hours, the battery may need replacing. If the battery voltage drops rapidly after power is removed from the controller, the battery needs replacing. If the controller memory inexplicably gets lost (not counting power surges, brownouts, etc.) and a station restore is needed, the battery may need replacing. Normally the above-mentioned tests will show that the battery has lost its storage capacity. The TAC part number for the White NiCAD battery that is on most of the I/Net Controllers is 01-2100-545. These batteries can no longer be ordered through the Customer Care department. For further battery info please reference Replacement I/NET Controller NICAD Battery info.  

Issue After successfully logged into Xenta Server web pages, java loading icon will be displayed as shown below. However, after a while it will automatically log the user out as shown below. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers 5.1.6 (Xenta 511, Xenta 515, Xenta 527, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913) Java 1.6 update 29 Note: This behavior may happen on other Xenta Server versions with different Java versions. Please refer to the Cause section for the reason. Cause Vista may not support the newest Java versions. For Vista 5.1.6, the recommended Java version is Java 1.6 update 20. Please refer to Recommended Java version for TAC Vista 5 for recommended Java version details. Resolution Go to Start > Settings > Control Panel > Add or Remove Programs. Find Java application (in this example is Java(TM) 6 Update 29), and select “Remove”. Reload the Xenta Server webpage, will find the Java icon will not be displayed this time. Instead, “Download Java” request link will be displayed. Click on the link and download the supported version of Java. The issue should be solved after the recommended version of Java is installed.

Issue Verifying the Com Port on a PC is working properly by using "Loopback" test in Terminal Emulator. Product Line Andover Continuum, Field Devices, Other, Satchwell MicroNet, Satchwell Sigma, TAC IA Series, TAC INET, TAC Vista Environment Hyperterminal RS-232 serial port Cause The following test writes to the serial port and reads from the same port. This will verify the Full duplex operation of the RS-232 communication. Resolution Short the TX and RX pins of the cable (pins 2 and 3) following the pinouts below. Gender is determined by pin type.                Male DB9 (Left) and Female DB9 (right)   Launch Hyperterminal by selecting Start>>Programs>>Accessories>>Hyperterminal. If you do not have Hyperterminal, please read Hyperterminal on Microsoft Windows Operating Systems. If you are asked if you would like to install a modem, select No. Choose any icon and name the session, select "OK". In the next Pop-Up menu, choose direct to COMx (where x is the number of the COM Port you are testing.) Set the flow control setting to None. Leave the other settings to default settings, select "OK" Select File » Properties from the menu bar, select the Settings tab, and then push the ASCII Setup button. Check the option for Echo typed characters locally. Type something. If you see double characters the serial port is setup correctly and is functional. The display is showing characters that are sent out and what is read in. The Emulator will send and display the TX and immediately read and display  RX. If you see exactly what you are typing, you have a communication issue. which could be: Bad Com Port Bad cables Pins not shorted correctly If you are out of physical ports to try, use a USB Serial Port converter. If you are using a USB, use Reassigning a USB Serial Adaptor to a desired COM port for instructions of assigning Com to another port.

Issue When upgrading to a different revision of software in I/NET Seven, there are a few steps that are highly recommended to ensure that the database doesn't get corrupted during the upgrade. Product Line TAC INET Environment I/NET Seven Cause Performing an upgrade of I/NET Seven software. Resolution Close I/NET Start DB Create and select the Verify Database option. Verify that the database has 0 differences. Select Upgrade Database to force an upgrade Select the Verify Database option again. Now back up the database to the local drive or media and proceed with the upgrade. Once completed, Select Restore database and proceed to where the back up is and restore the database to the system.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue Links not working after TGML conversion Converting I/NET graphics to TGML using the "Create Source Tree" option Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Seven 2.44 Cause I/NET stored graphics on the hard disk and allowed for complex folder structures to be used in organizing those graphics. When these graphics are converted to TGML, this structure may need to be preserved in order to prevent duplicate graphic names. Resolution For this example I have created a site with 3 buildings containing Identical I/NET graphics. Each Building has a summary page and a VAV page. All pages link back to a home page. In I/NET select System>Export Graphics to TGML(you can also right click on the I/NET interface in StruxureWare Workstation) Set your Source and Destination Path and click All Yes.  When you set your destination path, it must point to a folder that already exists in Windows.  The Export INET Graphics to TGML tool does not create this directory Notice that the default setting is to "Use destination path" If we click convert with that option, we will get only 3 graphics.  The graphics from other folders with the same name are over-written. Select the "Create Source Tree" option, ensure the correct graphics are scheduled to convert and click convert. Notice that In Windows Explorer a new folder structure is created that is identical to the original folder structure. Open StruxureWare Workstation. Create a folder system that matches what is on the Hard disk. Drag and drop the TGML files from Windows explorer to the corresponding folders in StruxureWare Workstation. Test you graphic links to ensure everything is functional. Note: Once the graphics are imported, StruxureWare will allow you to move them freely without breaking the binding between pages. There is another way to import all the I/NET graphic folders in one time. Refer to Import all converted I/NET graphic folders into EcoStruxure at one time.

Issue When trying to download a 5/7/9xx in XBuilder you get "Error code 401 - Unauthorized". Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Server Xenta 511, 527, 555, 701, 711, 721, 731, 913 XBuilder Cause Password in XBuilder project does not match the password in the Xenta device. Resolution Select the 5/7/9xx in the Network panel The password is in the right hand panel of XBuilder under the TCP/IP Settings section. Change this to match the password in the 5/7/9xx. If the password is not known then refer to Receive a temporary session password for a Xenta 5/7/9xx if the password has been lost.

Issue Original company sold to new company Site License needs to be updated for install/upgrade.  Computer failure and no software/license information is available. Downloaded software and during install it requests a CD Key Product Line Andover Continuum, TAC INET Environment Site Licensing for install/upgrade Cause Changes in company or computer replacement/upgrade or downloaded software and it is requesting a CD Key Resolution I/NET: 1. Original company sold to new company and Site License needs to be updated for install/upgrade: for company naming changes, contact your sales representative who in turn will contact Product Support and request a transfer of information or upgrade/purchase. Once the information has been cross referenced for validity, either a new or replacement CD Key can be generated. Please include the following when requesting transfer: User Name Site Name Site Address Serial Number Version number Build number CD Key 2. Computer failure and no software/license information is available: Send email to Product Support with the following information: User Name Site Name Site Address Serial Number version number Build number CD Key 3. CD Key for licenses on purchase of software can be ordered by contacting Contact Customer Care. Link is available on the Contact tab of this web page. Customer Care offers pricing, order placement, changes, expedites, and order status. Check Licensing of I/NET with SITE and SEAT License with License Key for issues with CD Key and Licensing information. Continuum: since Continuum only has physical security key licensing, the license is owned by the holder of the key. If you hold the key, you own the license. There is no need to contact PSS for moves, changes, restructuring. If the security key's are lost or stolen, you will need to purchase new keys to replace them. Continuum Software Licensing is available with Release 2.0. 

Issue When restoring database, an error will show up, saying that version is incompatible with this server. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause This is usually caused by restoring new SQL database to older version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Microsoft doesn't like to do this. Resolution There is build number matrix for each SQL server version:     RTM (Gold, no SP) SP1 SP2 SP3 SP4 SQL Server 2012 11.00.2100.60 11.00.3000       SQL Server 2008 R2 10.50.1600.1 10.50.2500 10.50.4000     SQL Server 2008 10.00.1600.22 10.00.2531 10.00.4000 10.00.5500   SQL Server 2005 9.00.1399.06 9.00.2047 9.00.3042 9.00.4035 9.00.5000 So check the build number in the error message and download the corresponding version of SQL to restore and be used for I/NET.  Refer to How to Troubleshoot on DBCreate for more issues about DBCreate.

Issue Error when installing SQL 2005 Express on a machine that had previously had MSDE installed Product Line TAC INET Environment SQL 2005 Express Cause  MSXML 6.0 SP2 is causing the installation to fail Resolution Download the program linked below Remove SQL 2005 from the system Run the application to remove MSXML 6.0 from the system Re-install SQL2005 Express MicrosoftFixit50568.msi.zip For alternative solutions see SQL Express install fails on MSXML 6 and Failed to create or configure database on SQL Server! ([17] SQL Server does not exist or access denied.).

Issue Where to begin troubleshooting Ethernet (TCP/IP) communication problems with a NPR Product Line TAC INET Environment I/NET NetPlus Router (NPR) Model Series 2000 Cause Possible Causes: Ethernet Communication is down Ethernet Port is closed Device is configured incorrectly Device failure Resolution Gather detailed information about exactly what is happening Ethernet Communication is down Using the command prompt ping the devices IP and trace its route. "ping xxx.xxx.xxx.xxx" and "tracert xxx.xxx.xxx.xxx" Watch to see if the Domain server prints out the correct Host name. If the device is shows as offline there may be an error with Firewall settings or Ethernet communication at the Host Workstation Disconnect the Ethernet cable from the Device and plug it into a laptop. See if you are on the network. Ethernet Port Is closed If the above process shows that Ethernet communication between the Workstation and Router is valid, you may have port closed. Use a crossover cable to connect a laptop to the device and see if you can connect to a controller ON THAT LINK in I/NET. Look for live values in Controller Summary. If you are able to do this, and you are able to show that Ethernet communication between the 2 devices is working then you most likely have a firewall that is block the UDP port 50069 Contact the building IT department to assist in rectifying this problem. Device is configured incorrectly If, in the above process, you were unable to connect to I/NET while direct connected to the Router via an Ethernet crossover cable, the device may be configured incorrectly Open the active I/NET configuration Profile Ensure that TCP/IP is enabled Add the Router’s IP address to the Reference Host Table Restart the I/O server Check communication Alternatively you can connect to the router via I/NET Direct Connect configuration profile. Refer to Troubleshoot an NPR problem with Windows Telnet utility on how to do this and check that the IP Address and details are set correctly. Communication should be restored. Device failure Try to reset the NPR: Remove the NPR cover. Depress the center tab of the I/DISC slot and hold it down. Next press the reset button on the front of the unit and hold for 10 seconds. Release the reset button and then release the center tab. Two LEDs should display steadily. Next depress the center tab and hold it down. Press the reset button on the front of the unit and hold for 10 seconds. Release the center tab and reset button simultaneously. The LEDs should display steadily. The NPR unit should now be ready for a software restore. Download and install the latest system file for the NPR. Configure the I/NET communication in your active Configuration Profile. If you not able to successfully update the firmware in the NPR then it is likely that the device is faulty and may require repair or replacement.  The current replacement for the Series 2000 NPR is the Xenta 527-NPR. Other Troubleshooting Steps See if the communication error shows up on multiple computers and if possible multiple locations. There may be an error with Firewall settings or Ethernet communication that only effects part of a large system Host Workstation Use a different Ethernet port to connect the NPR or workstation too. Direct connect to a controller on the controller LAN via TAP and see if any stations are offline. It is theoretically possible that some form of electrical failure on the controller LAN has caused the NPR to appear offline. If you are unable to see the entire controller LAN from anyone one device, you should troubleshoot Controller LAN communication. Contact Product Support with your findings.

Issue Managing communication between I/NET and StruxureWare Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Enterprise server level integration I/NET Automation server level integration StruxureWare Building Operation 1.6.1.5000 and above. Cause Users should manage data flow on the controller LAN in order to maintain efficient communication. Any binds to objects under the I/NET interface follow the settings for the INET Global device scan rate (min) and the INET Global point scan rate (s). By default, this is set to 60 minutes for device status and 5 seconds for point bindings. The INET Global device scan rate (min)  is used to monitor online devices. A device will show offline sooner than the configured setting as all points would show offline.  The  INET Global point scan rate (s) is applied to all binds between StruxureWare and I/NET.  Opening a graphic or watch window will ignore this rule and immediately request values. After that, the scan will update according to the configured setting. A controller can either follow the Global scan rates as by default or use its own setting.  When a controller has the property DCU scan rate or point scan rate set to 0, it will follow the scan rate configured for the I/NET interface. An I/NET 19200 speed Controller LAN will handle a maximum of 10 token cycles per second. Each cycle allows a single packet of information to be passed from a single controller to the server. 1 Packet can contain all data for up to 18 points on a single controller. This means binding to manual, value, and PvControl for 18 points on a single 7718 will take one packet. Binding only the value of 5 points on 5 different controllers will take 5 packets. Adding devices to the controller LAN and adding additional polling will slow down the number of cycles per second on the controller LAN. Resolution All active binds will poll every scan interval. Graphic binds are only active when the graphic is open. Trend Logs will poll every scan interval regardless of the log configuration options.  Whenever possible, use the I/Net Alarm and Trend objects rather than creating separate StruxureWare alarm and trend objects. Trend Log Best Practices: Use the I/NET Trend Extension as outlined in Using I/NET trends in StruxureWare Building Operation please refer to the online help guide for complete information. Create Extended Trend Logs of this information for long term storage. I/Net Alarm Best Practices: Use the I/NET point extension to configure the alarm to be triggered by logic within the I/NET controller. I/NET Alarms have 3 priority options which are Routine, Priority, and Critical. This can be globally assigned to any priority using the I/NET interface messages tab. Other StruxureWare Alarm enhancements are available to I/NET objects as well. Scheduling and programming I/NET from StruxureWare Whenever possible, bind values to a single I/NET controller per controller LAN and then create I/NET Global/Indirect point relationships to distribute this value to other devices on the controller LAN. Using a single controller allows more information to be sent per packet. I/NET Global points will only broadcast on change. In this scenario, the server is polling a single controller ever scan interval and then on change all other controllers are updated. Increase the Point scan rate Using the information above you should be able to calculate how many packets are required for your system for each token pass. If this number increases to the point that more packets are required than are possible in the default 5 seconds, increase the scan rate. You can increase it on specific over loaded controllers or on all controllers together.

Issue If the Xenta Server IP address is unknown or lost, how can the user retrieve or reset the IP address? Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause Once the Xenta Server IP address is lost, the user has to use a serial connection cable to connect the Xenta Server to the HyperTerminal in order to retrieve the IP address. The serial cable is a RS-232 to RJ10 cable which can be purchase from Schneider Electric order entry (Part number: 00730920). For some reason, if the cable need to be home made, please follow the steps below to connect correct pins. Note: some third party IP search/scan software can be used to search all IP addresses in a range. User can also use this type of software to retrieve Xenta Server’s IP addresses. Resolution Xenta Server serial cable guide: Connect RJ10 pin 1 to RS232 pin 2. Connect RJ10 pin 2 to RS232 pin 3. Connect RJ10 pin 4 to RS232 pin 5. Connect RS232 pin 1, 6, 4 together. Refer to IP setup for a Xenta server (Xenta 5/7/9xx) through serial communication for how to set up HyperTerminal in order to retrieve/setup Xenta Server IP address.

Issue After installed I/NET, DBCreate will never pop up to create a new database, which will cause I/NET never launches. Backup and Restore button are greyed out when opening DBCreate, which also will cause I/NET fails to launch. When restoring database, an error will show up, saying that version is incompatible with this server. When restoring the database, an access deny error will show up. Unable to create a backup of an I/NET Seven Database using DBCreate, gets a backup failed error. When restoring I/NET database backup from another server in DBcreate, it shows an error: Error dropping PRIMARY KEY 'PK_DvrServers': Could not allocate space for object 'sys.sysserefs'.'clust' in database 'InetDb' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup. Product Line EcoStruxure Building Operation, TAC INET Environment I/NET Cause SQL default instance is not created correctly. SQL2005 BCM is not installed correctly if SQL2008 is used, or there is a database version mismatch for I/NET. This is usually caused by restoring new SQL database to old version or under different kind of Operation Systems (like restoring a 64 bit database to a 32bit SQL server). Windows permissions are not enough to do the restoring Functionality of the host pc and the database seems to be inconsistent. If the database size limit is reached, I/NET database will fail to update. The backup of the database will be fine, but when trying to restore onto another computer, it will also fail. Resolution If you are using I/NET 2.4x, and already have a named SQL instance on the computer (for example, TAC Vista 5.1.7 or higher has been installed, with a named instance installed called TACVista), I/NET may fail to recognize it, while also fail to create a default instance. Similar kind of warning will pop up during the I/NET installation: Under this condition, use your current SQL server installer or browse to /SQLExpress folder of I/NET installation CD, to manually create a new default instance. You can refer to the guide within the /SQLExpress folder about how to create it. As long as the default instance is created, DBCreate will pop up immediately and a new database can be created. If 64 bit Operation System is used, refer to Installing I/NET Seven on a 64-bit operating system for the detailed guide. Also refer to Installation guidelines for installing I/NET and Vista on the same PC for more details about installing I/NET and TAC Vista on one computer. If SQL 2008 or SQL 2008 R2 is used, be sure to follow the correct steps about how to install them: I/NET Seven with SQL 2008: I/NET Seven with SQL 2008 Installing I/NET Seven on a 64-bit operating system: Installing I/NET Seven 2.42 or higher on a 64-bit operating system If SQL 2008 is installed correctly, please refer to Data Base maintenance before performing an upgradeto perform a forced upgrade for the database. Refer to Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate: Incompatible SQL Server Version error when Restoring I/NET Database in DBCreate Refer to DBCreate backup access denied using Windows Server 2008 R2 Standard and Microsoft SQL 2008 R2: DBCreate backup access denied using Windows Server 2008 R2 Standard & Microsoft SQL 2008 R2. Refer to Unable to Create a backup in DBCreate: Unable to Create a backup in DBCreate. Refer to Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached: Fail to Restore the Backup from I/NET with SQL Database Size Limit is Reached.

Issue When logging into Xenta server using Internet Explorer 8 a certificate error is displayed as displayed below: When logging into the web server of a Xenta controller using Internet Explorer 8 an error message is shown stating that there is a problem with the website's security certificate. The error reads: There is a problem with this website's security certificate. The security certificate presented by this website was issued for a different website's address. Security certificate problems may indicate an attempt to fool you or intercept any data you send to the server. We recommend that you close this webpage and do not continue to this website. Click here to close this webpage. Continue to this website (not recommended). More information How to install a self signed certificate. Product Line Satchwell MicroNet, TAC INET, TAC Vista Environment Internet Explorer 8 Xenta 511, Xenta 527, Xenta 555, Xenta 701, Xenta 711, Xenta 721, Xenta 731, Xenta 913 SSL Cause The default certificate in the Xenta web server is a self-signed certificate. Since the certificate is not issued by a recognized Certificate Authority the web browser (in this case Internet Explorer 😎 cannot validate the authenticity of the certificate and suggests that the user not continue to the website each time the user tries to access it. Resolution Click "Continue to Website" to continue to the screen shown below. Click on "Certificate Error" which is found on the right side of the address bar at the top. A dialog similar to the one below will open. Click "View certificates". The certificate dialog will appear. Click "Install Certificate." The Certificate Import Wizard will open. Click Next. Allow Windows to automatically select where to store the certificate. Proceed to Finish the Certificate Import Wizard. A notification appears indicating that the certificate was imported successfully. Restart Internet Explorer for the change to take effect. Note: The certificate will need to be installed in each client computer that accesses the Xenta server but once this complete it does not need to be done again. The exception to this is if the web address of the Xenta server is changed or if Internet Explorer is uninstalled then reinstalled. The alternative is that a certificate issued by a Certificate Authority (CA) may be purchased. These certificates are pre-installed into the web browser and will automatically prevent certificate errors from occurring on all client computers that access the web server. Note that these can be quite expensive and unless the Xenta web server is being hosted on the internet they are not necessary. See "This Connection is Untrusted" certificate error when logging in to a Xenta Server using Firefox for information on installing certificates into Firefox. Update: Starting in September 2014, all major browsers will be disabling 1024-bit roots within their trusted roots stores. Any SSL certificates chained to a 1024-bit root will no longer work on any browsers that takes this action or one that relies on another's root store (the self-signed certificate is 1024-bit). This means that you will still get the security warning even if you have installed the self-signed certificate.

Issue Receive the following errors when trying to restore a SQL database: ERROR MESSAGE #1 Msg 3169, Level 16, State 1, Line 1 The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.1600. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. ERROR MESSAGE #2 Server: Msg 3241, Level 16, State 7, Line 1 The media family on device [path of backup] is incorrectly formed. SQL Server cannot process this media family. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. ERROR MESSAGE #3 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 661. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. ERROR MESSAGE #4 Server: Msg 3241, Level 16, State 7, Line 1 The media family on device [path of backup] is incorrectly formed. SQL Server cannot process this media family. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. ERROR MESSAGE #5 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 655. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. ERROR MESSAGE #6 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. Product Line Other, TAC INET, TAC Vista Environment SQL Server 2008, SQL Server 2005 and SQL Server 2000 Enterprise, Standard, Express, MSDE Cause You cannot restore a backup created with a newer version of SQL Server on an instance running an older version of SQL Server. Unfortunately, the error messages that are displayed may not always tell you that it is a versioning problem. Here are various combinations of SQL versions and there associated error messages: SQL Server 2008 R2 to SQL Server 2008 Msg 3169, Level 16, State 1, Line 1 The database was backed up on a server running version 10.50.1600. That version is incompatible with this server, which is running version 10.00.1600. Either restore the database on a server that supports the backup, or use a backup that is compatible with this server. Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 R2 to SQL Server 2005 Server: Msg 3241, Level 16, State 7, Line 1 The media family on device [path of backup] is incorrectly formed. SQL Server cannot process this media family. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 R2 to SQL Server 2000 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 661. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 to SQL Server 2005 Server: Msg 3241, Level 16, State 7, Line 1 The media family on device [path of backup] is incorrectly formed. SQL Server cannot process this media family. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2008 to SQL Server 2000 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 655. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. SQL Server 2005 to SQL Server 2000 Server: Msg 3169, Level 16, State 1, Line 1 The backed-up database has on-disk structure version 611. The server supports version 539 and cannot restore or upgrade this database. Server: Msg 3013, Level 16, State 1, Line 1 RESTORE DATABASE is terminating abnormally. Resolution Possibly the quickest and simplest solution may be to uninstall any software including SQL currently installed, then re-install any software along with the correct version of SQL. If this is not an option, then Microsoft does provide information on how to upgrade different versions of SQL. Links are provided below: How to: Upgrade to SQL Server 2005 (Setup) How to: Upgrade to SQL Server 2008 (Setup) Also check Software and Firmware compatibility matrix for older versions of the traditional product lines for supported Operating Systems and SQL versions.