FREQUENTLY ASKED QUESTIONS

Summary

Console
Error message during Console loading
PCs are missing from the "Network" sub-Section of the "Inventory" Section
Error accessing Object "Detail"
Certain Objects seem to be missing from automatic trees
No information is displayed in the "Windows" and "Software" tabs
Certain files seem to be missing from the "Queries" or "Licenses" Sections
Missing pie from the "Summary" view
Incorrect results in the "Software" view
Incorrect results in the "Software tracking" view
The "Stop Synexsys audits" option in the "ADMIN" menu doesn't work
Thousands separator in numerical fields
Numerical custom fields display the local currency symbol
Certain reports are not displayed
Installation
Does Synexsys need to be installed on an actual Windows Server?
How can I install the various elements (Servers, Console, etc.) on different machines?
Error loading file midas.dll
PCs Audits

What conditions are required for the correct communication between the PCs and the Synexsys server?
A DOS window is displayed during remote audits (login script)
Error "File sxsiagent. exe not found" is displayed during agent launch via login script
Audit process is very slow
Non-consistent network names (HOSTNAME)
Error: the \OUTBOX folder is missing...
Can I execute audits if the WAN is in a VPN?
Centrino Processor not detected

Distribution of the Synexsys agent as a Windows service

Must a local agent be installed to perform audits?
Deploying agents as Windows services
No inventory upload
Deploying the agent as a service in a WorkGroup
Problems with deployment on a shared folder
Agent deployment - Error messages in the "Status" column

'CRON.TAB file cannot be found in master client \clientref'
'CONFIG.INI cannot be found in master client \clientref'

'Error creating target folder: <folder_UNC>'
'Error verifying existence of target folder: <folder_UNC>'

'The source folder \clientref does not exist: <path to \clientref>'
'Error copying files'
'Main file of remote agent does not exist: <UNC path to remote sxsiagent.exe>'

'Service Manager not available: <API error>'
'Service cannot be created: <API error>'
'Error opening service: <API error>'
'Service cannot be started: <API error>'
'Error checking service status: <API error>'
'Service is not started: <API error>'

'Other errors'

Various

Backup procedure save.bat or maint_db.bat does not work
Can I audit Linux, Unix, or Mac workstations?

 

You can enhance this list by sending your questions to support@synexsys.ch

Detail

Console
Error message during Console loading

If you encounter an error message such as: "I/O error for file \Synexsys\database\sxsi.fdb. Error while trying to open file", the access path to the database is incorrect. Check the parameters of file ..\console\config.ini. Key DBNAME must be similar to:

SERVER:DISK:\Program Files\Synexsys\database\sxsi.fdb

or even

DISK:\Program Files\Synexsys\database\sxsi.fdb , if you are launching the Console from the server.

If you launch the Synexsys Console remotely using a shortcut, check that the "Open with" shortcut option is correctly setup with a UNC path such as \\SERVER\SHARED\console\bin.

Your firewall may be keeping you from accessing the Synexsys server.
You don't have a C: drive on your PC.
PCs are missing from the "Network" sub-Section of the "Inventory" Section

Synexsys uses Windows's API to detect the network. The only difference is that Synexsys doesn't invoke the server that has been selected as "Master Browse", as the file explorer. Your PC's file explorer requests the "Master Browse" the last known status of the network neighborhood and displays it without checking if the visible machines are still connected. Instead, Synexsys dynamically refreshes the content every time.

It is also possible that the NETWORK= parameter of your Console's config.ini is not correctly defined. Use the Console setup program to modify it.
Error accessing Object "Detail"

You have not selected any Object.

Certain Objects are missing from automatic trees

If the "Hide the node <Not included>" option in the Admin menu is selected, automatic trees will not display the <Not included> node.

Automatic trees are created based on the fields belonging to Objects. If one of the fields of a given Object doesn't contain a value or contains a non-valid value, the Object is excluded from the tree and placed in the "Not included" system node. Since not included Objects are of no interest and displaying the <Not included> node requires time, Synexsys can skip this node. If you need to see all the Objects, simply deactivate the "Hide the <Not included> node" option.

No information is displayed in the Windows and Software tabs

You havn't performed any "Windows" and / or "Files" inventory for the selected PC.

I cannot see certain files in Synexsys although those files are present on the selected PC.
You havn't performed any "Files" inventory for the selected PC(s). Go to the PC's "Audits" tab and check whether the "Files audit" field contains a date.

