Building Automation Knowledge Base

Issue Equalization not working on a File Master and Client Are you having an issue where you have a File Master and several Clients but cannot get Equalization to work? It looks like the snapshot gets delivered but the File Master’s Icon stays red and the client never gets the database.  Environment I/NET Cause SQL services may not be running properly. Resolution There are a few possibilities that could be the cause of this not working. Verify that MSSQLSERVER and SQLSERVERAGENT are set for Automatic and Local Machine in Services. Verify that the file C:\Program Files\Microsoft SQL Server\MSSQL\Data\InetDbSnapshot.mdf already exists but is not a registered database on the file master. See note below. Go to the FM; delete C:\Program Files\Microsoft SQL Server\MSSQL\Data\InetDbSnapshot.mdf and InetDbSnapshot_Log.ldf. Set all PCs to Stand Alone; re-promote the File Master and then the clients again. Note: This is an existing file that SQL uses, if you can rename it, it means that the existing one is not being used and therefore cannot be created by SQL again. If you cannot rename this file then this is not your issue.

Issue Running reports on a PC that is using Datacard ID Works and the report is not showing up on the PC screen as expected. Only half of the report is visible while the other half is scrambled and unreadable. Environment Datacard ID Works Cause The Datacard ID Works Printer can only print that format and not text which was why the display was wrong in the Reports. Resolution Select Printers from, Start or Control Panel. Uncheck the ID Works printer if it is your default. If you have a secondary or Network printer, just add it to your system and make it the default. Run the Reports again and it will come out the way it should.

Issue When running Seven (Crystal) Reports on the same PC as ID Works Environment I/NET Site Cause Having issue when running Seven (Crystal) Reports on the same PC as ID Works Resolution Using "Smart Printer Driver" set as the windows DEFAULT printer Seven Reports fails while attempting to display the query. You may first see a small window with '1/4o and a square". Before opening Seven Reports change your windows DEFAULT printer to another printer. Restart Seven Reports and run a query. The problem is due to the default paper size ID Works uses versus what windows uses.

Issue When upgrading I/NET 2000 to I/NET Seven, if during the install process you answered Yes and specified the I/NET 2000 root directory, I/NET Seven defaults all of its default directories to I/NET 2000. Environment I/NET Site Cause Issue when upgrading I/NET 2000 to I/NET Seven, if during the install process you answered Yes and specified the I/NET 2000 root directory, I/NET Seven will make all the default directories to I/NET 2000 Resolution Either copy the new BIN files into the old I/NET 2000 data directory, or change the I/NET configuration after the upgrade to point to the I/NET Seven data directory. By leaving everything the way it is, it will result in problems with I/NET Seven security, and transactions not showing up correctly.

Issue Can not Add, Delete or copy Individuals. Environment I/NET Seven Cause When the display order is based on the hexadecimal card number, the Add, Delete, and Copy functions become disabled in the Individuals Summary. This is not an issue with the database or password rights   Resolution Choose some other display order to re-enable the Add, Delete and Copy functions. Go to Access > Individuals. If you have multiple Tenants SELECT the respective Tenant From the Individual Summary display select OPTIONS Change the Display order to Individual, Last Name, First Name or Group Name. Do not put it on Card Number (Hexadecimal). This is option disables the Add, Delete and Copy buttons. OK out of the Options editor The Add, Delete and Copy buttons should now be available.

Issue Deleting Last Tenant from a given door in the System Environment I/NET site with Access Control Cause After deleting last tenant from a given door in the System, issue with cause individuals to not gain access Resolution Are you having an issue with individuals not gaining Access to a given door after the last Tenant is deleted from a Mipped 7920 and the SCU? This may have come about after a door was modified and the last Tenant may have been mistakenly deleted by the user. To correct this, a DPU Restore needs to be done to get the Tables realigned again. Once this is done, then access will be granted to the individuals. This will only take place if you are using I/Net Seven rev 2.11 and below. It was addressed in I/Net Seven rev 2.12, so all you have to do is upgrade your system.

Issue Configure a Xenta 5/7/9xx for no timeout log out. Environment Xenta Servers Xenta 511, 527, 555, 701, 711, 721, 731, 913 Cause A Xenta 5/7/9xx controller is set up with certain predefined time out durations for logging out inactive users.  While you cannot disable this feature, you can set the duration sufficiently long to effectively eliminate the log out if desired. Resolution Generate a certificate.  To avoid the certificate error every time you connect to the Xenta 5/7/9xx, go to XBuilder, and generate a certificate that has the same name as the IP address of the Xenta. Edit the file viewuser.html.  Connect to the Xenta using FTP.  For example Internet Explorer ftp://:@ viewuser.html is located in the folder www/config.  Save the file on your hard drive.  Edit the file with Notepad, and add the following correction to viewuser.html Line 159:  Add another Option tag with a value of "259200000" and description of 3000 days following the form of the previous entries. Carry out the changes.  Connect to the Xenta using FTP.  Change the name of the file in the Xenta (Backup) Copy the file the you have on your hard drive to the Xenta. Activate "no logout."  Go to the configuration page in the Xenta.  Select "3000 days" for log out

