Hey,
I took your advice from BMCDN and deployed it as a war file.
I had to add some lines to the startup.sh in order for the servlet to
work, but at least it's up and running.
Thanks!
On Jul 9, 9:59 am, Axton [EMAIL PROTECTED] wrote:
Differences in your environment could cause the issue.
Hi,
Thanks for the tip.
I tried it out but editing out the code generates more errors.
It seems that this section is needed for other parts of the script.
Any other ideas?
What might be causing it? Can I add something to SuSE linux to get
this working?
Thanks
On Jul 8, 9:55 pm, Kurniadi
Hi,
I was wondering if anyone knows how I can get past this error when
installing remedy midtier 7.1 in SuSE 10.2.0.12
./mt_install: line 6109: release-notes-sles-10.2.0.12SUSE: command not
found
./mt_install: line 5974: =0: command not found
expr: syntax error
expr: syntax error
Operating
Hi,
I have a ticket open but haven't heard from BMC is a long time. Seems
to take them a while to 1. look at the bug 2. admit there is a bug. 3.
escalate it 4. get it fixed.
Anyway.
Does any one with SRM have this issue?
If you use en_US on the server but the clients have en_CA or en_AU, it
I noticed that even though my account has 'administrator' permissions,
I do not see all the forms that appadmin can.
Also for the AR System User Preference form, my admin account cannot
search on all records. It only brings up my user preference entry.
But appadmin can view all user preference
No it doesn't have a fixed license.
I change it to fixed and voila, I can see everything!
Thanks Peter!
On Apr 1, 1:42 pm, Lammey, Peter A. [EMAIL PROTECTED] wrote:
Does your account have a Fixed AR License?
AR system will not recognize the user as actually being an admin if the user
does
I have the same issue.
Remedy 7.0.1 patch 6.
I added the assignee column and tried referencing one of those
assignee fields (helpdesk) and it still doesn't show anything.
I look up the form that it should be looking at and look up the
records and it shows nothing in the assignee field on the
I'm wondering something.
Updated to ITSM patch 6.
Now in Overview Console... Unassigned view doesn't bring up anything.
I have 8 unassigned incidents, but when I check the Overview console,
the unassigned doesn't show up.
This happens to all support users.
Anyone else with this issue?
On Mar 5,
Ok so we got to the root of the problem causing the system to crash.
So I noticed that a handful of incidents were being updated with work
info.
This work info would push back to the related Service Request.
But there is a filter that would loop and keep looping endlessly until
the system
Our support team has found that the 2 error logs we sent showed that
both times the ar server crapped out at a filter/filter guide.
SRM:AOI:Process_IN_PushAppRequestInfo_05_EventParam_TableLoop (165)
I wonder if the other 2 people experiencing issue might be able to
check their filter logs to see
It took a bit of time to find out where this went hahaha.
Sorry but I'm changing the subject back.
On Feb 14, 12:02 pm, Sanford, Claire
[EMAIL PROTECTED] wrote:
Does anyone have any idea why some times when a Task ticket is updated,
the entry is copied to the CHG ticket's Work Log and other
Hi,
We are getting the same issues.
When looking at the event logs and witnessing it happen, it looks like
something is causing the Remedy service to restart by itself on our
system.
This causes a 2-4 minutes outage as the remedy service restarts
itself.
We are in the midst of troubleshooting.
Actually, over the weekend, we put SRM 2.1 into production and ITSM
module patch 6.
After this, our problems started with the AR ERR [90] Cannot establish
a network connection to the AR
System server: our server (0) : RPC: Miscellaneous tli error -
System error
(connection refused)
It started on
Did that.. and they are looking into it...
Why would the remedy service suddenly restart?
I can see it happen. I've seen it 3 times when people message me that
it is down.
I check the server and the remedy service restarts (not the sever but
just the service)
arerror.log doesn't seem to
Thanks for the tips.
We are running Windows 2003
Remedy 7.0.1 patch 4
ITSM 7.0.3 patch 6
SRM 2.1
SLM 7.0.3 patch 4
Database is on a remote server with windows 2003 and sql 2000.
I will check out the email part and hopefully see something that can
be fixed.
Harry
On Feb 13, 4:51 pm, john
I've had this happen to me..
It was resolved the same way... it just corrected itself after 5 mins.
On Jan 31, 12:43 pm, Harry Pugh [EMAIL PROTECTED]
wrote:
Thanks - I'll be on the lookout for that if it happens again.
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL
I was just wondering if anyone was having issues with notifications to
submitters on the request level?
I know you can turn it on from the SRD level and it is.
But I found that in the filter,
SRM:REQ:NotificationGenerator_899_PNP`!, Remedy Login ID is not
pushing to the NTE:SYS NT Process Control
We have had it configured in development (SRM 2.0) since last June.
But it has been buggy and therefore not put into production.
We upgraded to SRM 2.1 last month and found new bugs that keep us from
rolling it out.
I agree with Donald.
It's a good product with potential.
It's a real pain to
Hi,
Does anyone have SRM 2.1 installed in dev or prod?
We have it set up but have numerous issues. It is an upgrade from SRM
2.0.
First, it seems the email confirmation to end user on the SRM:Request
form doesn't send out.
Second, out of the box question/answer values don't push to the work
2nd issue. Answers not pushing to work order is a defect. It will be
fixed in SRM 2.1 patch 1. Or you can request the fix.
SW00283237
On Jan 17, 2:46 pm, [EMAIL PROTECTED] wrote:
Hi,
Does anyone have SRM 2.1 installed in dev or prod?
We have it set up but have numerous issues. It is an
The fix I received from BMC indeed show that locales are the problem.
I think there are 2 new filters and modification to the
SRM:AppInstanceBridge form.
I can send you the def fix if you want.
On Jan 17, 3:52 pm, Savant, [EMAIL PROTECTED] [EMAIL PROTECTED]
wrote:
We have SRM 2.1 installed in
21 matches
Mail list logo