Re: Issues with country specific characters on User tool 7.1 in Remedy upgrade from 7.1 to 9

[Mueller, Doug]

Vivek,

It sounds to me like you have a character set configuration confusion...

What was the character set of your old Oracle DB?
What is the character set of your new Oracle 12C DB?

If they don't match, how did you migrate the data between them to make sure the 
character sets were converted properly for all stored data?

What was the configuration setting of the AR System server for character set on 
the 7.1 instance?
What is the configuration setting of the AR System server for character set on 
the 9 instance?

The AR System DOES NOT have to match the DB character set.  However, the AR 
System character set is the key to what the client interaction is.


What you are seeing is typical if for example you have the character set 
configured for Latin1 but Swedish is actually a Latin2 character set language 
so the system doesn't understand the characters that are not part of the Latin1 
(basically English with a few extras) character set.

If the DB is configured with the Unicode Character Set, it supports all 
languages.  You can configure AR System 9 with the Unicode character set too.  
Then mixing and matching languages is just fine.

You can change the AR System character set and restart the server to have it 
take effect.  If the DB character set has to be changed, that is a major 
production as the data has to be reprocessed.

NOTE: If you had a Unicode DB but a Latin1 AR System, any records created 
during the time of mismatch may be incorrect in the DB and those you have to 
correct manually by fixing the text.  That is because the data would not have 
been encoded correctly as the character set mappings between AR System and the 
DB were occurring while you entered data that was not understood by the AR 
System character set.


Hopefully, not too confusing and hopefully a pointer to the direction to look.


One more note about the Windows User Tool client that could be the issue:

The Windows User Tool DOES NOT support Unicode.  You can configure a given 
instance with a character set.  It will show all entries in that character set 
correctly but languages in other character sets will not show correctly.  But, 
those same records would show correctly in another User Tool configured with 
the appropriate character set for the entries.  There is no solution for this.  
The Windows User Tool can only be in one character set.

The mid-tier on the other hand works in the Unicode character set so can mix 
and match languages without issue (assuming the underlying environments are 
Unicode otherwise it is restricted to the character set of the underlying 
server).


Lots of specific details, but again, hopefully, this helps point to what may be 
wrong in your environment.

Doug Mueller

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of VIVEK GARG
Sent: Sunday, April 24, 2016 7:48 PM
To: arslist@ARSLIST.ORG
Subject: Issues with country specific characters on User tool 7.1 in Remedy 
upgrade from 7.1 to 9

Hi,

While trying to upgrade Remedy 7.1 to Remedy 9, we have first installed oracle 
12c, then migrated entire production data from Remedy 7.1 on oracle 12c, then 
installed Remedy 8.1 and then we did a installation of remedy 9.

Things working fine for us but we are only stuck with one issue of country 
specific characters while accessing Remedy through user tool 7.1.
for e.g. When we save records in Swedish language, table records display those 
records in some strange characters.

Please let me know if anyone knows how to fix this.

Thanks,
Vivek

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers 
Are, and have been for 20 years"

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Issues with country specific characters on User tool 7.1 in Remedy upgrade from 7.1 to 9

[David Charters]

You have to use the Middle tier,  the user tool is a no longer supported



Sent via the Samsung Galaxy S® 6 edge, an AT&T 4G LTE smartphone


 Original message 
From: VIVEK GARG 
Date: 4/25/2016 12:48 AM (GMT-05:00)
To: arslist@ARSLIST.ORG
Subject: Issues with country specific characters on User tool 7.1 in Remedy 
upgrade from 7.1 to 9

Hi,

While trying to upgrade Remedy 7.1 to Remedy 9, we have first installed oracle 
12c, then migrated entire production data from Remedy 7.1 on oracle 12c, then 
installed Remedy 8.1 and then we did a installation of remedy 9.

Things working fine for us but we are only stuck with one issue of country 
specific characters while accessing Remedy through user tool 7.1.
for e.g. When we save records in Swedish language, table records display those 
records in some strange characters.

Please let me know if anyone knows how to fix this.

Thanks,
Vivek

___
UNSUBSCRIBE or access ARSlist Archives at 
www.arslist.org<http://www.arslist.org>
"Where the Answers Are, and have been for 20 years"

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Issues with country specific characters on User tool 7.1 in Remedy upgrade from 7.1 to 9

[VIVEK GARG]

Hi,

While trying to upgrade Remedy 7.1 to Remedy 9, we have first installed oracle 
12c, then migrated entire production data from Remedy 7.1 on oracle 12c, then 
installed Remedy 8.1 and then we did a installation of remedy 9.

Things working fine for us but we are only stuck with one issue of country 
specific characters while accessing Remedy through user tool 7.1.
for e.g. When we save records in Swedish language, table records display those 
records in some strange characters.

Please let me know if anyone knows how to fix this.

Thanks,
Vivek

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: New Remedy Upgrade Project!! :)

[Tauf Chowdhury]

You guys didn't even get to the rate yet. I'm sure it's like $60/hr all 
inclusive lol 😂

Sent from my iPhone

> On Dec 23, 2015, at 5:25 PM, remedy...@gmail.com wrote:
> 
> **
> Then 3 more...
> Then... 3 more...
> Then  3 more
> 
> Sent from my iPhone
> 
>> On Dec 23, 2015, at 3:45 PM, Sanford, Claire 
>>  wrote:
>> 
>> **
>> BMC probably told them it would only take 3 weeks! 
>>  
>> From: Action Request System discussion list(ARSList) 
>> [mailto:arslist@ARSLIST.ORG] On Behalf Of Rick Cook
>> Sent: Wednesday, December 23, 2015 11:09 AM
>> To: arslist@ARSLIST.ORG
>> Subject: Re: New Remedy Upgrade Project!! :)
>>  
>> **
>> Yeah, I was thinking the same thing.  Rick's #1 rule of consulting is that 
>> the customer can set the scope or the time line.  Not both. 
>> 
>> Rick
>> 
>> On Dec 23, 2015 9:05 AM, "Roger Justice"  wrote:
>> **
>> Who else on the list consider 16 days to do a 7.1 to 8.1 upgrade to short 
>> and as you can see from PIKSSO custom authentication the customer has ITSM.
>>  
>>  
>> -Original Message-
>> From: Anna Peters 
>> To: arslist 
>> Sent: Wed, Dec 23, 2015 11:56 am
>> Subject: New Remedy Upgrade Project!! :)
>> 
>> **
>> Good Morning, Arslist!
>> New project available IMMEDIATELY– please send resume and rate requirements 
>> if you are interested.
>>  
>> Engagement Overview
>> Duration: 4 weeks (4-day work weeks are ok)
>> Location: Fort Meade, MD
>> **TS/SCI is required**
>>  
>> ARS 7.1 – ARS 8.1 Upgrade1
>> ·Back-up current database
>> ·Export forms
>> ·Run upgrade scripts
>> ·Test
>> ·Perform any necessary remediation
>>  
>> Install & Configure email
>>  
>> LDAP for Authentication Configuration Implementation
>> ·Configure LDAP authentication using the BMC supplied AR External 
>> Authentication (AREA) LDAP plug-in.
>>  
>> LDAP for People Data Population Implementation
>> ·Setup and configure LDAP People Data Population using the BMC 
>> supplied AR System Database Connectivity (ARDBC) LDAP plug-in.
>>  
>> Install and Configure PKISSO for Remedy ITSM/MidTier
>> ·Assist customer with installation and configuration of the Remedy 
>> AREA plugin and the PKISSO custom authenticator for MidTier.
>>  
>> Documentation
>> ·Document System
>>  
>> Thank you and Happy Holidays!!
>>  
>> Anna Peters
>> Recruiter
>> 
>>  
>> Comcentric Inc.
>> 10463 Park Meadows Drive #208
>> Lone Tree, CO 80124
>> 
>>  
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
> _ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: New Remedy Upgrade Project!! :)

[remedyboy]

Is it Friday  🤓

Sent from my iPhone

> On Dec 23, 2015, at 12:08 PM, Rick Cook  wrote:
> 
> **
> Yeah, I was thinking the same thing.  Rick's #1 rule of consulting is that 
> the customer can set the scope or the time line.  Not both. 
> 
> Rick
> 
>> On Dec 23, 2015 9:05 AM, "Roger Justice"  wrote:
>> **
>> Who else on the list consider 16 days to do a 7.1 to 8.1 upgrade to short 
>> and as you can see from PIKSSO custom authentication the customer has ITSM.
>>  
>>  
>> -Original Message-
>> From: Anna Peters 
>> To: arslist 
>> Sent: Wed, Dec 23, 2015 11:56 am
>> Subject: New Remedy Upgrade Project!! :)
>> 
>> **
>> Good Morning, Arslist!
>> New project available IMMEDIATELY– please send resume and rate requirements 
>> if you are interested.
>>  
>> Engagement Overview
>> Duration: 4 weeks (4-day work weeks are ok)
>> Location: Fort Meade, MD
>> **TS/SCI is required**
>>  
>> ARS 7.1 – ARS 8.1 Upgrade1
>> ·Back-up current database
>> ·Export forms
>> ·Run upgrade scripts
>> ·Test
>> ·Perform any necessary remediation
>>  
>> Install & Configure email
>>  
>> LDAP for Authentication Configuration Implementation
>> ·Configure LDAP authentication using the BMC supplied AR External 
>> Authentication (AREA) LDAP plug-in.
>>  
>> LDAP for People Data Population Implementation
>> ·Setup and configure LDAP People Data Population using the BMC 
>> supplied AR System Database Connectivity (ARDBC) LDAP plug-in.
>>  
>> Install and Configure PKISSO for Remedy ITSM/MidTier
>> ·Assist customer with installation and configuration of the Remedy 
>> AREA plugin and the PKISSO custom authenticator for MidTier.
>>  
>> Documentation
>> ·Document System
>>  
>> Thank you and Happy Holidays!!
>>  
>> Anna Peters
>> Recruiter
>> 
>>  
>> Comcentric Inc.
>> 10463 Park Meadows Drive #208
>> Lone Tree, CO 80124
>> 
>>  
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
> _ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: New Remedy Upgrade Project!! :)

[remedyboy]

Then 3 more...
Then... 3 more...
Then  3 more

Sent from my iPhone