You have executed a full inventory but you have excluded certain extensions and/or folders from the audit.

Go to the "Audit rules" sub-Section of the "Parameters" Section and check the filters.

A graphic is missing from the "Summary" view

No graphic is displayed in the "Summary" view when you select:

the node (All)
the last node of a branch
the main node of a tree that does not contain sub-levels
a node with sub-levels containing no Objects
one or several Objects
one or several nodes from the trees

Incorrect results in the "Software" view

You have selected a specific node from the classification trees. Try selecting the node (All) and refreshing the view.

No results are displayed for certain software tracking packages or the results displayed for certain packages do not match reality

Possible reasons:

You entered a wrong parameter, too exclusive or too restrictive in the definition of your package. For example, you entered a path where a specific file should be found. In this case, SXSi will count only the software that matches your condition. All others will be excluded.

The "Stop Synexsys audits" option in the "ADMIN" menu doesn't work

Make sure you have editing rights for folder ..\synexsys\server\outbox. Synexsys tries to write the task for stopping the inventory processes in this folder. If it isn't successful, the request cannot be transmitted to the agents.

Important: Selecting this option doesn’t stop inventory processes. Only the audits that start after inventory processes finish will be stopped. Therefore, it is likely many PCs will continue to upload data to the database after the request to stop audit processes is issued.

Thousands separator in numerical fields

You cannot define a thousands separator in the mask which is different from the one set in your Windows regional settings panel. If need be, the latter are used.

Numerical custom fields display the local currency symbol

You have deleted the default mask of the numerical field. Enter a value in the mask. For instance, "0" or "0.00", to force an integer or decimal number format. This will avoid the currency symbol from being displayed.

Certain reports are not displayed

Certain Synexsys reports require a local Excel viewer in order to be displayed. The viewer's local path should already be setup, but it could be incorrect.

Folder ..\synexsys\console\bin contains file sxsreport.inw. Open the file with the Notepad and check that the path to the XLSViewer is correct. For instance: XLSViewer=C:\Program Files\Microsoft Office\Office\excel.exe.

Installation
Does Synexsys need to be installed on a Windows Server?

If you expect to have more than 10 simultaneous connections from the Console to the database, you should consider installing a Server type OS. However, a Pro type OS is fine if you have less connections.

How can I install the various elements (Servers, Console, etc.) on different machines?

REMARK: The evaluation version does not allow you to install the different modules of Synexsys on several machines. All components are installed on a local PC.

In full versions, Synexsys' main installation program allows installing the various modules in different PCs.

However, you may launch the Console remotely in both versions. To do it, you must first share the ..\console folder. Then browse the network or connect a network reader to the folder and launch Console.exe as you would normally.

Error loading file Midas.dll

File MIDAS.DLL must be present in the \console\bin folder (console.exe). If midas.dll is present in this folder and you still receive the message, follow these instructions to register the DLL:

Copy MIDAS.DLL on the machine from which you want to execute the Console. For instance: in Winnt\system32.

Open a DOS window and access the folder where you copied MIDAS.DLL.

Enter the following command exactly as follows: regsvr32 midas.dll and then press ENTER.

Go back to Windows and re-launch the Synexsys Console.

PCs Audits
What conditions are required for the correct communication between the PCs and the Synexsys server?

A ping must return an answer if it is done from the audited PCs to Synexsys' FTP server. In addition to this, the communication port defined in the agent and Synexsys FTP server's setup must be open.

The port used by Synexsys for FTP transfers between the agent and the FTP server is 5026 by default. You can change this setting using the Synexsys Server setup program.

Regarding communication between the Synexsys Server and the Console and the database, the default port is 3050. It can be modified in Firebird's configuration file.

Concerning rights for the \CLIENT share, having a "read-only" access is enough. At NTFS level, you should only restrict "read-only" access to the shared folder(s).

A DOS window is displayed during remote audits (login script)

This is a common problem. You have invoked sxsiagent.exe from the login script's batch file (normally login.bat) without using the START command. If this is the case, the DOS window is displayed even if the task has been completed. To avoid this problem, you must use a syntax such as :

START /B /D “\\SERVER/CLIENT$\bin\agent" sxsiagent.exe /OPTIONS

If you have several operating systems in your company, then put the following code in your login script. It will launch the appropriate command line according to the local operating system :

