| |
| DomainScan v1.0x issues | DomainScan v2.x issues
 |
|
|
|
DomainScan v1.1 -> v1.71 issues
| Legend |
Resolved bugs |
Normal |
Non-critical |
Critical |
BugID# 50
| Found: v1.70
Affected versions: v1.70 (Client)
Fixed: 1.71 | IP address fields will only accept 2 digits per octet
|
BugID# 49
| Found: v1.70
Affected versions: v1.70 (Client)
Fixed: 1.71 | The tab order in Preferences is confusing
|
BugID# 48
| Found: v1.62
Affected versions: v1.6x (Client)
Fixed: 1.63 | In OS breakdown; the last computer in a operating system group does not respond to double clicking
|
BugID# 47
| Found: v1.62
Affected versions: v1.6x (Client)
Fixed: 1.63 | Numbers in user reports in 'Domain Report' is not correctly formatted
|
BugID# 46
| Found: v1.61
Affected versions: v1.6 (Client)
Fixed: 1.62 | Send mail may not launch the mail application but a random window in DomainScan
|
BugID# 45
[Critical]
| Found: v1.61
Affected versions: v1.x (Service)
Fixed: 1.62 | Non-admin users not detected on Windows NT/2000. The WMI implementation in Windows prior to XP does not detect users unless they’re local administrators. Therefore, DomainScan may not show that a user is logged on.
|
BugID# 44
| Found: v1.61
Affected versions: v1.61
Fixed: 1.62 | Preferences: If a network path is entered in the path-fields, DomainScan will not recognize the path as a legal path, and the path will be cleared automatically.
| Workaround: To load a default database from a remote server, enter the name in the ‘Default’ entry in ‘Client.ini’. The same solution applies for the disk cache location (‘DiskCacheLocation’), although it is not recommended to use a remote server as DomainScan Client database cache. |
BugID# 43
| Found: v1.6
Affected versions: v1.5x (Client)
Fixed: 1.62 | Use of the ’Connect As’ option may cause the Find and WMI tools not to return data from clients. This is an error, caused by the use of alternative logon credentials, to a remote RPC server, where the callback from that server results in a security error
| Workaround: The ‘Connect As’ account must also be an administrative account on the computer from where the query is performed (This workaround may not work in all scenarios) |
BugID# 42
[Critical]
| Found: v1.52
Affected versions: v1.1x (Service)
Fixed: 1.6 | If DomainScan Service fails to complete the first scan, subsequent scans will report a “wrong database ID” failure (Event -105 in the Windows event log), and quit immediately. This will happen if DomainScan Service stops after it has created the static database (ds_store), but not the dynamic database (ds_dyn) before the stop error.
| Workaround: Delete the database files |
BugID# 41
| Found: v1.52
Affected versions: v1.5x (Client)
Fixed: 1.6 | The selection tree in Preferences does not update graphically when a node is collapsed, resulting in a graphical error in the presentation of the tree.
|
BugID# 40
| Found: v1.52
Affected versions: v1.12+ (Client)
Fixed: 1.6 | The ‘Show selected Time’ option will fail to present the right amount of days when the number of days extends one year (365 days).
|
BugID# 39
| Found: v1.52
Affected versions: v1.5x (Client)
Fixed: 1.6 | DomainScan will automatically insert a database name in the 'default database' field in Preferences, if the field is empty.
|
BugID# 38
| Found: v1.52
Affected versions: v1.5x (Client)
Fixed: 1.6 | In Domain Report, the IP range report does not format IP addresses into the a.b.c.d format, but presents the IP addresses as numbers.
|
BugID# 37
| Found: v1.52
Affected versions: v1.1x (Client)
Fixed: 1.6 | Wildcard searches (for instance in the search tools) may fail to include all computers, that the wildcard search should select, in the search.
|
BugID# 36
[Critical]
| Found: v1.51SR1
Affected versions: v1.51SR1
Fixed: 1.51 SR2 | DomainScan Services is installed with a wrong pathname (the path is correct, but the application names is duplicated – i.e. c:\programs files\domainscan\scanengine.exescanengine.exe).
|
BugID# 35
| Found: v1.51
Affected versions: v1.51 (Client)
Fixed: 1.51 SR1 | DomainScan might not recognize a correct path to a database, if the database name contains uppercase letters, but recognize it as a folder, and therefore append the database name to the otherwise correct path.
|
BugID# 34
| Found: v1.5
Affected versions: v1.5 (Client)
Fixed: 1.51 | The Domain Report document will always write that virtual servers are excluded – even if they are included.
|
BugID# 33
| Found: v1.5
Affected versions: v1.5 (Client)
Fixed: 1.51 | Images in the Domain Report are missing.
The image locations were altered at the last moment before release, which were not updated into the HTML generator, which means that the Domain Report file tries to locate the images in the help_domainscan/webpic folder, which is not present in the v1.5 | Workaround: Copy the webpic folder into the help_domainscan folder |
BugID# 32
| Found: v1.5
Affected versions: v1.5
Fixed: 1.51 | The warning text for users that has exceeded the allowed number of simultaneous logins may be (null) instead of the intended error message
|
BugID# 31
| Found: v1.12sr1
Affected versions: v1.0 -> v1.12sr1 (Client)
Fixed: 1.5 | The correct icon for offline servers is not shown. Instead, the icon for offline computers is shown.
|
BugID# 30
| Found: v1.12sr1
Affected versions: v1.1x -> v1.12sr1 (Client)
Fixed: 1.5 | If the computer information panel are showing virtual/cluster server information, and the panel is reused for a real computer, the panel fails to use correct captions. However, the correct information is shown.
| Workaround: Close the computer information panel and launch it again. |
BugID# 29
| Found: v1.12
Affected versions: v1.1x -> v1.12sr1 (Client)
Fixed: 1.5 | The 'Release Notes' shortcut launches Preferences instead of the release notes
| Workaround: Launch 'Release Notes' from the start menu |
BugID# 28
[Critical]
| Found: v1.12
Affected versions: v1.0 -> v1.12
Fixed: v1.12SR1 | Due to an overrun error, license keys may not validate, if the user name contains non-standard characters (ASCII values above 127)
Contact GH Software for a replacement key, if you encounter the problem. |
BugID# 27
| Found: v1.12
Affected versions: v1.1 -> v1.12 (Client)
Fixed: 1.5 | The list with Warning Receivers may be empty in the Scan Range Wizard
|
BugID# 26
| Found: v1.11
Affected versions: v1.0 -> v1.11 (Service)
Fixed: v1.12 | In special cases, where the Windows browse list is empty (0 computers are reported as being ‘online’ by Windows); DomainScan does not recognize this as an error, and continues to operate normally, which leads to the wrong conclusion that all computers are offline.
This situation may occur right after a reboot, where the Windows subsystem has just initialized but not yet received the browse list from the browse master.
This issue is already addressed to some level in the release notes, regarding installing DomainScan on domain controllers |
BugID# 25
| Found: v1.11
Affected versions: v1.11 (Client)
Fixed: 1.5 | Computer information and hardware browser may show the amount of installed RAM as 0MB (and free RAM as 4095TB)
A quick fix has been applied to DomainScan v1.12, but it does not resolve all cases |
BugID# 24
| Found: v1.11
Affected versions: v1.11 (Client)
Fixed: 1.5 | The Cache system may fail to sync with the database
Note: Reopened. Initial fix in v1.12 was not effective | Workaround: Disable cache or restart DomainScan Client |
BugID# 23
| Found: v1.11
Affected versions: v1.0 -> v1.11 (Client)
Fixed: v1.12 | Hardware browser will not freeze
|
BugID# 22
| Found: v1.1
Affected versions: v1.1 (Service)
Fixed: v1.11 | If a users exceeds his/hers number of simultaneous logins, the warning systems fails to list all computers in the email warning
| Workaround: Check DomainScan Client for user login information |
BugID# 21
| Found: v1.1
Affected versions: v1.1
Fixed: v1.11 | New port names are not remembered in the scan range wizard, and they can’t be edited
Note: Port numbers are added to scan ranges correctly | Workaround: Manually edit the ds_dyn.gdb database. Important: Stop the service while editing the database file |
BugID# 20
| Found: v1.1
Affected versions: v1.1 (Client)
Fixed: v1.11 | The list with warning receivers may suddenly be empty in the scan range wizard, even though warning receivers are defined
| Workaround: Restart DomainScan Client |
BugID# 19
| Found: v1.1
Affected versions: v1.1 (Client)
Fixed: v1.11 | Databases upgraded from DomainScan v1.x will not show ‘users’ in the usage graph for users. However, the graph is shown correctly
|
Bugs from DomainScan v1.0x can be found here
|
|
|
|
|
|
2003 - 2012 GHIT ApS (Formerly GH Software). Contact |