> On Dec 23, 2015, at 3:45 PM, Sanford, Claire 
>  wrote:
> 
> **
> BMC probably told them it would only take 3 weeks! 
>  
> From: Action Request System discussion list(ARSList) 
> [mailto:arslist@ARSLIST.ORG] On Behalf Of Rick Cook
> Sent: Wednesday, December 23, 2015 11:09 AM
> To: arslist@ARSLIST.ORG
> Subject: Re: New Remedy Upgrade Project!! :)
>  
> **
> Yeah, I was thinking the same thing.  Rick's #1 rule of consulting is that 
> the customer can set the scope or the time line.  Not both. 
> 
> Rick
> 
> On Dec 23, 2015 9:05 AM, "Roger Justice"  wrote:
> **
> Who else on the list consider 16 days to do a 7.1 to 8.1 upgrade to short and 
> as you can see from PIKSSO custom authentication the customer has ITSM.
>  
>  
> -Original Message-----
> From: Anna Peters 
> To: arslist 
> Sent: Wed, Dec 23, 2015 11:56 am
> Subject: New Remedy Upgrade Project!! :)
> 
> **
> Good Morning, Arslist!
> New project available IMMEDIATELY– please send resume and rate requirements 
> if you are interested.
>  
> Engagement Overview
> Duration: 4 weeks (4-day work weeks are ok)
> Location: Fort Meade, MD
> **TS/SCI is required**
>  
> ARS 7.1 – ARS 8.1 Upgrade1
> ·Back-up current database
> ·Export forms
> ·Run upgrade scripts
> ·Test
> ·Perform any necessary remediation
>  
> Install & Configure email
>  
> LDAP for Authentication Configuration Implementation
> ·Configure LDAP authentication using the BMC supplied AR External 
> Authentication (AREA) LDAP plug-in.
>  
> LDAP for People Data Population Implementation
> ·Setup and configure LDAP People Data Population using the BMC 
> supplied AR System Database Connectivity (ARDBC) LDAP plug-in.
>  
> Install and Configure PKISSO for Remedy ITSM/MidTier
> ·Assist customer with installation and configuration of the Remedy 
> AREA plugin and the PKISSO custom authenticator for MidTier.
>  
> Documentation
> ·Document System
>  
> Thank you and Happy Holidays!!
>  
> Anna Peters
> Recruiter
> 
>  
> Comcentric Inc.
> 10463 Park Meadows Drive #208
> Lone Tree, CO 80124
> 
>  
> _ARSlist: "Where the Answers Are" and have been for 20 years_
> _ARSlist: "Where the Answers Are" and have been for 20 years_
> _ARSlist: "Where the Answers Are" and have been for 20 years_
> _ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: New Remedy Upgrade Project!! :)

[Sanford, Claire]

BMC probably told them it would only take 3 weeks!

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Rick Cook
Sent: Wednesday, December 23, 2015 11:09 AM
To: arslist@ARSLIST.ORG
Subject: Re: New Remedy Upgrade Project!! :)

**

Yeah, I was thinking the same thing.  Rick's #1 rule of consulting is that the 
customer can set the scope or the time line.  Not both.

Rick
On Dec 23, 2015 9:05 AM, "Roger Justice" 
mailto:rjust2...@aol.com>> wrote:
**
Who else on the list consider 16 days to do a 7.1 to 8.1 upgrade to short and 
as you can see from PIKSSO custom authentication the customer has ITSM.


-Original Message-
From: Anna Peters 
mailto:anna.pet...@comcentric.com>>
To: arslist mailto:arslist@ARSLIST.ORG>>
Sent: Wed, Dec 23, 2015 11:56 am
Subject: New Remedy Upgrade Project!! :)
**
Good Morning, Arslist!
New project available IMMEDIATELY– please send resume and rate requirements if 
you are interested.

Engagement Overview
Duration: 4 weeks (4-day work weeks are ok)
Location: Fort Meade, MD
**TS/SCI is required**

ARS 7.1 – ARS 8.1 Upgrade1
•Back-up current database
•Export forms
•Run upgrade scripts
•Test
•Perform any necessary remediation

Install & Configure email

LDAP for Authentication Configuration Implementation
•Configure LDAP authentication using the BMC supplied AR External 
Authentication (AREA) LDAP plug-in.

LDAP for People Data Population Implementation
•Setup and configure LDAP People Data Population using the BMC supplied 
AR System Database Connectivity (ARDBC) LDAP plug-in.

Install and Configure PKISSO for Remedy ITSM/MidTier
•Assist customer with installation and configuration of the Remedy AREA 
plugin and the PKISSO custom authenticator for MidTier.

Documentation
•Document System

Thank you and Happy Holidays!!

Anna Peters
Recruiter
[http://www.beccconference.org/wp-content/uploads/2012/04/groups.png]<https://urldefense.proofpoint.com/v2/url?u=https-3A__www.linkedin.com_profile_view-3Fid-3D6916941-26authType-3DNAME-5FSEARCH-26authToken-3DE1Bl-26locale-3Den-5FUS-26trk-3Dtyah-26trkInfo-3DclickedVertical-3Amynetwork-2Cidx-3A1-2D2-2D2-2CtarId-3A1430769203865-2Ctas-3Aanna-2520pete&d=CwMFaQ&c=cBOA5YEoZuz9KdLvh38YxdrPtfJt83ckXekfBgq5xB0&r=TjDOQeE84FB3IkKBOKJ7-reBz8qKDLQv4sMWw_GFxq4ypeuVm4ZMlj00hGeKuFbo&m=19AKGNrg3di0EXzOtIIc2OhEpII3vrnyu5YX5LeKTdM&s=gkr4LUn73KREVfSmVD8u3EQDSl07nSdaYYmgNUJp4EM&e=>

Comcentric Inc.
10463 Park Meadows Drive #208
Lone Tree, CO 80124
[cid:image001.png@01CFF1DD.30084AF0]

_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: New Remedy Upgrade Project!! :)

[Rick Cook]

Yeah, I was thinking the same thing.  Rick's #1 rule of consulting is that
the customer can set the scope or the time line.  Not both.

Rick
On Dec 23, 2015 9:05 AM, "Roger Justice"  wrote:

> **
> Who else on the list consider 16 days to do a 7.1 to 8.1 upgrade to short
> and as you can see from PIKSSO custom authentication the customer has ITSM.
>
>
> -Original Message-
> From: Anna Peters 
> To: arslist 
> Sent: Wed, Dec 23, 2015 11:56 am
> Subject: New Remedy Upgrade Project!! :)
>
> **
> Good Morning, Arslist!
> New project available IMMEDIATELY– please send resume and rate
> requirements if you are interested.
>
> *Engagement Overview*
> *Duration: 4 weeks (4-day work weeks are ok)*
> *Location: Fort Meade, MD*
> ***TS/SCI is required***
>
> *ARS 7.1 – ARS 8.1 Upgrade1*
> ·Back-up current database
> ·Export forms
> ·Run upgrade scripts
> ·Test
> ·Perform any necessary remediation
>
> *Install & Configure email*
>
> *LDAP for Authentication Configuration Implementation*
> ·Configure LDAP authentication using the BMC supplied AR External
> Authentication (AREA) LDAP plug-in.
>
> *LDAP for People Data Population Implementation*
> ·Setup and configure LDAP People Data Population using the BMC
> supplied AR System Database Connectivity (ARDBC) LDAP plug-in.
>
> *Install and Configure PKISSO for Remedy ITSM/MidTier*
> ·Assist customer with installation and configuration of the
> Remedy AREA plugin and the PKISSO custom authenticator for MidTier.
>
> *Documentation*
> ·Document System
>
> Thank you and Happy Holidays!!
>
> *Anna Peters *
> Recruiter
> [image:
> http://www.beccconference.org/wp-content/uploads/2012/04/groups.png]
> <https://www.linkedin.com/profile/view?id=6916941&authType=NAME_SEARCH&authToken=E1Bl&locale=en_US&trk=tyah&trkInfo=clickedVertical:mynetwork,idx:1-2-2,tarId:1430769203865,tas:anna%20pete>
>
> Comcentric Inc.
> 10463 Park Meadows Drive #208
> Lone Tree, CO 80124
> [image: cid:image001.png@01CFF1DD.30084AF0]
>
> _ARSlist: "Where the Answers Are" and have been for 20 years_
> _ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: New Remedy Upgrade Project!! :)

[William Rentfrow]

If you're including the steps to create the overlays from the pre-overlay days 
it's WAY too short for even one environment.

Also, the number of environments here is not discussed.  Dev and Prod?  
Dev/Test/Prod?  Dev/Test/CAT/Prod?

William Rentfrow
wrentf...@stratacominc.com
Office: 715-204-3061 or 701-232-5697x25
Cell: 715-498-5056

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Roger Justice
Sent: Wednesday, December 23, 2015 11:02 AM
To: arslist@ARSLIST.ORG
Subject: Re: New Remedy Upgrade Project!! :)

**
Who else on the list consider 16 days to do a 7.1 to 8.1 upgrade to short and 
as you can see from PIKSSO custom authentication the customer has ITSM.


-Original Message-
From: Anna Peters 
mailto:anna.pet...@comcentric.com>>
To: arslist mailto:arslist@ARSLIST.ORG>>
Sent: Wed, Dec 23, 2015 11:56 am
Subject: New Remedy Upgrade Project!! :)
**
Good Morning, Arslist!
New project available IMMEDIATELY– please send resume and rate requirements if 
you are interested.

Engagement Overview
Duration: 4 weeks (4-day work weeks are ok)
Location: Fort Meade, MD
**TS/SCI is required**

ARS 7.1 – ARS 8.1 Upgrade1

•Back-up current database

•Export forms

•Run upgrade scripts

•Test

•Perform any necessary remediation

Install & Configure email

LDAP for Authentication Configuration Implementation

•Configure LDAP authentication using the BMC supplied AR External 
Authentication (AREA) LDAP plug-in.

LDAP for People Data Population Implementation

•Setup and configure LDAP People Data Population using the BMC supplied 
AR System Database Connectivity (ARDBC) LDAP plug-in.

Install and Configure PKISSO for Remedy ITSM/MidTier

•Assist customer with installation and configuration of the Remedy AREA 
plugin and the PKISSO custom authenticator for MidTier.

Documentation
•Document System

Thank you and Happy Holidays!!

