rjfraser1 Absent Member.
Absent Member.
3074 views

verify of trusted app failed

Hi
I uninstalled Mobility, verifying that all directories had been deleted per the notes. When attempting to reinstall I'm getting the error "verify of trusted applications failed". I verified that I can telnet into the PO on port 7191 AND also that proxy is disabled. I deleted and recreated the Trusted app in C1, very carefully noted the name and path of the key file but still get the error. I have rebooted and retired the installation several times.
Any ideas how I can correct this? Thanks.
Labels (1)
0 Likes
15 Replies
Anonymous_User Absent Member.
Absent Member.

Re: verify of trusted app failed

On 12/23/2010 3:36 PM, rjfraser wrote:
>
> Hi
> I uninstalled Mobility, verifying that all directories had been deleted
> per the notes. When attempting to reinstall I'm getting the error
> "verify of trusted applications failed". I verified that I can telnet
> into the PO on port 7191 AND also that proxy is disabled. I deleted and
> recreated the Trusted app in C1, very carefully noted the name and path
> of the key file but still get the error. I have rebooted and retired
> the installation several times.
> Any ideas how I can correct this? Thanks.
>
>

Did you see the POA (verbose logging) get the new key? There's a pretty
clear log message it posts then
0 Likes
rjfraser1 Absent Member.
Absent Member.

Re: verify of trusted app failed

Hi Michael
Thanks for responding. When would I see the PO getting the key? Would I check the log as I create the Trusted App. or during the installation when I get the error?
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: verify of trusted app failed

On 12/23/2010 7:36 PM, rjfraser wrote:
>
> Hi Michael
> Thanks for responding. When would I see the PO getting the key? Would
> I check the log as I create the Trusted App. or during the installation
> when I get the error?
>
>

Both are good and both provide clear messages in the POA log.

hint: d074 means incorrect or missing trusted application

0 Likes
rjfraser1 Absent Member.
Absent Member.

Re: verify of trusted app failed

I don't see anything in the PO log (set to verbose). This is while installing Mobility, during the configuration of the GroupWise connector. I enter the info. for the trusted application and it goes out to verify and returns with the error... I do not see anything in the logs (firewall is turned off). Sounds like a communication problem but this was working, all I did was uninstall the Mobility Pack. One thing I did notice is that in the unistallation notes it said that the certificate files would be deleted. That did not happen.
0 Likes
rjfraser1 Absent Member.
Absent Member.

Re: verify of trusted app failed

Update:
When I edit the Trusted App. in C1 I see this:
07:52:00 28D ADM: Completed: Update object in post office - Trusted Application (Administrator: (PAGANINI) Admin.PEC, Domain: PECDOM)
But when, during GroupWise Connector configuration, it goes out to verify the Trusted App... nothing shows up in the logs.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: verify of trusted app failed

On 12/24/2010 8:06 AM, rjfraser wrote:
>
> I don't see anything in the PO log (set to verbose). This is while
> installing Mobility, during the configuration of the GroupWise
> connector. I enter the info. for the trusted application and it goes out
> to verify and returns with the error... I do not see anything in the
> logs (firewall is turned off). Sounds like a communication problem but
> this was working, all I did was uninstall the Mobility Pack. One thing I
> did notice is that in the unistallation notes it said that the
> certificate files would be deleted. That did not happen.
>
>

Yes, but if you CREATE the trusted app you should see it propagate to
the POA.
0 Likes
rjfraser1 Absent Member.
Absent Member.

Re: verify of trusted app failed

I deleted the TA and recreated it. Here is the log:
09:14:16 28D ADM: Completed: Update object in post office - Trusted Application (Administrator: (PAGANINI) Admin.PEC, Domain: PECDOM)
I then updated the key file on the mobility server and attempted the GW connector configuration and got this (the same error):
Verify of Trusted Application Login failed using
Server: IPAddress
Soap port: 7191
Application name: MobilityTA (the name I gave the TA in C1)
0 Likes
chfritsche Absent Member.
Absent Member.

Re: verify of trusted app failed

from novell data synchronizer doc:
When you set up the GroupWise Connector as a trusted application, you only need to fill in three fields in the Create Trusted Application dialog box in ConsoleOne:

Name
Location for Key File
Name of Key File

Do not fill in any other fields.


I would reinstall the Novell Data Synchronizer and select the Trusted Application File during the install of Novell Data Synchronizer. I have saved the Trusted Application File on my Desktop and copied with winscp to the Novell Data Synchronizer Server.
0 Likes
rjfraser1 Absent Member.
Absent Member.

Re: verify of trusted app failed

Actually, this is exactly what I did. When creating the TA key file I only filled in those fields, save to the local drive and then copied the file to the root of the mobility server with winscp. But, during the installation of the Data Synchronizer I get this error when it tries to verify the TA. I've tried the same process from start several times.
0 Likes
ukdtom Absent Member.
Absent Member.

Re: verify of trusted app failed

Try also and rebuild the PO.....

Looks like there's a comm. issue between the Domain, that ConsoleOne
talks to during the creation, and the PO


--
Tommy Mikkelsen
IT Quality A/S, Denmark
Novell Support Forums SYSOP / NKP

Sorry, but no support through email
Please join http://www.open-horizons.net

Best Regards Tommy Mikkelsen Denmark Please Report back any success or failure, That way we all learn Sorry, but no support through email "I hate bugs".......Tommy Lee Jones, MIB
0 Likes
rjfraser1 Absent Member.
Absent Member.

Re: verify of trusted app failed

I did a Domain and PO rebuild. It made no difference, still having the same problem.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.