Issue Can connect to a Xenta 527 through the web, and can ping it, but when trying to connect to it with I/NET, it shows that it is offline. Environment Xenta 527 I/NET Seven Cause If you start I/NET and go to Edit/Host Computer/Network Configuration, you can see the Xenta 527 but there is a – sign in the Cnf column. If you right click on your I/O Server/Configure and select NPR Routers, the unit will not be Online and if you uncheck the box then you might see it in the Offline entries. Resolution Check the following settings: Verify that port 50069 is opened on the commercial routers in that network. Using a PC that has ftp access, browse to the Xenta 527, ftp:// 0.0.0.0/configdb/inet/filter.xml Delete this file and then try connecting to it again through I/NET. This file gets recreated with the default settings whenever another NPR or PC tries to talk to it. If this fails, then format the unit and download the bin files back to the unit again.  

Issue Configure the 527-NPR to use custom port assignments Environment I/NET site Cause How to configure the 527-NPR to use custom port assignments Resolution The Xenta 527/511/913 line of controllers are configurable to use custom port numbers for the http, https, ftp, snmp, and other ethernet related protocols. This is configured in the web interface on these controllers. The 527-NPR however has a limited web interface that only allows you to modify the I/NET communication port (default 50069). To use custom port assignments you will need to follow these steps: Connect to the 527-NPR with a ftp client. Browse to the /sys/system directory. Copy the configuration file of the protocol you want to set a custom port on. (http.cfg for HTTP or HTTPS protocols) Modify the port number with notepad. Copy the file back into the /sys/system directory. Restart the 527-NPR. You will now be able to access the 527-NPR with the new port assignments.

Issue Global Points not working after an Upgrade. Environment I/NET site with Global points Cause Issue with Global Points not working after an Upgrade Resolution Are you having an issue with global points not working after you have upgraded from I/Net 2000 to I/Net Seven? There are 2 ways that you can resolve this, first: On your PC, do you have a reference host IP in your active profile in I/O Server? Change the setting back to 0, shut down I/Net and I/O Server and then restart it again. Modify the profile and place the IP address of the NPR in the reference hosts IP. If you are using an NPR, change the settings back to 0, restart the unit and then put the addresses back again into the reference host IP. Check your global points and they should be updating now. Secondly, follow this example: Point address Example High 1 (Calculation taking the high value from 15 zones) Point address Example High 2 (Calculation taking the high value from 12 zones) Point address Example Avg. (Average of High 1 and High 2) Create a new point and create a calculation that looks at the point that was not updating. After: Point address Example High 1 (Calculation taking the high value from 15 zones) ***Existing points that did not change*** Point address Example High 2 (Calculation taking the high value from 12 zones) ***Existing points that did not change*** Point address Example Avg. (Average of High 1 and High 2) ***Existing points that did not change*** Create a new point called: Point address Example Avg. A (Calculation pointed to Example Avg.) Made the Example Avg. point internal and not Global LAN. Made the newly created point the Global LAN point.

Issue Launching I/NET automatically on startup of the PC. Environment Microsoft Windows I/NET Cause There is a feature where the user can automatically launch I/NET when they start their PC. This keeps operators from having to remember to start I/NET after a reboot or power loss. Resolution Go to Windows Explorer > C:/Documents and Settings/Users/[select the user]/Start Menu/Programs/Startup Create a shortcut for I/NET Select I/NET, right click and select properties, at the end of "C:\Program Files\INET Seven\INetW.exe" place a /winuser. Now it should look like this "C:\Program Files\INET Seven\INetW.exe" /winuser. Log off or shut down the PC Restart it again and I/NET should automatically be started.

Issue Vista receives an I/NET transaction from a Xenta 527 as an alarm but not as a transaction Environment TAC Vista Workstation Alarm Queue Event Log I/NET Transactions Xenta 527 Cause If your time stamp is in the future, the events window (transactions window is really a filtered events window) will not display them but for some reason alarms come through. Resolution Open the Xenta 527 from Internet Explorer. Open the Events folder under I/NET. Look for the transactions. Note the date and time. Make sure the date and time in your 527 are set correctly and that the time zone is right in regional settings. Even though the SCU time stamps the transaction, the 527 shifts the stamp according to it's own settings.

Issue Time stamps of I/NET transactions are off in the Vista event and transaction windows. Environment Xenta 527 I/NET Events TAC Vista Workstation Cause Even though the SCU time stamps the transaction, the 527 will shift it according to it's time zone and date settings. Resolution Make sure the time is set correctly in the Xenta 527. 