Anna Peters
Recruiter
[http://www.beccconference.org/wp-content/uploads/2012/04/groups.png]<https://www.linkedin.com/profile/view?id=6916941&authType=NAME_SEARCH&authToken=E1Bl&locale=en_US&trk=tyah&trkInfo=clickedVertical:mynetwork,idx:1-2-2,tarId:1430769203865,tas:anna%20pete>

Comcentric Inc.
10463 Park Meadows Drive #208
Lone Tree, CO 80124
[cid:image001.png@01CFF1DD.30084AF0]

_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_

No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2016.0.7294 / Virus Database: 4489/11215 - Release Date: 12/19/15

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: New Remedy Upgrade Project!! :)

[Richter, Howard (CEI-Atlanta)]

Good luck to anyone who tries that. Maybe the 7.1 system is out of box and they 
are not moving any data to the 8.1 system.



Howard Richter, Senior System Administrator


From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Roger Justice
Sent: Wednesday, December 23, 2015 12:02 PM
To: arslist@ARSLIST.ORG
Subject: Re: [arslist] New Remedy Upgrade Project!! :)

**
Who else on the list consider 16 days to do a 7.1 to 8.1 upgrade to short and 
as you can see from PIKSSO custom authentication the customer has ITSM.


-Original Message-
From: Anna Peters 
mailto:anna.pet...@comcentric.com>>
To: arslist mailto:arslist@ARSLIST.ORG>>
Sent: Wed, Dec 23, 2015 11:56 am
Subject: New Remedy Upgrade Project!! :)
**
Good Morning, Arslist!
New project available IMMEDIATELY– please send resume and rate requirements if 
you are interested.

Engagement Overview
Duration: 4 weeks (4-day work weeks are ok)
Location: Fort Meade, MD
**TS/SCI is required**

ARS 7.1 – ARS 8.1 Upgrade1

•Back-up current database

•Export forms

•Run upgrade scripts

•Test

•Perform any necessary remediation

Install & Configure email

LDAP for Authentication Configuration Implementation

•Configure LDAP authentication using the BMC supplied AR External 
Authentication (AREA) LDAP plug-in.

LDAP for People Data Population Implementation

•Setup and configure LDAP People Data Population using the BMC supplied 
AR System Database Connectivity (ARDBC) LDAP plug-in.

Install and Configure PKISSO for Remedy ITSM/MidTier

•Assist customer with installation and configuration of the Remedy AREA 
plugin and the PKISSO custom authenticator for MidTier.

Documentation
•Document System

Thank you and Happy Holidays!!

Anna Peters
Recruiter
[http://www.beccconference.org/wp-content/uploads/2012/04/groups.png]<https://www.linkedin.com/profile/view?id=6916941&authType=NAME_SEARCH&authToken=E1Bl&locale=en_US&trk=tyah&trkInfo=clickedVertical:mynetwork,idx:1-2-2,tarId:1430769203865,tas:anna%20pete>

Comcentric Inc.
10463 Park Meadows Drive #208
Lone Tree, CO 80124
[cid:image001.png@01CFF1DD.30084AF0]

_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_

Click 
here<https://www.mailcontrol.com/sr/nIDrvCiP!nbGX2PQPOmvUihCLhWP7Wj9WAYnnrHJ67du+gvcROqg4IgpBziJkMmDsBsHXPldfWEhei1KLnaPDA==>
 to report this email as spam.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: New Remedy Upgrade Project!! :)

[Roger Justice]

Who else on the list consider 16 days to do a 7.1 to 8.1 upgrade to short and 
as you can see from PIKSSO custom authentication the customer has ITSM.
 
 
-Original Message-
From: Anna Peters 
To: arslist 
Sent: Wed, Dec 23, 2015 11:56 am
Subject: New Remedy Upgrade Project!! :)


**
Good Morning, Arslist! 
New project available IMMEDIATELY– please send resume and rate requirements if 
you are interested.
 
Engagement Overview
Duration: 4 weeks (4-day work weeks are ok)
Location: Fort Meade, MD
**TS/SCI is required**
 
ARS 7.1 – ARS 8.1 Upgrade1
·   Back-up current database
·   Export forms
·   Run upgrade scripts
·   Test
·   Perform any necessary remediation
 
Install & Configure email
 
LDAP for Authentication Configuration Implementation
·   Configure LDAP authentication using the BMC supplied AR External 
Authentication (AREA) LDAP plug-in.
 
LDAP for People Data Population Implementation
·   Setup and configure LDAP People Data Population using the BMC supplied 
AR System Database Connectivity (ARDBC) LDAP plug-in.
 
Install and Configure PKISSO for Remedy ITSM/MidTier
·   Assist customer with installation and configuration of the Remedy AREA 
plugin and the PKISSO custom authenticator for MidTier.
 
Documentation
·   Document System
 
Thank you and Happy Holidays!!
 
Anna Peters 
Recruiter

 
Comcentric Inc.
10463 Park Meadows Drive #208
Lone Tree, CO 80124

 
_ARSlist: "Where the Answers Are" and have been for 20 years_


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

New Remedy Upgrade Project!! :)

[Anna Peters]

Good Morning, Arslist!
New project available IMMEDIATELY- please send resume and rate requirements if 
you are interested.

Engagement Overview
Duration: 4 weeks (4-day work weeks are ok)
Location: Fort Meade, MD
**TS/SCI is required**

ARS 7.1 - ARS 8.1 Upgrade1

*Back-up current database

*Export forms

*Run upgrade scripts

*Test

*Perform any necessary remediation

Install & Configure email

LDAP for Authentication Configuration Implementation

*Configure LDAP authentication using the BMC supplied AR External 
Authentication (AREA) LDAP plug-in.

LDAP for People Data Population Implementation

*Setup and configure LDAP People Data Population using the BMC supplied 
AR System Database Connectivity (ARDBC) LDAP plug-in.

Install and Configure PKISSO for Remedy ITSM/MidTier

*Assist customer with installation and configuration of the Remedy AREA 
plugin and the PKISSO custom authenticator for MidTier.

Documentation

*Document System

Thank you and Happy Holidays!!

Anna Peters
Recruiter
[http://www.beccconference.org/wp-content/uploads/2012/04/groups.png]

Comcentric Inc.
10463 Park Meadows Drive #208
Lone Tree, CO 80124
[cid:image001.png@01CFF1DD.30084AF0]


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade

[James Smith]

Hi William/Roger,

Please correct me in below steps With server group upgrade.

1) Stop all servers in Server Group
2) Remove admin server from load balancer and make it standalone ( Remove from 
server group and make changes in ar.conf file)
3) Start the admin server and perform installation with Upgrade as an option ( 
rest of servers are all stopped)
4) Add the admin sever back to load balancer and restart the server. ( Rest of 
all servers except admin server are all stopped)
5) Perform installation on secondary non admin server with Server Group option 
( Secondary server is stopped and is in server group. Only Admin server is 
running in server group.No changes are required to be done in ar.conf file for 
secondary server)
6) Perform step 5 for rest of the non admin servers ( Only admin server should 
be up and running)
7) After completing installation on all servers, restart all severs.

Please correct me if anything is wrong.

James

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade

[James Smith]

Hi,

Thanks for your response. I am trying to upgrade from 7.6.04 to 8.1 no patch. I 
tried 2 times on production server but it failed every time. On Dev server it 
was successful as it was only one server.

On server group, I installed ARS on Admin server but on secondary server it is 
failing. 

Am I missing anything? Can you share any installation document in server group. 
I have plans to install it again this weekend. I will loose the project if I 
fail.

Please help me.

James

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade

[James Smith]

You have shared the information which I was not aware. Thanks a billion for it 
but still have couple of questions.

If AR Server service is down then how will the installer verifies the Remedy 
user credentials used during installation? Installation may fail here.
Do I have to stop the service from Services.msc console or kill any process?
I could not find the information of installing ARS on secondary server, can you 
share any documents or URL ?

Thank you for inputs.

James

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade

[William Rentfrow]

I am not talking about moving binaries.  I am talking about how the installer 
works on secondary installs.

When you install the first server in a server group the arserverd process 
should be up and running.  The installer does the file system upgrade and the 
db changes.

On the second (and all others) server the arserverd process should be DOWN when 
you run the installer.  The installer then only lays down the binaries and does 
not try to make any other changes to the database.

There are of course instances in the various installs where it still does 
connect to the database via the ar server and check stuff.

And, on top of that - there's a whole bunch of configuration you need to do to 
the servers prior to the upgrade.  You have to take them out of the server 
group, give them back their "real" names", etc.  

The upgrade manual covers all of this in excruciating detail (bring coffee).

William Rentfrow
wrentf...@stratacominc.com
Office: 715-204-3061 or 701-232-5697x25
Cell: 715-498-5056


-Original Message-
From: James Smith [mailto:bmcremedyarslis...@gmail.com] 
Sent: Saturday, April 25, 2015 11:37 PM
To: arslist@ARSLIST.ORG; William Rentfrow
Cc: James Smith
Subject: Re: Remedy Upgrade

Hello Willia ,

Moving binaries on servers is not an option for me since I am installing 8.1. I 
have read the docs page which says installation has to be done on all servers.

https://docs.bmc.com/docs/display/public/ars81/Upgrading+server+groups#Upgradingservergroups-Toperformanin-placeupgrade

James


-
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2014.0.4800 / Virus Database: 4311/9524 - Release Date: 04/12/15
Internal Virus Database is out of date.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade

[James Smith]

Hello Willia ,

Moving binaries on servers is not an option for me since I am installing 8.1. I 
have read the docs page which says installation has to be done on all servers.

https://docs.bmc.com/docs/display/public/ars81/Upgrading+server+groups#Upgradingservergroups-Toperformanin-placeupgrade

James

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade

[William Rentfrow]

Not sure why I am replying to this on a Saturday night, but

James - you really need to get a better understanding of the upgrade process 
for a server group.  The first server is the only one where you want the 
application servers up.  The second/third/etc servers need to be upgraded in a 
very specific way which only lays the binaries down on those servers - it 
shouldn't be touching the database.  Ergo, the database should be backed up 
prior to the first, and the file system on all servers prior to each upgrade.

Again, the exact process depends on version, but server group upgrades are 
tricky if you have never done one.  Heck, they are tricky when you have done 
them.

I'd suggest you read the server group docs, make an outline of an upgrade plan, 
and post here for critique.  And search the list - many of us have posted about 
that exact topic.

William Rentfrow
wrentf...@stratacominc.com
Office: 715-204-3061 or 701-232-5697x25
Cell: 715-498-5056

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Roger Justice
Sent: Saturday, April 25, 2015 2:33 PM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Upgrade

