Re: Error using rrrchive
Hi Misi Thanks for providing the 6.3 version. I've just ran it against 2 records that had failed with version 7.0 and they both worked. I'm now running against a bigger batch (5k records) that had failed before. Let's see it the good results keep coming! Unfortunately I couldn't find out why the records are failing with version 7.0. Please let me know if you want me to send any log file or data sample, just in case you want to dig deeper on this issue. I will obviously keep you informed on the final result. Once again, thanks very much for your assistance Cheers Rafael Bertolini -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Misi Mladoniczky Sent: 27 July 2010 16:47 To: arslist@ARSLIST.ORG Subject: Re: Error using rrrchive Hi, My guess is that the caracters encoded might be the problem. RRR|Chive leaves to the ARAPI to do the character conversion, but if the target database does not support a specific character, you might get a problem. I guess... I also guess that in version 5.x of the AR System, character encodings were not strictly enforced, and that bad characters could have ended up in the database. The bad codes could be something that got there on even older versions of your system. When you go via ARX-files, the character codes are rechecked, and possibly cleaned, before the import. I will send you a private mail with the URL to the 6.3-version of RRR|Chive, so you can test that as well. Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia: * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. Hi Misi Yes, I could set ARAPILOGGING on the current version and it generated the log file, but as you expected, no really useful information was provided (just the failed ARMergeEntry with no description on why it failed). The faulty records always fail. I can use qual to try to migrate only one faulty record and it always fails with the same message. (ARERR 91) I then exported the faulty record and imported it into the new server and I noticed something strange: on the original server I have some Japanese (I think) characters and they were imported as ? characters. (I can see the Japanese characters in the ARX file). Anyway, I can see records that were migrated successfully and have Japanese characters (not as many as this one though) and I can also see records that failed to migrate and don't seem to have any Japanese characters, so not sure it's related to the problem. If possible, I'd like to test with the 6.3 version, just to try all the possibilities. I'm really sorry to keep bugging you with this. Thanks very much for all your assistance. Regards, Rafael Bertolini Consultant Fusion Business Solutions (UK) Ltd Tel: +44 208 8146177 Mob: +44 7500 441522 www.fusion.co.uk Fusion is the largest consultancy in Europe that focuses exclusively on BMC Software solutions -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Misi Mladoniczky Sent: 27 July 2010 12:17 To: arslist@ARSLIST.ORG Subject: Re: Error using rrrchive Hi, ARAPILOGGING exists for old versions as well, but may not be well documented. Follow the information for 7.5 ARAPILOGGING. I do not think that you will get much out of that though, as the failing call is ARMergeEntry, and we get the error message... The only thing I can think of is incompatibility issues between your 5.x server and the 7.0 API, and that for the ARGetEntry for some reason give us a corrupt structure. Does the exact same records fail each time? Have you tried to export one of the problematic records to an ARX-file (ARUser) and the importing it with ARImport? I may be able to supply a 6.3-API version of RRR|Chive that may work differently. Any API should be working 2 versions backwards and 2 versions forward, at least. Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia: * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. HI Misi Thanks for your reply. I took a look at ARERR91 description and then checked the handlers on my windows server and it seems to be ok. Answering your questions, one server is version 5 and the other 7.1. I'm migrating data from an archive form with no workflow related to it. In the server error log file there's no error at all. I also enabled the API log on the server and I can see the ARGetEntry and a ARMergeEntry calls as you explained, but again, no error at all (I guess the failed records are failing before
Re: Error using rrrchive
HI Misi Thanks for your reply. I took a look at ARERR91 description and then checked the handlers on my windows server and it seems to be ok. Answering your questions, one server is version 5 and the other 7.1. I'm migrating data from an archive form with no workflow related to it. In the server error log file there's no error at all. I also enabled the API log on the server and I can see the ARGetEntry and a ARMergeEntry calls as you explained, but again, no error at all (I guess the failed records are failing before these two calls). Taking a look at the troubleshooting guide, I see API 7.5 has a client-side ARAPILOGGING environment variable that we can be set to generate client-side logs. However, I suspect the rrrchive version I have is running with API 7.0 (arapi70.dll) and checking this version troubleshooting guide, there's no mention to this functionality. Just wondering if there's a new rrrchive that uses API 75? Again, many thanks for your assistance. I'll continue to try to find different ways to generate different logs to see if any of them will help me to find the problem. Regards, Rafael Bertolini Consultant Fusion Business Solutions (UK) Ltd Tel: +44 208 8146177 Mob: +44 7500 441522 www.fusion.co.uk Fusion is the largest consultancy in Europe that focuses exclusively on BMC Software solutions -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Misi Mladoniczky Sent: 26 July 2010 14:14 To: arslist@ARSLIST.ORG Subject: Re: Error using rrrchive Hi, This is what the error message means: http://rrr.se/cgi/arerrr?n=91 The debug-level does not improve information, as this is a BMC-generated error message. Something goes wrong in the RPC-call to the server, all encapsulated inside the AR-API supplied by BMC. In general, rrrchive just performs an ARGetEntry and a ARMergeEntry call to the server, not modifying the actual data. The problem has to be found somewhere on the target-server. Which version do the two servers have? Do you use the target_disable_merge_fltr=YES? If not, there may be merge-filters that cause the problem. Do you have anything in the server-error-log on the target server? Any threads crashing? I would try to increase logging on the Remedy-server to get more info. What do you other people have to say about ARERR 91? The verifydata and verifyattachents is something that happens after the ARMergeEntry to the target server. In other words after you get the ARERR 91. These options are useful only if you do not rely on the AR-API to give an error message if things fail. It rereads the target record created and compares it to the original. Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia: * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. Hi I'm using rrrchive to migrate some data between two servers. In general, it's working just fine but some records (around 5%) fail to migrate with the following log: rrrchive: 2010-07-22 11:55:14, type=ARS, level=ERROR, file=rrrchive.cpp, line=417 ARMergeEntry(server=servername, form=form name, entry=A02) API CALL SEVERITY: AR_RETURN_ERROR, failure, status contains details ARStatusList: contains 1 messages Number: ARERR 91 Message: Cannot open catalog; Message number = 91 Append: RPC: Can't encode arguments I've tried to increase the log level to DEBUG but there's no additional log being generated. I've also tried using verifydata and verifyattachments, all with the same result. I can see some records with attachment were migrated fine (and some records without attachment failed) so I don't think it's attachment related. Any ideas on how to get a more detailed log or what could be causing this error? Cheers Rafael ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are -- This message was scanned by ESVA and is believed to be clean. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: Error using rrrchive
Hi Misi Yes, I could set ARAPILOGGING on the current version and it generated the log file, but as you expected, no really useful information was provided (just the failed ARMergeEntry with no description on why it failed). The faulty records always fail. I can use qual to try to migrate only one faulty record and it always fails with the same message. (ARERR 91) I then exported the faulty record and imported it into the new server and I noticed something strange: on the original server I have some Japanese (I think) characters and they were imported as ? characters. (I can see the Japanese characters in the ARX file). Anyway, I can see records that were migrated successfully and have Japanese characters (not as many as this one though) and I can also see records that failed to migrate and don't seem to have any Japanese characters, so not sure it's related to the problem. If possible, I'd like to test with the 6.3 version, just to try all the possibilities. I'm really sorry to keep bugging you with this. Thanks very much for all your assistance. Regards, Rafael Bertolini Consultant Fusion Business Solutions (UK) Ltd Tel: +44 208 8146177 Mob: +44 7500 441522 www.fusion.co.uk Fusion is the largest consultancy in Europe that focuses exclusively on BMC Software solutions -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Misi Mladoniczky Sent: 27 July 2010 12:17 To: arslist@ARSLIST.ORG Subject: Re: Error using rrrchive Hi, ARAPILOGGING exists for old versions as well, but may not be well documented. Follow the information for 7.5 ARAPILOGGING. I do not think that you will get much out of that though, as the failing call is ARMergeEntry, and we get the error message... The only thing I can think of is incompatibility issues between your 5.x server and the 7.0 API, and that for the ARGetEntry for some reason give us a corrupt structure. Does the exact same records fail each time? Have you tried to export one of the problematic records to an ARX-file (ARUser) and the importing it with ARImport? I may be able to supply a 6.3-API version of RRR|Chive that may work differently. Any API should be working 2 versions backwards and 2 versions forward, at least. Best Regards - Misi, RRR AB, http://www.rrr.se Products from RRR Scandinavia: * RRR|License - Not enough Remedy licenses? Save money by optimizing. * RRR|Log - Performance issues or elusive bugs? Analyze your Remedy logs. Find these products, and many free tools and utilities, at http://rrr.se. HI Misi Thanks for your reply. I took a look at ARERR91 description and then checked the handlers on my windows server and it seems to be ok. Answering your questions, one server is version 5 and the other 7.1. I'm migrating data from an archive form with no workflow related to it. In the server error log file there's no error at all. I also enabled the API log on the server and I can see the ARGetEntry and a ARMergeEntry calls as you explained, but again, no error at all (I guess the failed records are failing before these two calls). Taking a look at the troubleshooting guide, I see API 7.5 has a client-side ARAPILOGGING environment variable that we can be set to generate client-side logs. However, I suspect the rrrchive version I have is running with API 7.0 (arapi70.dll) and checking this version troubleshooting guide, there's no mention to this functionality. Just wondering if there's a new rrrchive that uses API 75? Again, many thanks for your assistance. I'll continue to try to find different ways to generate different logs to see if any of them will help me to find the problem. Regards, Rafael Bertolini Consultant Fusion Business Solutions (UK) Ltd Tel: +44 208 8146177 Mob: +44 7500 441522 www.fusion.co.uk Fusion is the largest consultancy in Europe that focuses exclusively on BMC Software solutions -Original Message- From: Action Request System discussion list(ARSList) [mailto:arsl...@arslist.org] On Behalf Of Misi Mladoniczky Sent: 26 July 2010 14:14 To: arslist@ARSLIST.ORG Subject: Re: Error using rrrchive Hi, This is what the error message means: http://rrr.se/cgi/arerrr?n=91 The debug-level does not improve information, as this is a BMC-generated error message. Something goes wrong in the RPC-call to the server, all encapsulated inside the AR-API supplied by BMC. In general, rrrchive just performs an ARGetEntry and a ARMergeEntry call to the server, not modifying the actual data. The problem has to be found somewhere on the target-server. Which version do the two servers have? Do you use the target_disable_merge_fltr=YES? If not, there may be merge-filters that cause the problem. Do you have anything in the server-error-log on the target server? Any threads crashing? I would try to increase logging on the Remedy-server to get more info. What do you other people have to say about
Error using rrrchive
Hi I'm using rrrchive to migrate some data between two servers. In general, it's working just fine but some records (around 5%) fail to migrate with the following log: rrrchive: 2010-07-22 11:55:14, type=ARS, level=ERROR, file=rrrchive.cpp, line=417 ARMergeEntry(server=servername, form=form name, entry=A02) API CALL SEVERITY: AR_RETURN_ERROR, failure, status contains details ARStatusList: contains 1 messages Number: ARERR 91 Message: Cannot open catalog; Message number = 91 Append: RPC: Can't encode arguments I've tried to increase the log level to DEBUG but there's no additional log being generated. I've also tried using verifydata and verifyattachments, all with the same result. I can see some records with attachment were migrated fine (and some records without attachment failed) so I don't think it's attachment related. Any ideas on how to get a more detailed log or what could be causing this error? Cheers Rafael ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug10 www.wwrug.com ARSlist: Where the Answers Are
Re: Slow responses
Joe, I don't know if it's your case, but once my users were having slowness anytime they save a request in which a diary field was modified (if no diary field was modified, no slowness). The issue was an Oracle parameter. If it's your case, I can try to find what parameter it was... Rafael Bertolini Soria, Joe wrote: I think I 'accidentally' found the issue. I turned off confirmation of a new request, created several incidents and did not experience any slowness. I turned confirmation back on and it takes 10-50 seconds to come back. How in the world do I fix that? -Original Message- From: Soria, Joe Sent: Fri 3/30/2007 11:01 AM To: arslist@ARSLIST.ORG Cc: Subject:Slow responses Listers, I am baffled here and need some guidance. We are running ARS 6.3 patch 20 on solaris. The user community experiences extreme slowness when submitting on any form. We have verified that there is no latency on our network, we have also verified that our database is performing at a very good rate. Our app server and db server reside on the same subnet. I have performed client side logging, as well as filter/sql/api logging. Both our app server and db server are experience low load on both cpu memory. I am not seeing any significant load of transactions nor have I been able to isolate the slowness. I have rtfm and am coming to you as a last resort (before calling support, argh). Any ideas on troubleshooting this is greatly appreciated. Joe ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are -- * Rafael Bertolini * System Analyst Ícaro Technologies http://www.icaro.com.br *Work:* +55 19 3731 8308 *E-mail:* [EMAIL PROTECTED] *Fax:* +55 19 3731 8304 / A informação transmitida destina-se apenas à pessoa ou entidade a quem foi endereçada e pode conter informação confidencial, legalmente protegida e para conhecimento exclusivo do destinatário. Se o leitor desta advertência não for o seu destinatário, fica ciente de que sua leitura, divulgação, distribuição ou cópia é estritamente proibida. Caso a mensagem tenha sido recebida por engano, favor comunicar ao remetente e apagar o texto do computador. Este ambiente está sujeito a monitoramento. //The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. This environment is subject to monitoring. / ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
How to manage duplicated problems?
Hi all! Using ITSM 6.0, what do you think is the best way to manage duplicated problems? Let's say two different support staff find out a problem and creates a problem register into Help Desk form (same CTI). ITSM 6.0 doesn't prevent this. Unlike duplicated incidentes (where we can mark one as duplicate of the other), for problems we don't have the Mark as duplicate. Do you think is enough to simply related them (under Related Items page)? Other suggestions? Thanks in advanced! Rafael Bertolini -- * Rafael Bertolini * System Analyst Ícaro Technologies http://www.icaro.com.br *Work:* +55 19 3731 8308 *E-mail:* [EMAIL PROTECTED] *Fax:* +55 19 3731 8304 / A informação transmitida destina-se apenas à pessoa ou entidade a quem foi endereçada e pode conter informação confidencial, legalmente protegida e para conhecimento exclusivo do destinatário. Se o leitor desta advertência não for o seu destinatário, fica ciente de que sua leitura, divulgação, distribuição ou cópia é estritamente proibida. Caso a mensagem tenha sido recebida por engano, favor comunicar ao remetente e apagar o texto do computador. Este ambiente está sujeito a monitoramento. //The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. This environment is subject to monitoring. / ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: AR System Alert (Notifier) No pop-up, sound, etc.
Hi! I've just have a similar issue. In my case, it was caused by a firewall between the server and the clients. The server needs an *entrant connection* to the client machine, so the alert can pop-up. If this connection does not exist, the user STILL can log in in the alert tool and click in the refresh button to get news alerts (because the connection user machine - server exists). To get the entrant connection on the client machines, we need to set an specific port for alert, in the Tools-Options of alert tool. HTH Rafael Bertolini Rick Cook wrote: I assume that you configured the Alert tool to notify the user in the way(s) they preferred? Rick -Original Message- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Hendershot,Bruce D. Sent: Sunday, February 18, 2007 6:11 AM To: arslist@ARSLIST.ORG Subject: AR System Alert (Notifier) No pop-up, sound, etc. We just upgraded our servers to 7.0.01 but our clients are on 5.1. Although messages are getting into the Alert Events table they do not cause the tool to display a message, flash the icon or make a sound on user's desktops. We had problems with this for a subset of users even when the servers were also 5.1, but now it doesn't seem to work for anyone. We tried installing just the 7.0 version of Alert (not User) but that didn't help. We'll be upgradeing User and Alerts to 7 in a few weeks but I have some users that rely on the message from the Alert tool. Any ideas would be welcome. Thanks. ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are -- * Rafael Bertolini * System Analyst Ícaro Technologies http://www.icaro.com.br *Work:* +55 19 3731 8308 *E-mail:* [EMAIL PROTECTED] *Fax:* +55 19 3731 8304 / A informação transmitida destina-se apenas à pessoa ou entidade a quem foi endereçada e pode conter informação confidencial, legalmente protegida e para conhecimento exclusivo do destinatário. Se o leitor desta advertência não for o seu destinatário, fica ciente de que sua leitura, divulgação, distribuição ou cópia é estritamente proibida. Caso a mensagem tenha sido recebida por engano, favor comunicar ao remetente e apagar o texto do computador. Este ambiente está sujeito a monitoramento. //The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. This environment is subject to monitoring. / ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers Are
Re: Java API - ARGetQualifier
And the problem was gone!!!
Thank you, Sebastian!!
de Man Sebastiaan wrote:
Hi Rafael,
I can't really see where the problem is, however here is my method of getting a
QualifierInfo, which I've copied and pasted several times over different
projects and always works, perhaps you're not getting all the fields?
In my example the String GuiNr has the GUID field value in it, and I use it to
find the entry. This compiles and works for v7.0
NameID Schema_name = new SchemaKey(AR System Email Messages));
FieldFactory fieldFactory = FieldFactory.getFactory();
FieldCriteria fCrit = new FieldCriteria();
fCrit.setRetrieveAll(true);
// We'd like all types of fields
Timestamp timestamp = new Timestamp(0);
FieldListCriteria fListCrit = new FieldListCriteria(Schema_name,
timestamp, FieldType.AR_ALL_FIELD);
Field[] field = FieldFactory.findObjects(context, fListCrit, fCrit);
QualifierInfo qal = Util.ARGetQualifier(context, '179' = \ + GuiNr + \, field, null, Constants.AR_QUALCONTEXT_DEFAULT);
Hope this helps,
Sebastiaan de Man
Softlab Schweiz AG
-Original Message-
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED]
On Behalf Of Rafael Bertolini
Sent: Donnerstag, 2. November 2006 18:33
To: arslist@ARSLIST.ORG
Subject: Re: Java API - ARGetQualifier
Hi Jarl!
Got the same problem using condition = \'Status\' = \New\;
MessageType: 2
MessageNum: 1
MessageText: Error while parsing the qualifier (Error Code: 6)
AppendedText: Error position: 8
at com.remedy.arsys.api.Proxy.ARGetQualifier(Native Method)
at com.remedy.arsys.api.Util.ARGetQualifier(Util.java:1822)
at br.com.icaro.ars.data.ARSForm.findEntries(ARSForm.java:271)
at br.com.icaro.ars.data.ARSForm.main(ARSForm.java:388)
:(
Jarl Grøneng wrote:
Try this:
condition = \'Status\' = \New\;
--
Jarl
On 11/2/06, Rafael Bertolini [EMAIL PROTECTED] wrote:
Hello guys!
I'm having problems to do a qualificated search using java api (ARS
6.3). Here is the code:
.
.
.
condition = 'Status' = \New\;
try {
QualifierInfo qualifier =
Util.ARGetQualifier(server, condition, fields,
fields, Constants.AR_QUALCONTEXT_DEFAULT);
.
.
.
And here is the exception:
MessageType: 2
MessageNum: 1
MessageText: Error while parsing the qualifier (Error Code: 6)
AppendedText: Error position: 8
at com.remedy.arsys.api.Proxy.ARGetQualifier(Native Method)
at com.remedy.arsys.api.Util.ARGetQualifier(Util.java:1822)
at br.com.icaro.ars.data.ARSForm.findEntries(ARSForm.java:271)
It's complainning in the single quote after field's name. I've
already try with field ID like this:
condition = '7' = \New\;
but then it's complain at position 3.
I could print the fields of the form using api, and yes, there is the
status field (7) there ;)
Any ideas?
--
* Rafael Bertolini *
System Analyst
Ícaro Technologies
http://www.icaro.com.br *Work:* +55 19 3731 8308
*E-mail:* [EMAIL PROTECTED]
*Fax:* +55 19 3731 8304
/
A informação transmitida destina-se apenas à pessoa ou entidade a
quem foi endereçada e pode conter informação confidencial, legalmente
protegida e para conhecimento exclusivo do destinatário. Se o leitor
desta advertência não for o seu destinatário, fica ciente de que sua
leitura, divulgação, distribuição ou cópia é estritamente proibida.
Caso a mensagem tenha sido recebida por engano, favor comunicar ao
remetente e apagar o texto do computador. Este ambiente está sujeito
a monitoramento.
//The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential and/or
privileged material. Any review, retransmission, dissemination or
other use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient
is prohibited. If you received this in error, please contact the
sender and delete the material from any computer. This environment is
subject to monitoring. /
_
__
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:Where the Answers Are
__
_
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:Where the Answers Are
--
* Rafael Bertolini *
System Analyst
Ícaro Technologies
http://www.icaro.com.br *Work:* +55 19 3731 8308
*E-mail:* [EMAIL PROTECTED]
*Fax:* +55 19 3731 8304
/
A informação transmitida destina-se apenas à pessoa ou entidade a quem
foi endereçada e pode conter informação confidencial, legalmente
protegida e para conhecimento exclusivo do destinatário. Se o leitor
desta advertência não for o seu destinatário, fica ciente de que sua
leitura, divulgação, distribuição ou cópia é estritamente proibida. Caso
a mensagem tenha sido recebida por
Re: Java API - ARGetQualifier
Hi Jarl!
Got the same problem using condition = \'Status\' = \New\;
MessageType: 2
MessageNum: 1
MessageText: Error while parsing the qualifier (Error Code: 6)
AppendedText: Error position: 8
at com.remedy.arsys.api.Proxy.ARGetQualifier(Native Method)
at com.remedy.arsys.api.Util.ARGetQualifier(Util.java:1822)
at br.com.icaro.ars.data.ARSForm.findEntries(ARSForm.java:271)
at br.com.icaro.ars.data.ARSForm.main(ARSForm.java:388)
:(
Jarl Grøneng wrote:
Try this:
condition = \'Status\' = \New\;
--
Jarl
On 11/2/06, Rafael Bertolini [EMAIL PROTECTED] wrote:
Hello guys!
I'm having problems to do a qualificated search using java api (ARS
6.3). Here is the code:
.
.
.
condition = 'Status' = \New\;
try {
QualifierInfo qualifier =
Util.ARGetQualifier(server, condition, fields, fields,
Constants.AR_QUALCONTEXT_DEFAULT);
.
.
.
And here is the exception:
MessageType: 2
MessageNum: 1
MessageText: Error while parsing the qualifier (Error Code: 6)
AppendedText: Error position: 8
at com.remedy.arsys.api.Proxy.ARGetQualifier(Native Method)
at com.remedy.arsys.api.Util.ARGetQualifier(Util.java:1822)
at br.com.icaro.ars.data.ARSForm.findEntries(ARSForm.java:271)
It's complainning in the single quote after field's name. I've already
try with field ID like this:
condition = '7' = \New\;
but then it's complain at position 3.
I could print the fields of the form using api, and yes, there is the
status field (7) there ;)
Any ideas?
--
* Rafael Bertolini *
System Analyst
Ícaro Technologies
http://www.icaro.com.br *Work:* +55 19 3731 8308
*E-mail:* [EMAIL PROTECTED]
*Fax:* +55 19 3731 8304
/
A informação transmitida destina-se apenas à pessoa ou entidade a quem
foi endereçada e pode conter informação confidencial, legalmente
protegida e para conhecimento exclusivo do destinatário. Se o leitor
desta advertência não for o seu destinatário, fica ciente de que sua
leitura, divulgação, distribuição ou cópia é estritamente proibida. Caso
a mensagem tenha sido recebida por engano, favor comunicar ao remetente
e apagar o texto do computador. Este ambiente está sujeito a
monitoramento.
//The information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer. This environment is subject to monitoring. /
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:Where the Answers Are
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
ARSlist:Where the Answers Are
--
* Rafael Bertolini *
System Analyst
Ícaro Technologies
http://www.icaro.com.br *Work:* +55 19 3731 8308
*E-mail:* [EMAIL PROTECTED]
*Fax:* +55 19 3731 8304
/
A informação transmitida destina-se apenas à pessoa ou entidade a quem
foi endereçada e pode conter informação confidencial, legalmente
protegida e para conhecimento exclusivo do destinatário. Se o leitor
desta advertência não for o seu destinatário, fica ciente de que sua
leitura, divulgação, distribuição ou cópia é estritamente proibida. Caso
a mensagem tenha sido recebida por engano, favor comunicar ao remetente
e apagar o texto do computador. Este ambiente está sujeito a monitoramento.
//The information transmitted is intended only for the person or entity
to which it is addressed and may contain confidential and/or privileged
material. Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by persons or
entities other than the intended recipient is prohibited. If you
received this in error, please contact the sender and delete the
material from any computer. This environment is subject to monitoring. /
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:Where the Answers
Are
Error sending email
Hi all!!! I've created a SLA that sends an email after sometime a incident is created. It also sends an alert. The SLA is working, since I've got the alert, but no email was sent. In the AR System Email Error Logs, I've got this message Invalid Addresses; nested exception is: class javax.mail.SendFailedException: 550 5.7.1 [EMAIL PROTECTED]... Relaying denied javax.mail.SendFailedException: Invalid Addresses; nested exception is: class javax.mail.SendFailedException: 550 5.7.1 [EMAIL PROTECTED]... Relaying denied at com.sun.mail.smtp.SMTPTransport.rcptTo(SMTPTransport.java:848) at com.sun.mail.smtp.SMTPTransport.sendMessage(SMTPTransport.java:323) at com.remedy.arsys.emaildaemon.SenderModule.sendMessage(SenderModule.java:74) at com.remedy.arsys.emaildaemon.CreatorModule.createMessage(CreatorModule.java:1468) at com.remedy.arsys.emaildaemon.CreatorModule.doWork(CreatorModule.java:360) at com.remedy.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:268) at java.lang.Thread.run(Thread.java:534) It says invalid addresses, but the email [EMAIL PROTECTED] is correct (mine). What else could be? ARS 6.3 Solaris 8 TIA, Rafael Bertolini -- * Rafael Bertolini * System Analyst Ícaro Technologies http://www.icaro.com.br *Work:* +55 19 3731 8308 *E-mail:* [EMAIL PROTECTED] *Fax:* +55 19 3731 8304 / A informação transmitida destina-se apenas à pessoa ou entidade a quem foi endereçada e pode conter informação confidencial, legalmente protegida e para conhecimento exclusivo do destinatário. Se o leitor desta advertência não for o seu destinatário, fica ciente de que sua leitura, divulgação, distribuição ou cópia é estritamente proibida. Caso a mensagem tenha sido recebida por engano, favor comunicar ao remetente e apagar o texto do computador. Este ambiente está sujeito a monitoramento. //The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. This environment is subject to monitoring. / ___ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
Re: OT: Dell laptop battery recall
** https://www.dellbatteryprogram.com/Identify.aspx At this link you can verify if your battery will explode ;) Timothy Powell wrote: ** Just saw this pop up on the Dell website. Since so many of us use Dell laptops, I thought I'd pass it on. I'm sure that there will be a rush on available batteries and the sooner you get your replacement order in the better. https://www.dellbatteryprogram.com/ Regards to the list. Tim Powell __20060125___This posting was submitted with HTML in it___ -- Rafael Bertolini System Analyst caro Technologies http://www.icaro.com.br Work: +55 19 3731 8308 E-mail: [EMAIL PROTECTED] Fax: +55 19 3731 8304 A informao transmitida destina-se apenas pessoa ou entidade a quem foi endereada e pode conter informao confidencial, legalmente protegida e para conhecimento exclusivo do destinatrio. Se o leitor desta advertncia no for o seu destinatrio, fica ciente de que sua leitura, divulgao, distribuio ou cpia estritamente proibida. Caso a mensagem tenha sido recebida por engano, favor comunicar ao remetente e apagar o texto do computador. Este ambiente est sujeito a monitoramento. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. This environment is subject to monitoring. __20060125___This posting was submitted with HTML in it___
Diary fields with msg Character string exceeds maximum size allowed
** Hi all!! I've found a topic in the list about Diary fields full, but that doesn't help me :( I have an escalation that tries to push data into a diary field. Here goes escalation log and arerror.log: Escalation log: ESCL TID: 31 RPC ID: 036010 Queue: Escalation Client-RPC: 390603 USER: AR_ESCALATOR 1: Push Fields ESCL TID: 31 RPC ID: 036010 Queue: Escalation Client-RPC: 390603 USER: AR_ESCALATOR OSR:Msg (536871005) = momomomomo Cdigo: 32281005 Mensagem: momomomo ESCL TID: 31 RPC ID: 036010 Queue: Escalation Client-RPC: 390603 USER: AR_ESCALATOR Error while performing escalation action ArError LOG: Tue Jul 25 18:51:38 2006 390603 : Character string exceeds maximum size allowed : : 536871005 : (ARERR 559) It seems that my diary field is full... any ideas? TIA, Rafael Bertolini -- Rafael Bertolini System Analyst caro Technologies http://www.icaro.com.br Work: +55 19 3731 8308 E-mail: [EMAIL PROTECTED] Fax: +55 19 3731 8304 A informao transmitida destina-se apenas pessoa ou entidade a quem foi endereada e pode conter informao confidencial, legalmente protegida e para conhecimento exclusivo do destinatrio. Se o leitor desta advertncia no for o seu destinatrio, fica ciente de que sua leitura, divulgao, distribuio ou cpia estritamente proibida. Caso a mensagem tenha sido recebida por engano, favor comunicar ao remetente e apagar o texto do computador. Este ambiente est sujeito a monitoramento. The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any computer. This environment is subject to monitoring. __20060125___This posting was submitted with HTML in it___