Issue Integrated NPR Dial on a Xenta 527 Environment I/NET site with Integrated NPR Dial Cause Explanation of Integrated NPR Dial on a Xenta 527 Resolution Are you having an issue where you are setting up NPR Dial on a Xenta 527? Only the US Robotics V92 56K Faxmodem is supported. Do realize that this device cannot perform Auto Dial Auto Answer (AD/AA) functionality. To configure NPR Dial you will need to get the Xenta Modem Kit, part # 0-073-0916. These steps should point you in the right direction: -   Verify that you have the right strings for the modem. Create an I/NET Configuration profile for Integrated NPR Dial and make it active. Restart I/NET. Add site phone numbers (Edit > Host Computers > Phone Numbers.) Connect the necessary cables to the Xenta 527 unit and modem. You can get a full description from part number OFL-3972-001 with all the cables etc. Connect the adapter to the modem then the L1 cable from the modem to port A on the Xenta 527 unit. Query your modem, check the settings and baud rate then dial the site.

Issue I have a Window XP PC and cannot get the MSDE to load Environment Windows XP MSDE I/NET Seven Cause According to the Microsoft web site, the file and printer sharing has to be turned off to load Microsoft SQL. Resolution Turn off file and printer sharing. Once The I/NET software is loaded, re-activate the Shared objects.

Issue Dell PC will not allow the MSDE to load from I/NET Seven Environment There are (3) different computers from Dell: L100 Latitude D505 Latitude GX OptiPlex series desktop All were running Windows XP Pro and all had an installation of MSSQL installed already. Cause When I/NET is installed for the first time and MSDE begins to install it fails on the "renaming of the SQL folder" partly due to "Read Only" right to the folder SQL is installed in. The error message is has this reference in it about SQL: MSSQL$MICROSOFTBCM cannot be renamed. The install of I/NET stops at this point. You do not have the option to use "Add Remove Programs" to uninstall this previous install of SQL. Resolution Go to "Manage\Services and Applications\Services... to Stop and or Disable (3) current instances of SQL running. Right click on "MSSQLSERVER" and click on Properties, then click on the Startup type, then select "Disabled", click Apply and then repeat for MSSQLserverADHelper and SQLSERVERAGENT. Now close the Manage window and then begin the I/NET Seven install again. MSDE will install correctly as well as the rest of the I/NET Seven install.

Issue How does the "Door Closed Timer" work in the I/NET Seven Door editor? Environment I/NET site with Access Control Cause Explaining the Door Closed Timer in the I/NET Seven Door editor Resolution Set the duration of the Door closed timer to a value from 0 to 25.5 seconds (0.1-second increments). This timer determines how long the door must remain closed (as sensed by the door sense switch) before an unauthorized door open condition will trigger a "forced door" message. Use this feature to help prevent false "forced door" messages that can sometimes occur when a door closes, but then bounces enough distance to trigger a temporary open condition at the door sense switch.

Issue "Door open too long" and "Forced door" alarm masking Environment I/NET Resident I/O Cause All of the masking, priorities, and message types may be set in the door editor. DOTL and forced door may even be configured as an alarm or message, but if the Resident I/O point is not masked for the door (08DO or 09DO), you won't receive any DOTL or forced door alarms. Resolution You can also use this arrangement to your benefit. Maybe you want all transactions to one host but you want the DOTL or forced door to go to another one in a guard station. Maybe you want only those to dial out a pager.

Issue Host Trend Log reporting "?" for some values Environment I/NET Seven Host Trend Log Cause The reason for the "?" is because a rule was not complied with. The Print interval/Sample Interval did not result in an even number. Resolution The Basic rule for the "Host Trend Log" is the Print Interval (divided by) Sample Interval – must equal an even number. For example the default setting in this editor is as follows: Print Interval – 1440 Sample Interval – 30 So 1440/30 = 48

Issue There are some rules using the I/NET Seven "Working Offline" options. Environment I/NET site Cause  I/NET Seven "Working Offline" options Resolution If you take a DCUxxxx.sav file from an older version of I/NET Seven and open it up thru the "Work Offline" in a newer version of I/NET Seven (Rev 2.xx) and modify that save file. You will have issues with this DCUxxx.sav file, for instance if you return this modified DCUxxxx.sav file back in the older version of I/NET Seven you will see changes in the Time Schedules and "Door ATS" time schedules in a Mipped 7920 board. It adds two new lines in Time Schedules and the "Door ATS". Here is what you will see in the "Door ATS" APB (Anti Passback) settings for that door. APB Reset for that door. This is the Original ATS Schedule. So the Rule to follow is this: If you are working with DCUxxxx.sav from I/NET Seven rev 1.xx, then you must use the same version of :Work Offline. If you are working with DCUxxxx.sav from an I/NET Seven rev 2.xx, you must the 2.xx version of "Work Offline"