**
It would help if you include version from and version to.


-Original Message-
From: James Smith 
To: arslist 
Sent: Sat, Apr 25, 2015 3:17 pm
Subject: Remedy Upgrade

Hi List,



How all are doing pals? Imagining all are fine with family and in

party mood of weekend.



Let me come to my concern so that you can help me. I

have 3 servers in a server group and I am planning to upgrade it. Wondering what

would be the blackout plan? If I complete the upgrade on 1 server successful and

next server fails then do I need to restores all 3 servers or only next server?

What about database?



After completing upgrade on 1 server, do I need to take

db backup again before going to next server? If I do so then it may take lot of

time if DB size is large or if I have more servers in my environment ( let say

10 - I have seen it).



How you guys are doing upgrade blackout plan in server

group environment? I have given only one day change window for production server

upgrade.



Please share your valuable

opinions.



James.



___

UNSUBSCRIBE

or access ARSlist Archives at www.arslist.org<http://www.arslist.org>

"Where the Answers Are, and have

been for 20 years"
_ARSlist: "Where the Answers Are" and have been for 20 years_

No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2014.0.4800 / Virus Database: 4311/9524 - Release Date: 04/12/15
Internal Virus Database is out of date.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade

[Roger Justice]

It would help if you include version from and version to.
 
 
-Original Message-
From: James Smith 
To: arslist 
Sent: Sat, Apr 25, 2015 3:17 pm
Subject: Remedy Upgrade


Hi List,

How all are doing pals? Imagining all are fine with family and in
party mood of weekend.

Let me come to my concern so that you can help me. I
have 3 servers in a server group and I am planning to upgrade it. Wondering what
would be the blackout plan? If I complete the upgrade on 1 server successful and
next server fails then do I need to restores all 3 servers or only next server?
What about database?

After completing upgrade on 1 server, do I need to take 
db backup again before going to next server? If I do so then it may take lot of
time if DB size is large or if I have more servers in my environment ( let say
10 - I have seen it).

How you guys are doing upgrade blackout plan in server
group environment? I have given only one day change window for production server
upgrade.

Please share your valuable
opinions.

James.

___
UNSUBSCRIBE
or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have
been for 20 years"

 

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Remedy Upgrade

[James Smith]

Hi List,

How all are doing pals? Imagining all are fine with family and in party mood of 
weekend.

Let me come to my concern so that you can help me. I have 3 servers in a server 
group and I am planning to upgrade it. Wondering what would be the blackout 
plan? If I complete the upgrade on 1 server successful and next server fails 
then do I need to restores all 3 servers or only next server? What about 
database?

After completing upgrade on 1 server, do I need to take  db backup again before 
going to next server? If I do so then it may take lot of time if DB size is 
large or if I have more servers in my environment ( let say 10 - I have seen 
it).

How you guys are doing upgrade blackout plan in server group environment? I 
have given only one day change window for production server upgrade.

Please share your valuable opinions.

James.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade - Suggestions required.

[BradRemedy]

Hi Karthick

We are nearing the completion of our ITSM upgrade and plan to go live in
the next month after final testing and data migration has been completed.
Our upgrade was from ITSM 7.5 to the latest version. We had to make the
same decision you are facing now and went with the option to do a clean
ITSM 8.1 install with SRM 8.1 (latest patches / SP) and then redevelop
any customization we had done. It was a bit of work however we took
the opportunity to review our customization and see if they were
not accommodated for in the new ITSM version or if we could do the
customization in a better way. So basically we did a code review.

I didn't want to do a in place upgrade as I didn't want to bring across any
"buggy" customization's or any other bugs to the new version.

If you can, do a clean install and then review your customization's. Then
as the other guys said, use DDM or rrrchive to migrate your data across.

Good Luck.

Cheers
Brad

On Mon, Feb 23, 2015 at 9:38 AM, Rod Harris  wrote:

> **
> Hi Karthick,
>
> I agree with Rick in advocating standing up a new environment and moving
> your data to it. There are many advantages to doing thing this way and I
> probably don't have to list them all here. Stand up a new environment, on a
> new database,  install ARS, ITSM to each server in the group, get it
> patched to the right versions, apply the customization you need to preserve
> via overlays (some may be covered in the new version), then use rrr|Chive
> or similar to move the data to the new environment.Perhaps use this as an
> opportunity to archive old unnecessary data at the same time (eg old
> notification logs). Using this approach you will be able to test your new
> system in full prior to the big cutover weekend. On a big system it can
> take time to synchronize the data but rrr|Chive's synctotarget feature can
> be used to minimize any duplication of effort and this can all be done up
> front.
>
> There are (at least) a couple of gotchas to be aware of if you do stand up
> a new server and move your data to it.
>
> 1. Some forms have had unique indexes added to the "Instance ID" field.
> They probably should have been there all along but if you have somehow
> allowed duplicate instance IDs to creep in (via "copy to new") then you
> will need to clear this field and generate new IDs for the dupes when
> moving data to the new system.
>
> 2. Doing an in-place upgrade to a system populated with data can take a
> very long time and can timeout before completion. I presume the upgrades
> can sometime do data conversions and this is the reason. I think in one
> instance it tries to push fields to every row in a table in one transaction
> and that kept repeating, timing out or reaching the filter limit before
> rolling back. Best advice is to try and avoid doing an in-place upgrade to
> systems with lots of data. Clear the data out of impacted tables, do the
> upgrade and then replace the data. That's why it is best to do the patch
> upgrades prior to moving data to new system.
>
> 3. Some of the same out of the box foundation data has different request
> IDs between versions of ITSM. If you try and merge the foundation data
> between 2 different releases of ITSM you can end up with duplicate
> permission groups or similar. identify the real key and delete the dupes on
> migration.
>
> I'm sure there are some other gotchas and as Rick says when you start
> combining changes to the data as you migrate things can get a little messy
> but I think you may be surprised how easy it actually is to move the data
> from one version of remedy to a new one.
>
> Rod Harris
>
> PS BMC advocates using DDM Delta Data Migrator which does a similar job to
> rrr|Chive
>
>
> On Saturday, 21 February 2015, Rick Westbrock 
> wrote:
>
>> **
>>
>> Good point, it should be easier to get AR working properly then ITSM
>> before worrying about getting your old data into the mix. I have the fun of
>> building a new product catalog as part of the upgrade as well as changing
>> from multi-tenant to single-tenant so it’s going to be a fun ride over here.
>>
>>
>>
>> -Rick
>>
>>
>>
>> *From:* Action Request System discussion list(ARSList) [mailto:
>> arslist@ARSLIST.ORG] *On Behalf Of *Rick Cook
>> *Sent:* Friday, February 20, 2015 8:36 AM
>> *To:* arslist@ARSLIST.ORG
>> *Subject:* Re: Remedy Upgrade - Suggestions required.
>>
>>
>>
>> **
>>
>> Yup.  We are doing the same upgrade, and are doing it via the build and
>> migrate plan, not an upgrade in place.
>>
>>
>>
>> There are some bugs in the 8.1.02 installers, too, as I 

Re: Remedy Upgrade - Suggestions required.

[Rod Harris]

Hi Karthick,

I agree with Rick in advocating standing up a new environment and moving
your data to it. There are many advantages to doing thing this way and I
probably don't have to list them all here. Stand up a new environment, on a
new database,  install ARS, ITSM to each server in the group, get it
patched to the right versions, apply the customization you need to preserve
via overlays (some may be covered in the new version), then use rrr|Chive
or similar to move the data to the new environment.Perhaps use this as an
opportunity to archive old unnecessary data at the same time (eg old
notification logs). Using this approach you will be able to test your new
system in full prior to the big cutover weekend. On a big system it can
take time to synchronize the data but rrr|Chive's synctotarget feature can
be used to minimize any duplication of effort and this can all be done up
front.

There are (at least) a couple of gotchas to be aware of if you do stand up
a new server and move your data to it.

1. Some forms have had unique indexes added to the "Instance ID" field.
They probably should have been there all along but if you have somehow
allowed duplicate instance IDs to creep in (via "copy to new") then you
will need to clear this field and generate new IDs for the dupes when
moving data to the new system.

2. Doing an in-place upgrade to a system populated with data can take a
very long time and can timeout before completion. I presume the upgrades
can sometime do data conversions and this is the reason. I think in one
instance it tries to push fields to every row in a table in one transaction
and that kept repeating, timing out or reaching the filter limit before
rolling back. Best advice is to try and avoid doing an in-place upgrade to
systems with lots of data. Clear the data out of impacted tables, do the
upgrade and then replace the data. That's why it is best to do the patch
upgrades prior to moving data to new system.

3. Some of the same out of the box foundation data has different request
IDs between versions of ITSM. If you try and merge the foundation data
between 2 different releases of ITSM you can end up with duplicate
permission groups or similar. identify the real key and delete the dupes on
migration.

I'm sure there are some other gotchas and as Rick says when you start
combining changes to the data as you migrate things can get a little messy
but I think you may be surprised how easy it actually is to move the data
from one version of remedy to a new one.

Rod Harris

PS BMC advocates using DDM Delta Data Migrator which does a similar job to
rrr|Chive

On Saturday, 21 February 2015, Rick Westbrock 
wrote:

> **
>
> Good point, it should be easier to get AR working properly then ITSM
> before worrying about getting your old data into the mix. I have the fun of
> building a new product catalog as part of the upgrade as well as changing
> from multi-tenant to single-tenant so it’s going to be a fun ride over here.
>
>
>
> -Rick
>
>
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arslist@ARSLIST.ORG] *On Behalf Of *Rick Cook
> *Sent:* Friday, February 20, 2015 8:36 AM
> *To:* arslist@ARSLIST.ORG
> *Subject:* Re: Remedy Upgrade - Suggestions required.
>
>
>
> **
>
> Yup.  We are doing the same upgrade, and are doing it via the build and
> migrate plan, not an upgrade in place.
>
>
>
> There are some bugs in the 8.1.02 installers, too, as I am finding.  All
> the more reason to do it in a simpler environment.
>
>
>   Rick Cook
>
>
>
> On Fri, Feb 20, 2015 at 8:29 AM, Rick Westbrock 
> wrote:
>
> **
>
> Karthick-
>
>
>
> I know that others share my opinion that when you are jumping ahead
> multiple big versions like this it is probably better to stand up a fresh
> 8.1.02 environment and migrate relevant data from the old system to the
> new. That is my plan when I get a chance to work on upgrading our 7.1
> environment to 8.1.02 myself (although I am working with Linux servers). I
> believe there were quite a few posts to the list in the last six months or
> so regarding exactly this topic so you might want to visit arslist.org
> and search for the old posts there.
>
>
>
> In fact I did a quick search of my mailbox and found a thread named
> “Upgrade to 8.1 AR/ITSM” from just last month regarding this. Contact me
> off-list if you would like me to send over the messages. That thread had a
> mention of the AMIGO program which you should also investigate.
> https://kb.bmc.com/infocenter/index?page=content&id=KA404408
>
>
>
> -Rick
>
>
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arslist@ARSLIST.ORG] *On Behalf Of *Karthick S
> *Sent:* Thursday, February 19, 2015 9:51 PM
> *To:* arslist