call server_name\share_name\getwinver.exe
if errorlevel 6 goto wxp
if errorlevel 5 goto wnt
if errorlevel 1 goto w9x
if errorlevel 0 goto wother
:wxp
echo Processing agent for Windows 2000, Windows XP, Windows 2003
START /PRIORITY /B /D "\\server_name\share_name" sxsiagent.exe /H /W /S /FHy /FWy /FSy /FULL [/Dnn|/Thhmm] /DETAIL
goto end
:wnt
echo Processing agent for Windows NT
START /D\\server_name\share_name /PRIORITY /B sxsiagent.exe /H /W /S /FHy /FWy /FSy /FULL [/Dnn|/Thhmm] /DETAIL
goto end
:w9x
echo Processing agent for Windows 9x (Millenium, 98, 98SE et 95)
START \\server_name\share_name\sxsiagent.exe /H /W /S /FHy /FWy /FSy /FULL [/Dnn|/Thhmm] /DETAIL
goto end
:wother
echo OS Unknown
:end

IMPORTANT :

Note that the quotes only enclose the full path but not the executable nor the options.

Don't include an "EXIT" command in the batch file, since this would end the parent process (the DOS window) and therefore, the agent.

Omit options /B and /D in Win95 and Win98

In NT4, no space should be left between /D and the path. The path should also carry no spaces. Quotation marks are also not allowed. Any mistake in the command line could lead to an error such as: "File sxsiagent.exe cannot be found...".

"START" CANNOT BE EXECUTED FROM THE START / EXECUTE MENU. THE COMMAND MUST BE PLACED IN A BATCH FILE (.BAT) OR EXECUTED FROM A DOS WINDOW (START / EXECUTE / CMD)

Audit process is very slow

As any other task, an inventory needs CPU time and memory to be achieved. It is not possible to optimise the speed of an audit and the available resources at the same time. Nevertheless, SXSi offers several solutions to improve the time needed to audit a PC while minimizing the impact of this process on other resources.

The amount of time and the resources needed to complete an audit depends upon several factors:

The cycle frequency of each SXSi component (Agent, Server, FTP Server(s))

Possible Solution: shorten the interval between "wake-up" cycles. If there are no pending tasks, the SXSi components will use very little resources. "Wake-up" cycles can therefore be as frequent as required (5 minutes is a standard when the agent is executed as a service).

Nature of the audit (auditing files takes more time than a hardware audit)

Possible Solution: schedule audits separately by nature. For instance: everyday at login time: Hardware and Windows audit; everyday at noon (or at night): Files audit. You can use the agent delay capabilities to optimise audit scheduling parameters.

