never mind. found the "strftime" function and it works great

Thanks for reply i install bison-2.4.1-setup.exe and aslo set directory path plz tell me where is problems Running message compiler 1>MC: may only specify one message file to compile. 1>MC: may only specify one message file to compile. 1>MC: may only specify one message file to compile. 1>MC: may only specify one message file to compile. 1>Microsoft (R) Message Compiler  Version 1.12.2505 1>Copyright (c) Microsoft Corporation. All rights reserved. 1>usage: MC [-?aAcdnosuUvw] [-m maxmsglen] [-h dirspec] [-e extension] [-r dirspec] [-x dbgFileSpec] filename.mc 1>      -? - displays this message 1>      -a - input file is ANSI (default). 1>      -A - messages in .BIN file should be ANSI. 1>      -b - .BIN filename should have .mc filename_ included for uniqueness. 1>      -c - sets the Customer bit in all the message Ids. 1>      -d - FACILTY and SEVERITY values in header file in decimal. 1>            Sets message values in header to decimal initially. 1>      -e extension - Specify the extension for the header file. 1>                      From 1 - 3 chars. 1>      -h pathspec - gives the path of where to create the C include file 1>                    Default is . 1>      -m maxmsglen - generate a warning if the size of any message exceeds 1>                      maxmsglen characters. 1>      -n - terminates all strings with null's in the message tables. 1>      -o - generate OLE2 header file (use HRESULT definition instead of 1>            status code definition) 1>      -r pathspec - gives the path of where to create the RC include file 1>                    and the binary message resource files it includes. 1>                    Default is . 1>      -s - insert symbolic name as first line of each message. 1>      -u - input file is Unicode. 1>      -U - messages in .BIN file should be Unicode (default). 1>      -v - gives verbose output. 1>      -w - warns if message text contains non-OS/2 compatible inserts. 1>      -x pathspec - gives the path of where to create the .dbg C include 1>                        file that maps message Ids to their symbolic name. 1>      filename.mc - gives the names of a message text file 1>                    to compile. 1>      Generated files have the Archive bit cleared. 1>The system cannot find the path specified. 1>Project : error PRJ0019: A tool returned an error code from "Running message compiler"

Yes, you have to add all other nodes to trusted nodes list on  ISP_gateway. So in your case it's probably easier to disable trusted nodes checking. Best regards, Victor

Thank you!That will help a lot! ;D

Looks like incorrect handling of unicode characters during export. There are some lines looking like this: <message>%6 : Le Batch Farmsat sur la machine %n ne fonctionne plus suite &#xFFF cette erreur : %4</message> How does this message looks in it's original form? Best regards, Victor

Hi I am try to compile netxms-1.0.12 in vc 6 in window xp service pack 2 and facing these problems 1 fatal error C1083: Cannot open include file: 'winevt.h': No such file or directory Error executing cl.exe. First I installes Microsoft SDK 2003  and also try  Microsoft Visual Studio 2008 SDK but unable to solved the problem.  plz indicate version of sdk. 3 fatal error C1083: Cannot open include file: 'Scintilla.h': No such file or directory When I install scintilla  and try to compile . These errors occur   C:\Net XMS project\software\scintilla\lexlib\Accessor.h(23) : error C2504: 'LexAccessor' : base class undefined C:\Net XMS project\software\scintilla\lexlib\Accessor.h(26) : error C2629: unexpected 'class Accessor (' C:\Net XMS project\software\scintilla\lexlib\Accessor.h(26) : error C2238: unexpected token(s) preceding ';' C:\NET XMS PROJECT\SOFTWARE\SCINTILLA\INCLUDE\WindowAccessor.h(15) : error C2079: 'WindowAccessor' uses undefined class 'SCILEXER_EXPORTABLE' 3  Compiling .\parser.y 'bison' is not recognized as an internal or external command, operable program or batch file. Error executing c:\windows.0\system32\cmd.exe. PlZ tell me how it can besolved Also tell which satiable version of  netXms Best Regard

hello this solution doesn't help primary ip adress still then same Aigars

Thank you, Victor!

hi victor, so what are the parameters for the event template ? are they %1 - %99 ? Best Regards, Lindeamon

hi victor, 10x a lot.now i understand. Best Regards, Lindeamon

OK, I will try to use libnxcl to development.And put the questions in right section of the forum. Thanks!

Still Down

Thank you, Victor, now the things around syslog make sense to me. I will continue searching the forum for information about the various subagents and then will ask again :). Thanks for the summary! Vladi

Hi, you have a little mistake in the parser. It should be: <parser>       <rules>         <rule><match>(.*)</match><event params="1">100024</event></rule>       </rules> </parser> regards

Thanks okay, issue clarified. Best regards.

This message continues indefinitely until I restart the server. Best regards.

Hi. DB Upgrede ERROR. ----------------- c:\bin\NetXMS\bin>nxdbmgr upgrade NetXMS Database Manager Version 1.1.5 Upgrading database... Upgrading from version 105 to 217 Upgrading from version 217 to 218 Upgrading from version 218 to 219 SQL query failed ([Microsoft][SQL Server Native Client 10.0][SQL Server]There is  already an object named 'images' in the database.): CREATE TABLE images (  guid varchar(36) not null,  mimetype varchar(64) not nu ll,  name varchar(255) not null,  category varchar(255) not null,  protected integer default 0,      PRIMARY KEY(guid),  UNIQUE(name, category)) Rolling back last stage due to upgrade errors... Database upgrade failed ----------------- Manager Server: Windows 2008 SQL Server 2008 Please help it.

ohhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhhh i will give this a try cause i think i have tried it before and it did not worked. Best Regards, Lindeamon

During discovery is there anyway to automatically manage/unmanage interfaces based on the SNMP ifDesc value. For example if you had the words "manage" or "umanage" in the interface description field. Thanks Michael

Thank you Victor. It seems all work fine now. Best regards.