Re: Remedy Upgrade - Suggestions required.

[Rick Westbrock]

Good point, it should be easier to get AR working properly then ITSM before 
worrying about getting your old data into the mix. I have the fun of building a 
new product catalog as part of the upgrade as well as changing from 
multi-tenant to single-tenant so it’s going to be a fun ride over here.

-Rick

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Rick Cook
Sent: Friday, February 20, 2015 8:36 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Upgrade - Suggestions required.

**
Yup.  We are doing the same upgrade, and are doing it via the build and migrate 
plan, not an upgrade in place.

There are some bugs in the 8.1.02 installers, too, as I am finding.  All the 
more reason to do it in a simpler environment.

Rick Cook

On Fri, Feb 20, 2015 at 8:29 AM, Rick Westbrock 
mailto:rwestbr...@24hourfit.com>> wrote:
**
Karthick-

I know that others share my opinion that when you are jumping ahead multiple 
big versions like this it is probably better to stand up a fresh 8.1.02 
environment and migrate relevant data from the old system to the new. That is 
my plan when I get a chance to work on upgrading our 7.1 environment to 8.1.02 
myself (although I am working with Linux servers). I believe there were quite a 
few posts to the list in the last six months or so regarding exactly this topic 
so you might want to visit arslist.org<http://arslist.org> and search for the 
old posts there.

In fact I did a quick search of my mailbox and found a thread named “Upgrade to 
8.1 AR/ITSM” from just last month regarding this. Contact me off-list if you 
would like me to send over the messages. That thread had a mention of the AMIGO 
program which you should also investigate. 
https://kb.bmc.com/infocenter/index?page=content&id=KA404408

-Rick

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Karthick S
Sent: Thursday, February 19, 2015 9:51 PM
To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>
Subject: Remedy Upgrade - Suggestions required.

**
We are planning to do an upgrade in Remedy, please provide your suggestions on 
this.

Our current remedy environment is 7.1 Version and it’s database version is SQL 
2005.
We are planning for an upgrade it to latest version 8.1.02 version.
We have planned in 2 sections, first upgrading Remedy 7.1 to 7.6.04 and then to 
7.6.04 to 8.1.02.

We have a new test server which is Windows Server 2012 R2 64 Bit and SQL Server 
2014 64 Bit Enterprise Edition.

We have planned to take a backup copy of AR System DB from production server 
which has DB version 2005 and copied into 2014 SQL DB version, from their we 
can perform the upgrade.
Is it possible, please let me know.?

Or creating a test DB at 2005 SQL version, start the upgrade in Windows Server 
2012 R2 64 Bit and point it to test DB (2005 SQL version) and later on moving 
the DB instance from 2005 SQL DB to 2014 SQL DB.






Regards,
Karthick Sundararajan
_ARSlist: "Where the Answers Are" and have been for 20 years_
_ARSlist: "Where the Answers Are" and have been for 20 years_

_ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade - Suggestions required.

[Rick Cook]

Yup.  We are doing the same upgrade, and are doing it via the build and
migrate plan, not an upgrade in place.

There are some bugs in the 8.1.02 installers, too, as I am finding.  All
the more reason to do it in a simpler environment.

Rick Cook

On Fri, Feb 20, 2015 at 8:29 AM, Rick Westbrock 
wrote:

> **
>
> Karthick-
>
>
>
> I know that others share my opinion that when you are jumping ahead
> multiple big versions like this it is probably better to stand up a fresh
> 8.1.02 environment and migrate relevant data from the old system to the
> new. That is my plan when I get a chance to work on upgrading our 7.1
> environment to 8.1.02 myself (although I am working with Linux servers). I
> believe there were quite a few posts to the list in the last six months or
> so regarding exactly this topic so you might want to visit arslist.org
> and search for the old posts there.
>
>
>
> In fact I did a quick search of my mailbox and found a thread named
> “Upgrade to 8.1 AR/ITSM” from just last month regarding this. Contact me
> off-list if you would like me to send over the messages. That thread had a
> mention of the AMIGO program which you should also investigate.
> https://kb.bmc.com/infocenter/index?page=content&id=KA404408
>
>
>
> -Rick
>
>
>
> *From:* Action Request System discussion list(ARSList) [mailto:
> arslist@ARSLIST.ORG] *On Behalf Of *Karthick S
> *Sent:* Thursday, February 19, 2015 9:51 PM
> *To:* arslist@ARSLIST.ORG
> *Subject:* Remedy Upgrade - Suggestions required.
>
>
>
> **
>
> We are planning to do an upgrade in Remedy, please provide your
> suggestions on this.
>
>
>
> Our current remedy environment is 7.1 Version and it’s database version is
> SQL 2005.
>
> We are planning for an upgrade it to latest version 8.1.02 version.
>
> We have planned in 2 sections, first upgrading Remedy 7.1 to 7.6.04 and
> then to 7.6.04 to 8.1.02.
>
>
>
> We have a new test server which is Windows Server 2012 R2 64 Bit and SQL
> Server 2014 64 Bit Enterprise Edition.
>
>
>
> We have planned to take a backup copy of AR System DB from production
> server which has DB version 2005 and copied into 2014 SQL DB version, from
> their we can perform the upgrade.
>
> Is it possible, please let me know.?
>
>
>
> Or creating a test DB at 2005 SQL version, start the upgrade in Windows
> Server 2012 R2 64 Bit and point it to test DB (2005 SQL version) and later
> on moving the DB instance from 2005 SQL DB to 2014 SQL DB.
>
>
>
>
>
>
>
>
>
>
>
>
>
> *Regards,*
>
> *Karthick Sundararajan*
>
> _ARSlist: "Where the Answers Are" and have been for 20 years_
>  _ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade - Suggestions required.

[Rick Westbrock]

Karthick-

I know that others share my opinion that when you are jumping ahead multiple 
big versions like this it is probably better to stand up a fresh 8.1.02 
environment and migrate relevant data from the old system to the new. That is 
my plan when I get a chance to work on upgrading our 7.1 environment to 8.1.02 
myself (although I am working with Linux servers). I believe there were quite a 
few posts to the list in the last six months or so regarding exactly this topic 
so you might want to visit arslist.org and search for the old posts there.

In fact I did a quick search of my mailbox and found a thread named "Upgrade to 
8.1 AR/ITSM" from just last month regarding this. Contact me off-list if you 
would like me to send over the messages. That thread had a mention of the AMIGO 
program which you should also investigate. 
https://kb.bmc.com/infocenter/index?page=content&id=KA404408

-Rick

From: Action Request System discussion list(ARSList) 
[mailto:arslist@ARSLIST.ORG] On Behalf Of Karthick S
Sent: Thursday, February 19, 2015 9:51 PM
To: arslist@ARSLIST.ORG
Subject: Remedy Upgrade - Suggestions required.

**
We are planning to do an upgrade in Remedy, please provide your suggestions on 
this.

Our current remedy environment is 7.1 Version and it's database version is SQL 
2005.
We are planning for an upgrade it to latest version 8.1.02 version.
We have planned in 2 sections, first upgrading Remedy 7.1 to 7.6.04 and then to 
7.6.04 to 8.1.02.

We have a new test server which is Windows Server 2012 R2 64 Bit and SQL Server 
2014 64 Bit Enterprise Edition.

We have planned to take a backup copy of AR System DB from production server 
which has DB version 2005 and copied into 2014 SQL DB version, from their we 
can perform the upgrade.
Is it possible, please let me know.?

Or creating a test DB at 2005 SQL version, start the upgrade in Windows Server 
2012 R2 64 Bit and point it to test DB (2005 SQL version) and later on moving 
the DB instance from 2005 SQL DB to 2014 SQL DB.






Regards,
Karthick Sundararajan
_ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Remedy Upgrade - Suggestions required.

[Karthick S]

We are planning to do an upgrade in Remedy, please provide your suggestions
on this.



Our current remedy environment is 7.1 Version and it's database version is
SQL 2005.

We are planning for an upgrade it to latest version 8.1.02 version.

We have planned in 2 sections, first upgrading Remedy 7.1 to 7.6.04 and
then to 7.6.04 to 8.1.02.



We have a new test server which is Windows Server 2012 R2 64 Bit and SQL
Server 2014 64 Bit Enterprise Edition.



We have planned to take a backup copy of AR System DB from production
server which has DB version 2005 and copied into 2014 SQL DB version, from
their we can perform the upgrade.

Is it possible, please let me know.?



Or creating a test DB at 2005 SQL version, start the upgrade in Windows
Server 2012 R2 64 Bit and point it to test DB (2005 SQL version) and later
on moving the DB instance from 2005 SQL DB to 2014 SQL DB.







*Regards,*

*Karthick Sundararajan*

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

[ADV] ARSmarts to ease your Remedy upgrade.

[Support]

Hello List,

Here is a nice reaction we received from someone who is evaluating 
ARSmarts :-)


/Just a thought, have you considered partnering with BMC? It seems like 
your product will help many folks who are upgrading to the next version 
of Remedy.


/Cheers.

Kaïs.
kais.albas...@arsmarts.com.

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade to 8 - LDAP Integration - sAMAccountName

[BradRemedy]

Hi Lj

Thanks for that advice - will try that and let you know if I manage to sort
this out. Will also log a support ticket with BMC so long so that they can
confirm on their side and log a bug if necessary.

Thanks again


On Fri, Nov 8, 2013 at 5:28 PM, LJ LongWing  wrote:

> **
> Brad,
> One thing you may be experiencing is with the change from C LDAP plugin to
> Java LDAP Plugin, one thing you could try is to disable the Java one,
> re-implement the C one, and see if the problem goes away...if it does,
> obviously log a bug on the Java version with BMC.  If the problem remains,
> you may have a mapping difference on your Vendor form, check what attribute
> the Request ID field is mapped to on both systems to verify where the
> problem may be coming from.
>
>
> On Fri, Nov 8, 2013 at 6:27 AM, BradRemedy  wrote:
>
>> **
>> Howdy all
>>
>> Hope everyone is well
>>
>> We are in the process of testing a upgrade from 7.5 patch 003 to version
>> 8 patch 002. On the old version of Remedy, we had a simple vendor form that
>> connected to our AD server and returned the AD details of our users.
>>
>> On our test server, we have setup version 8 and configured the LDAP
>> integration exactly the same way as our current live server.
>>
>> However, when we do a search on our live system (running 7.5 patch 003)
>> on the vendor form, we get a result in the 'Request ID' field of 'johns'.
>>
>> The same searchon the version 8 system however, we are getting back
>>  "DC=abcops,DC=ne|t:-:johns"
>>
>> This is affecting our SSO solution and for the life of me I cannot figure
>> out why we are getting a different format back.
>>
>> Has anyone experience this or have any idea on where I can start looking.
>>
>> I have also checked the source code in the AD system and
>> the sAMAccountName is correctly stored as "johns".
>>
>> Any advice or assistance is appreciated.
>>
>> Thanks
>> Brad
>> _ARSlist: "Where the Answers Are" and have been for 20 years_
>
>
> _ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade to 8 - LDAP Integration - sAMAccountName

[LJ LongWing]

Brad,
One thing you may be experiencing is with the change from C LDAP plugin to
Java LDAP Plugin, one thing you could try is to disable the Java one,
re-implement the C one, and see if the problem goes away...if it does,
obviously log a bug on the Java version with BMC.  If the problem remains,
you may have a mapping difference on your Vendor form, check what attribute
the Request ID field is mapped to on both systems to verify where the
problem may be coming from.


On Fri, Nov 8, 2013 at 6:27 AM, BradRemedy  wrote:

> **
> Howdy all
>
> Hope everyone is well
>
> We are in the process of testing a upgrade from 7.5 patch 003 to version 8
> patch 002. On the old version of Remedy, we had a simple vendor form that
> connected to our AD server and returned the AD details of our users.
>
> On our test server, we have setup version 8 and configured the LDAP
> integration exactly the same way as our current live server.
>
> However, when we do a search on our live system (running 7.5 patch 003) on
> the vendor form, we get a result in the 'Request ID' field of 'johns'.
>
> The same searchon the version 8 system however, we are getting back
>  "DC=abcops,DC=ne|t:-:johns"
>
> This is affecting our SSO solution and for the life of me I cannot figure
> out why we are getting a different format back.
>
> Has anyone experience this or have any idea on where I can start looking.
>
> I have also checked the source code in the AD system and
> the sAMAccountName is correctly stored as "johns".
>
> Any advice or assistance is appreciated.
>
> Thanks
> Brad
> _ARSlist: "Where the Answers Are" and have been for 20 years_

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Remedy Upgrade to 8 - LDAP Integration - sAMAccountName

[BradRemedy]

Howdy all

Hope everyone is well

We are in the process of testing a upgrade from 7.5 patch 003 to version 8
patch 002. On the old version of Remedy, we had a simple vendor form that
connected to our AD server and returned the AD details of our users.

On our test server, we have setup version 8 and configured the LDAP
integration exactly the same way as our current live server.

However, when we do a search on our live system (running 7.5 patch 003) on
the vendor form, we get a result in the 'Request ID' field of 'johns'.

The same searchon the version 8 system however, we are getting back
 "DC=abcops,DC=ne|t:-:johns"

This is affecting our SSO solution and for the life of me I cannot figure
out why we are getting a different format back.

Has anyone experience this or have any idea on where I can start looking.

I have also checked the source code in the AD system and the sAMAccountName
is correctly stored as "johns".

Any advice or assistance is appreciated.

Thanks
Brad

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Re: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

[Peter Romain]

I have installed ARS 7.1 Patch 2 against Java 1.6 U6 and ARS 7.1 Patch 7
with Java 1.6 U16.

The readme for ARS 7.1 Patch 5 has the following fixed issue:

SW00298577
The Plug-in server was unable to load the web services dll when running on
Java 1.6.0_05 and threw an error: Unable to extract minor version from Java
VM version string: 10.0-b19 (ARERR 9130).

I assume that you are using an unpatched ARS 7.1.

If upgrading Java doesn't solve the problem then is an upgrade of ARS
possible?

Failing this you might need to install Java 1.5.

Cheers

Peter


-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Opela, Gary L CTR USAF ABW 72
ABW/SCOOA
Sent: 24 May 2010 15:09
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

I'm running Java version 1.6_16. I will upgrade to Update 20 and see if
that fixes it. I think that is probably a good indication, I forgot that
whenever the log files say that remedy is unable to find the minor
version, that usually means that I'm using an unsupported version. My
confusion is just htat 1.6 update 16 is not that old.

I'll update version quickly and then let you know how it goes. Thanks
for the suggestion.


Thanks,

Gary Opela, Jr.
Sr. Remedy Engineer
Avaya Phone Admin
RSP Cert, Sec+
COMM: 405 582 4272


-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W
Sent: Monday, May 24, 2010 9:07 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

** 

It looks like 7.1 is having a problem with your Java version "Unable to
extract minor version from Java VM version string: 16.0-b13" and that is
what is causing DSO not to run.  What version of Java are you running?

 

From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Opela, Gary L CTR USAF ABW 72
ABW/SCOOA
Sent: Sunday, May 23, 2010 5:14 PM
To: arslist@ARSLIST.ORG
Subject: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

 

** 

I upgraded from AR System version 6.3 to version 7.1 (Version 7.1.00
Build 200708221849).

 

I upgraded the system, all went well. I then created the licenses in the
license form, including the DSO license. However, whenever I try to DSO
a ticket from my server to another server, below are the lines generated
in the arerror.log:

 

Sun May 23 16:37:56 2010 : Action Request System(R) Server Version
7.1.00 Build 200708221849

(c) Copyright 1991-2007 BMC Software, Inc. 

Sun May 23 16:37:56 2010  390695 : Unable to extract minor version from
Java VM version string: 16.0-b13 (ARERR 9130)

Sun May 23 16:50:38 2010  Distrib : The server being accessed is not
licensed for the Distributed Server Option (ARDSERR 3106)

Sun May 23 16:50:38 2010 

Sun May 23 16:51:09 2010  Distrib : The server being accessed is not
licensed for the Distributed Server Option (ARDSERR 3106)

Sun May 23 16:51:09 2010 

Sun May 23 16:51:09 2010  Distrib : Pending distributed operation for
this entry canceled due to error (ARDSNOTE 3003)

Sun May 23 16:51:09 2010  - 

 

 

If the remote server is version 6.3, will I not be able to DSO tickets
to it from a 7.1 server??

 

 

Thanks,

 

Gary Opela, Jr.

Sr. Remedy Engineer

Avaya Phone Admin

RSP Cert, Sec+

COMM: 405 582 4272

 

 

_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"

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Re: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

[Walters, Mark]

This error;

Sun May 23 16:37:56 2010  390695 : Unable to extract minor version from Java VM 
version string: 16.0-b13 (ARERR 9130)

Is coming from the webservices plugin - it has a problem parsing the bxx bit of 
the version string.  This has been fixed, you need the latest libwebservice 
plugin file for your platform, it should be available from the patches download 
area.  It's not related to the DSO problem.

Have you checked the DSO-User-Password settings on both servers - remember that 
a DSO password is mandatory in 7.1 and you'll need to configure the 6.3 server 
to use it.

Mark

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Opela, Gary L CTR USAF ABW 72 
ABW/SCOOA
Sent: 24 May 2010 15:09
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

I'm running Java version 1.6_16. I will upgrade to Update 20 and see if that 
fixes it. I think that is probably a good indication, I forgot that whenever 
the log files say that remedy is unable to find the minor version, that usually 
means that I'm using an unsupported version. My confusion is just htat 1.6 
update 16 is not that old.

I'll update version quickly and then let you know how it goes. Thanks for the 
suggestion.


Thanks,

Gary Opela, Jr.
Sr. Remedy Engineer
Avaya Phone Admin
RSP Cert, Sec+
COMM: 405 582 4272


-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W
Sent: Monday, May 24, 2010 9:07 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

** 

It looks like 7.1 is having a problem with your Java version "Unable to extract 
minor version from Java VM version string: 16.0-b13" and that is what is 
causing DSO not to run.  What version of Java are you running?

 

From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Opela, Gary L CTR USAF ABW 72 
ABW/SCOOA
Sent: Sunday, May 23, 2010 5:14 PM
To: arslist@ARSLIST.ORG
Subject: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

 

** 

I upgraded from AR System version 6.3 to version 7.1 (Version 7.1.00 Build 
200708221849).

 

I upgraded the system, all went well. I then created the licenses in the 
license form, including the DSO license. However, whenever I try to DSO a 
ticket from my server to another server, below are the lines generated in the 
arerror.log:

 

Sun May 23 16:37:56 2010 : Action Request System(R) Server Version
7.1.00 Build 200708221849

(c) Copyright 1991-2007 BMC Software, Inc. 

Sun May 23 16:37:56 2010  390695 : Unable to extract minor version from Java VM 
version string: 16.0-b13 (ARERR 9130)

Sun May 23 16:50:38 2010  Distrib : The server being accessed is not licensed 
for the Distributed Server Option (ARDSERR 3106)

Sun May 23 16:50:38 2010 

Sun May 23 16:51:09 2010  Distrib : The server being accessed is not licensed 
for the Distributed Server Option (ARDSERR 3106)

Sun May 23 16:51:09 2010 

Sun May 23 16:51:09 2010  Distrib : Pending distributed operation for this 
entry canceled due to error (ARDSNOTE 3003)

Sun May 23 16:51:09 2010  - 

 

 

If the remote server is version 6.3, will I not be able to DSO tickets to it 
from a 7.1 server??

 

 

Thanks,

 

Gary Opela, Jr.

Sr. Remedy Engineer

Avaya Phone Admin

RSP Cert, Sec+

COMM: 405 582 4272

 

 

_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"

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Re: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

[Rick Cook]

