fp_idmworks

Vice Admiral
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-11-12
06:32
302 views
4.7.1 upgrade from 4.5 -- do add resource not working
loopback driver, after moving over to a 4.7.1 box can't use the do-add-resource action, etc.
The error was a 401 error
One thing I found... not sure if it was the fix is that a library was updated that I didn't notice with my other compares. I did a driver compare to double check changes, thinking maybe the userapp password was not pushed in the server copy from the old server to the new.... Any who, wondering if anybody knows if the actions rely on a library on the back end. I don't recall seeing any documentation about possible library updates to push out. I would have though that the library would have remained the same name and everything, but that the engine would already have had it in place...
Although... maybe it was something else that fixed it...
I did move it to https and copied the keys in the tomcat.ks file to the engine's cacerts and the encryption errors went away at that point and the 401 error came back... cool that I got the https working 🙂
The error was a 401 error
One thing I found... not sure if it was the fix is that a library was updated that I didn't notice with my other compares. I did a driver compare to double check changes, thinking maybe the userapp password was not pushed in the server copy from the old server to the new.... Any who, wondering if anybody knows if the actions rely on a library on the back end. I don't recall seeing any documentation about possible library updates to push out. I would have though that the library would have remained the same name and everything, but that the engine would already have had it in place...
Although... maybe it was something else that fixed it...
I did move it to https and copied the keys in the tomcat.ks file to the engine's cacerts and the encryption errors went away at that point and the 401 error came back... cool that I got the https working 🙂
1 Reply
Anonymous_User

Absent Member.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
2018-11-12
10:46
fp IDMWORKS <fp_IDMWORKS@no-mx.forums.microfocus.com> wrote:
>
loopback driver, after moving over to a 4.7.1 box can't use the
do-add-resource action, etc.
>
> The error was a 401 error
>
> One thing I found... not sure if it was the fix is that a library was
updated that I didn't notice with my other compares. I did a driver
compare to double check changes, thinking maybe the userapp password was
not pushed in the server copy from the old server to the new.... Any
who, wondering if anybody knows if the actions rely on a library on the
back end. I don't recall seeing any documentation about possible library
updates to push out. I would have though that the library would have
remained the same name and everything, but that the engine would already
have had it in place...
>
> Although... maybe it was something else that fixed it...
>
> I did move it to https and copied the keys in the tomcat.ks file to the
engine's cacerts and the encryption errors went away at that point and
the 401 error came back... cool that I got the https working 🙂
--
fp_IDMWORKS
------------------------------------------------------------------------
fp_IDMWORKS's Profile: https://forums.novell.com/member.php?userid=159589
View this thread: https://forums.novell.com/showthread.php?t=510216
>
Do you have any error messages in catalina.out?
--
Best regards
Marcus
>
loopback driver, after moving over to a 4.7.1 box can't use the
do-add-resource action, etc.
>
> The error was a 401 error
>
> One thing I found... not sure if it was the fix is that a library was
updated that I didn't notice with my other compares. I did a driver
compare to double check changes, thinking maybe the userapp password was
not pushed in the server copy from the old server to the new.... Any
who, wondering if anybody knows if the actions rely on a library on the
back end. I don't recall seeing any documentation about possible library
updates to push out. I would have though that the library would have
remained the same name and everything, but that the engine would already
have had it in place...
>
> Although... maybe it was something else that fixed it...
>
> I did move it to https and copied the keys in the tomcat.ks file to the
engine's cacerts and the encryption errors went away at that point and
the 401 error came back... cool that I got the https working 🙂
--
fp_IDMWORKS
------------------------------------------------------------------------
fp_IDMWORKS's Profile: https://forums.novell.com/member.php?userid=159589
View this thread: https://forums.novell.com/showthread.php?t=510216
>
Do you have any error messages in catalina.out?
--
Best regards
Marcus