Volume of collected files (it is quite common to have 5 or 10 times more information in one PC than in another, depending on the machine's role)

Possible Solution: schedule audits separately by nature. Have a good file clean up and archiving policy.

CPU speed and load of the Synexsys server and the audited PC.

Possible Solution: adapt the performance of your Synexsys server to the volume of information it has to process.

On the client side, the SXSi agent does not use more resources than other processes, but audit processes can be greatly slowed down if an audit, an antivirus, and the user's activities all run simultaneously.

Possible Solution: schedule audits separately by nature. You can use the agent delay capabilities to optimise audit-scheduling parameters. You can also assign a lower or higher priority to the audit process (see SXSIRUN.EXE tool).

Antivirus. Some antivirus solutions control processes such as the agent's and slow-down their execution. Typically, an audit could experience a slow-down of 20 to 80 % due to an antivirus.

Possible Solution: try to set up your antivirus so it doesn't control the SXSi agent's activities. Schedule audits at off-peak times.

Limited resources on the client

Possible Solution: schedule "File" audits separately and use the agent delay capabilities to optimise scheduling parameters. You can also assign a lower or higher priority to the audit process (see SXSIRUN.EXE tool).

Some of the audited PCs are uploaded to Synexsys with their NetBIOS name and others with a DNS suffix

Possible reasons:

You have defined a DNS suffix for certain PCs.

Check these PCs' properties. In the "Network Identification" tab, click on the "Properties" button and then on the "More" button of the "Identification Changes" window. The "DNS Suffix and NETBIOS Computer Name" window contains a field named "Primary DNS suffix of this computer". If this field is not empty, the current workstation will upload with a name such as MYPC.MYDOMAIN.COM.

The \OUTBOX folder is missing...

If an error message such as the following appears when an ASAP audit is launched or REG/INI custom fields are created:

"The \OUTBOX folder of the Synexsys server is absent or doesn't contain the dummy.dat file. Check your setup"

and the folder exists and contains file dummy.dat, you must set up the Console's config.ini file correctly.

Go to ..:\Program Files\Synexsys\console\config and edit CONFIG.INI.

Under [DATABASE], adapt the path based on the local context:

OUTBOX=C:\Program Files\Synexsys\server\outbox (drive name if the Console is launched locally)
OUTBOX=\\SERVER\C$\Program Files\Synexsys\server\outbox (UNC name if the Console is launched remotely)

WARNING: You need editing rights for the outbox folder.

Can I execute audits if the WAN is in a VPN?

ISPs that manage their clients' VPNs are in charge of providing the network infrastructures to clients that do not wish to manage or acquire their own. Regarding Synexsys, this doesn't change anything.

In the practice, the rules are the same as those applied to a LAN. Assuring the communication between the audited PCs and Synexsys' FTP server is the most important (see the details above).

In a VPN, there may be more security rules and firewalls can be more restrictive. Your provider can open the required ports so communication between the various Synexsys elements is possible.

Centrino Processor not detected

Centrino is a trademark registered by Intel for a technology, and not for a processor. This technology is based on the combination of the following 3 components:

Processor Intel® Pentium® M
Intel® 855 chipset family
Connection RLAN Intel® PRO/2100

For more information, check the following sites:

http://www.intel.com/english/products/mobiletechnology/centrino/index.htm (English)
http://www.intel.com/francais/products/mobiletechnology/centrino/index.htm (French)

Distribution of the Synexsys agent as a Windows service
Must a local agent be installed to perform audits?

No. There is no need to install anything! It is advised that you execute Synexsys audits through your login script (network connection script).

Of course, you may also automatically distribute the Synexsys agent and execute it as a Windows service (a good method for auditing servers, for example), but in this case you will need to have GLOBAL ADMINISTRATOR rights and to be recognised as LOCAL ADMINISTRATOR by the PCs where the service is installed (other important aspects are discussed below).

Deploying agents as a Windows service

What happens when the SXSi agent is deployed as a service for the first time?

Once the deployment has concluded, SXSi records that the agent has been deployed as a service on the remote PC. A temporary key is created for each PC on which the agent has been deployed. This key is also recorded in the SXSi database. When the PCs' inventories are uploaded for the first time, the keys are matched and audit data is then uploaded. Then the temporary key is replaced for good by the SXSi's SID.

I deployed the agents but I do not see the audited PCs in the Console

Before anything else, make sure the agent has been correctly installed. No error messages should appear in the "Status" column of the deployment window. If the value of the "Service status" field of the "Audits" tab is "Deployed", it means the agent is correctly installed but the audit hasn't been uploaded yet.

Possible reasons:

You did not refresh the information displayed in the Console. Press F5 or use the "Refresh screen" option in the "Tools" menu to update the data.
You did not wait long enough. An inventory cycle can last from 5 minutes to several tens of minutes because the task is done in an asynchronous mode.
The expected information is still in the upload queue. Check the folder ..\server\inbox\. If there are several files, the information you are expecting is maybe still there.

The IP address (or HOSTNAME) of your Synexsys server does not match the one the agents are sending audit data to. Check that the IP address of the server is identical to the one you can find in the ..client\config\config.ini file on the audited workstations.

In this case, a FTPERROR.ERR should be found in the folder where the agent has been installed (i.e. C:\SXSI). If this is so, the sxsiagent.log, which is normally found at the root of drive C: will contain information concerning the communication problem.

The ftp server has not started. Check that the "Synexsys FTP Server" service is launched automatically.

In this case, a FTPERROR.ERR should be found in the folder where the agent has been installed (i.e. C:\SXSI). If this is so, sxsiagent.log, which is normally found at the root of drive C: will contain information concerning the communication problem.

The Synexsys server has not started. Check that the "Synexsys Server" service is launched automatically.
The transfer of audit files between the audited PC and the FTP server hasn't taken place. This indicates there is an FTP communication problem or that a firewall is protecting the FTP port.

The agent has not been launched in the PC to be audited.

The agent should appear as "Synexsys Agent" in the list of services. It must be launched and its parameters must be set to Automatic.

The machine(s) have crashed
Deployment in a WorkGroup

Microsoft fixes the followin policy concerning the access rights in the context of a WorkGroup:

If you want to deploy the agent as a service and be able to copy files, you must ensure that a local share such as "DISK_C", exists on the remote PC. SXSi has to copy some files to the PC before being able to register and run the service. There is no concept of administrative shares in a WorkGroup. That means you cannot use symbols such as the $ sign in a path. (i.e. C$).

Contrary to what is found in a NT Domain, there is no concept of Global Administrator (Domain Admin) in a workgroup. Therefore, the only way to access a remote PC with sufficient rights is to connect to it as the local administrator.

To be clear, the problems you could encounter in a WorkGroup context are not due to Synexsys but to the way Microsoft manages Workgroups. You would have the same problems with any other software.

There are several solutions to the problems that could occur when deployment is in a WorkGroup. For instance:

The best solution, of course, and not only at SXSi level, would be to manage PCs and users in a domain. A domain is very simple to create and offers many advantages compared to a WorkGroup.
Another solutions is to create a Local Administrator account (USER + PWD) as well as a share (i.e. DISK_C) on each machine. Then, connect to this account from your own machine and launch the SXSi Console. This way, you can distribute the agent as a service within the WorkGroup as if you were Domain Administrator.

A good alterative would be to run the agent from the Start menu or from the "run" key of the registry instead of "pushing" it as a service:

KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run

REMARK: if you were to manage accounts in a domain, you could launch the agent remotely through the connection script (Login script). This feature isn't possible in a WorkGroup.

You can also use AUTOEX.NT (replaces autoexec.bat) to run the agent. See the Windows Resource Kit for more details on AUTOEX.NT usage.
Problems with deployment on a shared folder

SXSi allows deploying the agent on a shared folder, although you should avoid using this functionality because if you deploy the agent on a specific share such as "DISK_C\SXSI" and not on an administrative share such as "C$\SXSI", the agent will be executed through a UNC (i.e. \\PC_1234\\DISK_C\sxsi\agent\bin\sxsiagent.exe ...) and not through a local path (C:\sxsi\agent\bin\sxsiagent.exe ...). This could lead to unwanted network traffic or an abnormal startup time on slow networks.

Agent deployment - Error messages in the "Status" column

Error messages:

'CRON.TAB file cannot be found in master client \clientref'
'CONFIG.INI file cannot be found in master client \clientref'

Possible reasons:

The path to the master client (syntax = ..\clientref) must be entered correctly in the "Path to 'Master Client'".

File \clientref\CONFIG\CONFIG.INI must exist and be consistent.

File \clientref\BIN\SERVICE\CRON.TAB must exist.

The "Target" parameter must have a meaning at UNC level (you may use the "$" = invisible).

The "TEMP" parameters must have a meaning at the target workstation local level (environment variables such as %TEMP are not always present. A local path such as C:\SXSI\TEMP is advised.).

Please note that the value of the SID parameter is found in the config.ini file in the client. Since there are differences between the Windows 95/98/Me/NT4/2000/XP/2003 platforms, you will normally use %windir so it is compatible with all OS.

Error messages:

'Error creating target folder: <folder_UNC>'
'Error verifying existence of target folder: <folder_UNC>'

Possible reasons:

The target machine must be switched on and visible through the NetBIOS layer of the network (the NetBIOS layer allows you to use UNCs).

The Windows session of the user pushing the agent from the Console must have sufficient rights to launch this operation. The user must normally be "Domain Administrator" to be able to access system shares (referenced by a "$"). Basically, the user pushing the agent must have the rights to create a folder on the target share.

Error messages:

'The source folder \clientref does not exist: <path to \clientref>'
'Error copying files'
'Main file of remote agent does not exist: <UNC path to remote sxsiagent.exe>'

Possible reasons:

The path to the master client \clientref must be correct.

The Windows session of the user pushing the agent from the Console must have sufficient rights to launch this operation. The user must normally be "Domain Administrator" to be able to access system shares (referenced by a "$"). Basically, the user pushing the agent must have the rights to create a folder on the target share.

Error messages:

'Service Manager not available: <API error>'

The API error can be one of the following:

'ERROR_ACCESS_DENIED'
'ERROR_DATABASE_DOES_NOT_EXIST'
'ERROR_INVALID_PARAMETER'
'<Unknown error: '+error_code+'>'

Possible reasons:

The Windows session of the user pushing the agent from the Console must have sufficient rights to launch this operation. The user must normally be "Domain Administrator" to be able to access system shares (referenced by a "$"). Basically, the user pushing the agent must have the rights to create a folder on the target share.

See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/service_functions.asp for more details.

Error messages:

'Service cannot be created: <API error>'

The API error can be one of the following:

'ERROR_ACCESS_DENIED'
'ERROR_CIRCULAR_DEPENDENCY'
'ERROR_DUP_NAME'
'ERROR_INVALID_HANDLE'
'ERROR_INVALID_NAME'
'ERROR_INVALID_PARAMETER'
'ERROR_INVALID_SERVICE_ACCOUNT'
'ERROR_SERVICE_EXISTS'
'<Unknown error: '+error_code+'>'

Possible reasons:

The Windows session of the user pushing the agent from the Console must have sufficient rights to launch this operation. The user must normally be "Domain Administrator" to be able to access system shares (referenced by a "$"). Basically, the user pushing the agent must have the rights to create a folder on the target share.

See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/service_functions.asp for more details.

Error messages:

'Error opening service: <API error>'

The API error can be one of the following:

'ERROR_ACCESS_DENIED'
'ERROR_INVALID_HANDLE'
'ERROR_INVALID_NAME'
'ERROR_SERVICE_DOES_NOT_EXISTS'
'<Unknown error: '+error_code+'>'

Possible reasons:

The Windows session of the user pushing the agent from the Console must have sufficient rights to launch this operation. The user must normally be "Domain Administrator" to be able to access system shares (referenced by a "$"). Basically, the user pushing the agent must have the rights to create a folder on the target share.

See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/service_functions.asp for more details.

Error messages:

'Service cannot be started: <API error>'

The API error can be one of the following:

'ERROR_ACCESS_DENIED'
'ERROR_INVALID_HANDLE'
'ERROR_PATH_NOT_FOUND'
'ERROR_SERVICE_ALREADY_RUNNING'
'ERROR_SERVICE_DATABASE_LOCKED'
'ERROR_SERVICE_DEPENDENCY_DELETED'
'ERROR_SERVICE_DEPENDENCY_FAIL'
'ERROR_SERVICE_DISABLED'
'ERROR_SERVICE_LOGON_FAILED'
'ERROR_SERVICE_MARKED_FOR_DELETE'
'ERROR_SERVICE_NO_THREAD'
'ERROR_SERVICE_REQUEST_TIMEOUT'
'<Unknown error: '+error_code+'>'

Possible reasons:

The Windows session of the user pushing the agent from the Console must have sufficient rights to launch this operation. The user must normally be "Domain Administrator" to be able to access system shares (referenced by a "$"). Basically, the user pushing the agent must have the rights to create a folder on the target share.

See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/service_functions.asp for more details.

Error messages:

'Error checking service status: <API error>'
'Service is not started: <API error>'

The API error can be one of the following:

'ERROR_ACCESS_DENIED'
'ERROR_INVALID_HANDLE'
'SERVICE_STOPPED'
'SERVICE_START_PENDING'
'SERVICE_STOP_PENDING'
'SERVICE_CONTINUE_PENDING'
'SERVICE_PAUSE_PENDING'
'SERVICE_PAUSED'
' <Unknown error: '+error_code+'>'

Possible reasons:

The Windows session of the user pushing the agent from the Console must have sufficient rights to launch this operation. The user must normally be "Domain Administrator" to be able to access system shares (referenced by a "$"). Basically, the user pushing the agent must have the rights to create a folder on the target share.

See
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dllproc/base/service_functions.asp for more details.

Other errors:

In all other error cases, the exception manager will display the following in the "Status" column:

'ERROR: exception_error_message'

Various
Backup procedure save.bat or maint_db.bat does not work

At times, if the BAT files are not directly executed from the server's DOS prompt, they do not work unless the path that makes reference to the database file is modified.

Gbak.exe -b -ignore -user sysdba -password masterkey "..\..\database\sxsi.fdb" "..\..\database\sxsi.gbk"

becomes

Gbak.exe -b -ignore -user sysdba -password masterkey "SERVER:DISK:\program files\synexsys\database\sxsi.fdb" "..\..\database\sxsi.gbk"

and

Gbak.exe -replace -ignore -user sysdba -password masterkey "..\..\database\sxsi.gbk" "..\..\database\sxsi.fdb"

becomes

Gbak.exe -replace -ignore -user sysdba -password masterkey "..\..\database\sxsi.gbk" SERVER:DISK:\program files\synexsys\database\sxsi.fdb"

The .gbk file's path should not be changed.

Can I audit Linux, Unix or Mac workstations?

Not yet, but this functionality will come soon for Synexsys Inventory. However, you can audit any type of network device with Synexsys Network Audit at IP, MAC, NetBIOS, and SNMP level.

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

 

Last Update: 15.03.2005