I had the same impression as Fred, but I think we are both thinking not that
your Java is too old, but that it is too recent for 7.1.  Try a 1.5 version.

Rick
On Mon, May 24, 2010 at 7:08 AM, Opela, Gary L CTR USAF ABW 72 ABW/SCOOA <
gary.opela@tinker.af.mil> wrote:

> I'm running Java version 1.6_16. I will upgrade to Update 20 and see if
> that fixes it. I think that is probably a good indication, I forgot that
> whenever the log files say that remedy is unable to find the minor
> version, that usually means that I'm using an unsupported version. My
> confusion is just htat 1.6 update 16 is not that old.
>
> I'll update version quickly and then let you know how it goes. Thanks
> for the suggestion.
>
>
> Thanks,
>
> Gary Opela, Jr.
> Sr. Remedy Engineer
> Avaya Phone Admin
> RSP Cert, Sec+
> COMM: 405 582 4272
>
>
> -Original Message-
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W
> Sent: Monday, May 24, 2010 9:07 AM
> To: arslist@ARSLIST.ORG
> Subject: Re: Remedy Upgrade -- Now DSO doesn't work -- Urgent!
>
> **
>
> It looks like 7.1 is having a problem with your Java version "Unable to
> extract minor version from Java VM version string: 16.0-b13" and that is
> what is causing DSO not to run.  What version of Java are you running?
>
>
>
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] On Behalf Of Opela, Gary L CTR USAF ABW 72
> ABW/SCOOA
> Sent: Sunday, May 23, 2010 5:14 PM
> To: arslist@ARSLIST.ORG
> Subject: Remedy Upgrade -- Now DSO doesn't work -- Urgent!
>
>
>
> **
>
> I upgraded from AR System version 6.3 to version 7.1 (Version 7.1.00
> Build 200708221849).
>
>
>
> I upgraded the system, all went well. I then created the licenses in the
> license form, including the DSO license. However, whenever I try to DSO
> a ticket from my server to another server, below are the lines generated
> in the arerror.log:
>
>
>
> Sun May 23 16:37:56 2010 : Action Request System(R) Server Version
> 7.1.00 Build 200708221849
>
> (c) Copyright 1991-2007 BMC Software, Inc.
>
> Sun May 23 16:37:56 2010  390695 : Unable to extract minor version from
> Java VM version string: 16.0-b13 (ARERR 9130)
>
> Sun May 23 16:50:38 2010  Distrib : The server being accessed is not
> licensed for the Distributed Server Option (ARDSERR 3106)
>
> Sun May 23 16:50:38 2010 
>
> Sun May 23 16:51:09 2010  Distrib : The server being accessed is not
> licensed for the Distributed Server Option (ARDSERR 3106)
>
> Sun May 23 16:51:09 2010 
>
> Sun May 23 16:51:09 2010  Distrib : Pending distributed operation for
> this entry canceled due to error (ARDSNOTE 3003)
>
> Sun May 23 16:51:09 2010  - 
>
>
>
>
>
> If the remote server is version 6.3, will I not be able to DSO tickets
> to it from a 7.1 server??
>
>
>
>
>
> Thanks,
>
>
>
> Gary Opela, Jr.
>
> Sr. Remedy Engineer
>
> Avaya Phone Admin
>
> RSP Cert, Sec+
>
> COMM: 405 582 4272
>
>
>
>
>
> _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"
>

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Re: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

[Opela, Gary L CTR USAF ABW 72 ABW/SCOOA]

I'm running Java version 1.6_16. I will upgrade to Update 20 and see if
that fixes it. I think that is probably a good indication, I forgot that
whenever the log files say that remedy is unable to find the minor
version, that usually means that I'm using an unsupported version. My
confusion is just htat 1.6 update 16 is not that old.

I'll update version quickly and then let you know how it goes. Thanks
for the suggestion.


Thanks,

Gary Opela, Jr.
Sr. Remedy Engineer
Avaya Phone Admin
RSP Cert, Sec+
COMM: 405 582 4272


-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Grooms, Frederick W
Sent: Monday, May 24, 2010 9:07 AM
To: arslist@ARSLIST.ORG
Subject: Re: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

** 

It looks like 7.1 is having a problem with your Java version "Unable to
extract minor version from Java VM version string: 16.0-b13" and that is
what is causing DSO not to run.  What version of Java are you running?

 

From: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] On Behalf Of Opela, Gary L CTR USAF ABW 72
ABW/SCOOA
Sent: Sunday, May 23, 2010 5:14 PM
To: arslist@ARSLIST.ORG
Subject: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

 

** 

I upgraded from AR System version 6.3 to version 7.1 (Version 7.1.00
Build 200708221849).

 

I upgraded the system, all went well. I then created the licenses in the
license form, including the DSO license. However, whenever I try to DSO
a ticket from my server to another server, below are the lines generated
in the arerror.log:

 

Sun May 23 16:37:56 2010 : Action Request System(R) Server Version
7.1.00 Build 200708221849

(c) Copyright 1991-2007 BMC Software, Inc. 

Sun May 23 16:37:56 2010  390695 : Unable to extract minor version from
Java VM version string: 16.0-b13 (ARERR 9130)

Sun May 23 16:50:38 2010  Distrib : The server being accessed is not
licensed for the Distributed Server Option (ARDSERR 3106)

Sun May 23 16:50:38 2010 

Sun May 23 16:51:09 2010  Distrib : The server being accessed is not
licensed for the Distributed Server Option (ARDSERR 3106)

Sun May 23 16:51:09 2010 

Sun May 23 16:51:09 2010  Distrib : Pending distributed operation for
this entry canceled due to error (ARDSNOTE 3003)

Sun May 23 16:51:09 2010  - 

 

 

If the remote server is version 6.3, will I not be able to DSO tickets
to it from a 7.1 server??

 

 

Thanks,

 

Gary Opela, Jr.

Sr. Remedy Engineer

Avaya Phone Admin

RSP Cert, Sec+

COMM: 405 582 4272

 

 

_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: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

[Grooms, Frederick W]

It looks like 7.1 is having a problem with your Java version "Unable to extract 
minor version from Java VM version string: 16.0-b13" and that is what is 
causing DSO not to run.  What version of Java are you running?

From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Opela, Gary L CTR USAF ABW 72 
ABW/SCOOA
Sent: Sunday, May 23, 2010 5:14 PM
To: arslist@ARSLIST.ORG
Subject: Remedy Upgrade -- Now DSO doesn't work -- Urgent!

**
I upgraded from AR System version 6.3 to version 7.1 (Version 7.1.00 Build 
200708221849).

I upgraded the system, all went well. I then created the licenses in the 
license form, including the DSO license. However, whenever I try to DSO a 
ticket from my server to another server, below are the lines generated in the 
arerror.log:

Sun May 23 16:37:56 2010 : Action Request System(R) Server Version 7.1.00 Build 
200708221849
(c) Copyright 1991-2007 BMC Software, Inc.
Sun May 23 16:37:56 2010  390695 : Unable to extract minor version from Java VM 
version string: 16.0-b13 (ARERR 9130)
Sun May 23 16:50:38 2010  Distrib : The server being accessed is not licensed 
for the Distributed Server Option (ARDSERR 3106)
Sun May 23 16:50:38 2010 
Sun May 23 16:51:09 2010  Distrib : The server being accessed is not licensed 
for the Distributed Server Option (ARDSERR 3106)
Sun May 23 16:51:09 2010 
Sun May 23 16:51:09 2010  Distrib : Pending distributed operation for this 
entry canceled due to error (ARDSNOTE 3003)
Sun May 23 16:51:09 2010  - 


If the remote server is version 6.3, will I not be able to DSO tickets to it 
from a 7.1 server??


Thanks,

Gary Opela, Jr.
Sr. Remedy Engineer
Avaya Phone Admin
RSP Cert, Sec+
COMM: 405 582 4272



___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Remedy Upgrade -- Now DSO doesn't work -- Urgent!

[Opela, Gary L CTR USAF ABW 72 ABW/SCOOA]

I upgraded from AR System version 6.3 to version 7.1 (Version 7.1.00
Build 200708221849).

 

I upgraded the system, all went well. I then created the licenses in the
license form, including the DSO license. However, whenever I try to DSO
a ticket from my server to another server, below are the lines generated
in the arerror.log:

 

Sun May 23 16:37:56 2010 : Action Request System(R) Server Version
7.1.00 Build 200708221849

(c) Copyright 1991-2007 BMC Software, Inc. 

Sun May 23 16:37:56 2010  390695 : Unable to extract minor version from
Java VM version string: 16.0-b13 (ARERR 9130)

Sun May 23 16:50:38 2010  Distrib : The server being accessed is not
licensed for the Distributed Server Option (ARDSERR 3106)

Sun May 23 16:50:38 2010 

Sun May 23 16:51:09 2010  Distrib : The server being accessed is not
licensed for the Distributed Server Option (ARDSERR 3106)

Sun May 23 16:51:09 2010 

Sun May 23 16:51:09 2010  Distrib : Pending distributed operation for
this entry canceled due to error (ARDSNOTE 3003)

Sun May 23 16:51:09 2010  - 

 

 

If the remote server is version 6.3, will I not be able to DSO tickets
to it from a 7.1 server??

 

 

Thanks,

 

Gary Opela, Jr.

Sr. Remedy Engineer

Avaya Phone Admin

RSP Cert, Sec+

COMM: 405 582 4272

 


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug10 www.wwrug.com ARSlist: "Where the Answers Are"

Re: Remedy Upgrade

[Misi Mladoniczky]

Hi,

Why upgrade before you move?

I would do a clean AIX-install of the new version and then:
- Import groups
- Import defs (except the system forms)
- Fix the permissions on yor system forms to match any customization you
may have done
- Use RRR|DefHideExpandBox to restore your layout after
Submitter/Assigned/Modified are increased in size
(https://www.rrr.se/cgi/tools/main#rrrDefHideExpandBox)
- Move the rest of the data using the API. For example with RRR|Chive
(https://www.rrr.se/cgi/rrrchive/main)
- Test the new server
- Do a final incremental (RRR|Chive) data transfer and switch your DNS to
point on the new server

This solution will let you run your servers parallell entil you are ready
to switch. This will minimize downtime.

The data copying tool RRR|Chive can do incremental transfers of data
between your servers. This enables you to:
- Change any data on the new server and get it restored afterwords
- Do a last incremental transfer from the old production system and then
change DNS-settings

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.
* RRR|Translator - Manage and automate your language translations.
Find these products, and many free tools and utilities, at http://rrr.se.

> We are on Oracle 10g running on HP UX.   We need to upgrade before moving
> to IBM AIX.
>
> Thank you,
>
> Gary Roach
> gary.ro...@kennametal.com
>
>
>
>
>
> "Grooms, Frederick W" 
> Sent by: "Action Request System discussion list(ARSList)"
> 
> 02/19/2009 10:48 AM
> Please respond to
> arslist@ARSLIST.ORG
>
>
> To
> arslist@ARSLIST.ORG
> cc
>
> Subject
> Re: Remedy Upgrade
>
>
>
>
>
>
> It would help if you would state what OS and DB (Also if you are using any
> Remedy applications like ITSM).
>
> We recently did this.
>  First we pushed out the 7.1.0 patch 004 client to the users
>  We were already on Oracle 10g so no change there
>  We were on Solaris 8 so we had to upgrade to Solaris 9 or 10 (We did 10)
>
>  We do not use any of the canned applications (pure custom shop)
>  The Upgrade took about 90 minutes (since it has to go thru each form and
> update the size of each Created_By and Last_modified_By field)
>
> Fred
>
> -Original Message-
> From: Action Request System discussion list(ARSList)
> [mailto:arsl...@arslist.org] On Behalf Of Gary Roach
> Sent: Thursday, February 19, 2009 8:47 AM
> To: arslist@ARSLIST.ORG
> Subject: Remedy Upgrade
>
> We are on a 6.0.3  patch 020 server.  Client 6.00.1 patch 1364.   we want
> to upgrade to v 7.1.   Can anyone say how long (time) this would typically
> take ?
>
> Thank you,
>
> Gary Roach
> gary.ro...@kennametal.com
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
>
>
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor: RMI Solutions 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
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"

Re: Remedy Upgrade

[Gary Roach]

We are on Oracle 10g running on HP UX.   We need to upgrade before moving 
to IBM AIX. 

Thank you,

Gary Roach
gary.ro...@kennametal.com





"Grooms, Frederick W"  
Sent by: "Action Request System discussion list(ARSList)" 

02/19/2009 10:48 AM
Please respond to
arslist@ARSLIST.ORG


To
arslist@ARSLIST.ORG
cc

Subject
Re: Remedy Upgrade






It would help if you would state what OS and DB (Also if you are using any 
Remedy applications like ITSM).

We recently did this. 
 First we pushed out the 7.1.0 patch 004 client to the users 
 We were already on Oracle 10g so no change there 
 We were on Solaris 8 so we had to upgrade to Solaris 9 or 10 (We did 10)  

 We do not use any of the canned applications (pure custom shop) 
 The Upgrade took about 90 minutes (since it has to go thru each form and 
update the size of each Created_By and Last_modified_By field) 

Fred

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Gary Roach
Sent: Thursday, February 19, 2009 8:47 AM
To: arslist@ARSLIST.ORG
Subject: Remedy Upgrade

We are on a 6.0.3  patch 020 server.  Client 6.00.1 patch 1364.   we want 
to upgrade to v 7.1.   Can anyone say how long (time) this would typically 
take ? 

Thank you,

Gary Roach
gary.ro...@kennametal.com

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"

Re: Remedy Upgrade

[Grooms, Frederick W]

It would help if you would state what OS and DB (Also if you are using any 
Remedy applications like ITSM).

We recently did this.   
 First we pushed out the 7.1.0 patch 004 client to the users   
 We were already on Oracle 10g so no change there   
 We were on Solaris 8 so we had to upgrade to Solaris 9 or 10 (We did 10)   
 We do not use any of the canned applications (pure custom shop)   
 The Upgrade took about 90 minutes (since it has to go thru each form and 
update the size of each Created_By and Last_modified_By field)

Fred

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Gary Roach
Sent: Thursday, February 19, 2009 8:47 AM
To: arslist@ARSLIST.ORG
Subject: Remedy Upgrade

We are on a 6.0.3  patch 020 server.  Client 6.00.1 patch 1364.   we want to 
upgrade to v 7.1.   Can anyone say how long (time) this would typically take ? 

Thank you,

Gary Roach
gary.ro...@kennametal.com

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"

Remedy Upgrade

[Gary Roach]

We are on a 6.0.3  patch 020 server.  Client 6.00.1 patch 1364.   we want 
to upgrade to v 7.1.   Can anyone say how long (time) this would typically 
take ?

Thank you,

Gary Roach
gary.ro...@kennametal.com

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"

Remedy Upgrade Short Term Contract

[Keith Moon]

Hello;

My company is looking for an experienced Remedy developer or 
installation/upgrade engineer to help us upgrade from version 5.1 to the 
latester verion of 6.X. We have a very minimally configured/customized 
environment.

Job Requirements:

Must Have:
1. 5 or more years of experience on Remedy.
2. Be avaliable to travel and stay at client's hometown of Bakersfield, 
Ca. during engagement.

Nice to Have:
3. Experience in integration of Marimba with Remedy during upgrade.

Thanks,
Keith

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Re: Remedy Upgrade Issue To version 7.0

[patrick zandi]

I think the clob issue:: seems to be coming back now..  was not Clob at all.
it was from Varchar 2000 to Varchar 4000 .. sorry..


On 3/22/07, patrick zandi <[EMAIL PROTECTED]> wrote:


John,
Is this related to my issue with permission on the user form ?
It sounds soo familiar/similar. --view issue

The issue I had was the USER form on an UPGRADE loses it's permissions..
They are trounced on.
I just went to the user form in admintool, and modified the Form
Properties, and added my groups back in.. and saved.
Everything started working correctly after that..
This may not be your specific issue.. but I hope that helps some.

as far as the Clob issue:: I thought there was an easy way to fix that..
Like: open form and save,  or open form, and add 1 field and save, then
delete field and save..
I remember Doug Mueller talking about that.. little fuzzy.. Rug 99 ?


 On 3/22/07, jmchugh <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> We have recently upgraded remedy from ARS version 5.1.2 to 6.0.1 to
> 7.0.1 on Oracle 10g R2 on a Solaris 9 platform.
>
>
> We have found that no long type character fields have converted too
> clobs or varchars as would be expected.
>
>
> The issue has caused all ofending forms too drop there sql views.
>
>
> Has anyone seen this type of issue?
>
>
> What have you done too overcome this issue?
>
>
> Do you have any advice on how this can be resolved?
>
>
> Thanks for your advice in advance.
>
>
> John McHugh
> Remedy Consultant
>
> 
___
>
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
> the Answers Are"
>



--
Patrick Zandi





--
Patrick Zandi

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"

Re: Remedy Upgrade Issue To version 7.0

[patrick zandi]

John,
Is this related to my issue with permission on the user form ?
It sounds soo familiar/similar. --view issue

The issue I had was the USER form on an UPGRADE loses it's permissions..
They are trounced on.
I just went to the user form in admintool, and modified the Form Properties,
and added my groups back in.. and saved.
Everything started working correctly after that..
This may not be your specific issue.. but I hope that helps some.

as far as the Clob issue:: I thought there was an easy way to fix that..
Like: open form and save,  or open form, and add 1 field and save, then
delete field and save..
I remember Doug Mueller talking about that.. little fuzzy.. Rug 99 ?


On 3/22/07, jmchugh <[EMAIL PROTECTED]> wrote:


Hi,

We have recently upgraded remedy from ARS version 5.1.2 to 6.0.1 to
7.0.1 on Oracle 10g R2 on a Solaris 9 platform.


We have found that no long type character fields have converted too
clobs or varchars as would be expected.


The issue has caused all ofending forms too drop there sql views.


Has anyone seen this type of issue?


What have you done too overcome this issue?


Do you have any advice on how this can be resolved?


Thanks for your advice in advance.


John McHugh
Remedy Consultant


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
the Answers Are"





--
Patrick Zandi

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"

Re: Remedy Upgrade Issue To version 7.0

[Eric Roys]

John, 

We have the same issue (same environment, same upgrade path). The immediate
solution per Remedy Support is to export data from the offending form(s)
(i.e. requestID + offending fields), drop/recreate the offending fields, and
then re-import the data with update record preference. The other option I
was given was: submit a bug to support and escalate the ticket to get
feedback from engineering.

HTH,

Eric Roys
Sr. Software Engineer
Verizon Business

CONFIDENTIALITY: The information contained in this message and any
attachment may be proprietary, confidential, and privileged or subject to
the work product doctrine and thus protected from disclosure. If the reader
of this message is not the intended recipient, or an employee or agent
responsible for delivering this message to the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited. If you have received this
communication in error, please notify me immediately by replying to this
message and deleting it and all copies and backups thereof. Thank you.


-Original Message-
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of jmchugh
Sent: Thursday, March 22, 2007 7:19 AM
To: arslist@ARSLIST.ORG
Subject: Remedy Upgrade Issue To version 7.0

Hi,

We have recently upgraded remedy from ARS version 5.1.2 to 6.0.1 to
7.0.1 on Oracle 10g R2 on a Solaris 9 platform.


We have found that no long type character fields have converted too
clobs or varchars as would be expected.


The issue has caused all ofending forms too drop there sql views.


Has anyone seen this type of issue?


What have you done too overcome this issue?


Do you have any advice on how this can be resolved?


Thanks for your advice in advance.


John McHugh
Remedy Consultant


___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the
Answers Are"

__
This e-mail has been scanned by Verizon Managed Email Content Service, using
SkepticT technology powered by MessageLabs. For more information on Verizon
Managed Email Content Service, visit http://www.verizonbusiness.com.
__


__
This e-mail has been scanned by Verizon Managed Email Content Service, using 
Skeptic™ technology powered by MessageLabs. For more information on Verizon 
Managed Email Content Service, visit http://www.verizonbusiness.com.
__

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"

Remedy Upgrade Issue To version 7.0

[jmchugh]

Hi,

We have recently upgraded remedy from ARS version 5.1.2 to 6.0.1 to
7.0.1 on Oracle 10g R2 on a Solaris 9 platform.


We have found that no long type character fields have converted too
clobs or varchars as would be expected.


The issue has caused all ofending forms too drop there sql views.


Has anyone seen this type of issue?


What have you done too overcome this issue?


Do you have any advice on how this can be resolved?


Thanks for your advice in advance.


John McHugh
Remedy Consultant

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"