rhuhman1 Absent Member.
Absent Member.
1339 views

OES Client 2 SP4 (IR10) - Internal Error 0xFFFFFA27

I started to deploy out the OES Client 2 SP4 (IR10) on my end devices and found that my Lenovo 300e 2 in 1 devices are failing with an internal error 0xFFFFFA27 and will not allow logins. It only seems to be occuring on these devices. Searching for this error hasn't revealed a known issue with this client and any specific devices nor does it provide any valid option to resolve as of yet.

Anyone see this on similar deployments and have an idea on how to resolve this? I seem to have full network access outside of this error and can communicate with the device using ZCM. The only error I am seeing in the Windows logs is a reference to LogonUI.exe and a fault in the ntdll.dll file.

Windows 10 1709 is the primary windows version for these devices.

Thanks

Richard
Labels (1)
0 Likes
5 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: OES Client 2 SP4 (IR10) - Internal Error 0xFFFFFA27

Could that be a -1496 error? If so, are you sure your installs have NICI
on them properly?

It may be useful to try iManager Workstation on one of the boxes to see if
it works. Since you have the OES Client, you should have NICI, so
iManager 2.7 Workstation SHOULD work (unless you have NICI 3.x, in which
case get iManager 3.x Workstation), but if not then that may be another
pointer to NICI issues.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
rhuhman1 Absent Member.
Absent Member.

Re: OES Client 2 SP4 (IR10) - Internal Error 0xFFFFFA27

It is an 1497 error. I tried to install the client on a test machine manually to ensure no errors were presented and I get the same error/issue. This is only occurring on the Lenovo 300e. I have Dell, HP, and Toshiba systems that have updated with no issue. I did try to ensure that the NICI folder had the correct rights to ensure that NICI could run but that didn't help either.

I am currently looking at uninstalling IR10 and redeploying IR8a to see if the login is successful after that.
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: OES Client 2 SP4 (IR10) - Internal Error 0xFFFFFA27

On 12-10-18 17:04, rhuhman wrote:
>
> It is an 1497 error. I tried to install the client on a test machine
> manually to ensure no errors were presented and I get the same
> error/issue. This is only occurring on the Lenovo 300e. I have Dell, HP,
> and Toshiba systems that have updated with no issue. I did try to ensure
> that the NICI folder had the correct rights to ensure that NICI could
> run but that didn't help either.
>
> I am currently looking at uninstalling IR10 and redeploying IR8a to see
> if the login is successful after that.
>
>

i had similar issue with a customer with the lenovo dock and the eth
connection. Using the wireless worked fine. He went back to Lenovo to
get it fixed.
0 Likes
rhuhman1 Absent Member.
Absent Member.

Re: OES Client 2 SP4 (IR10) - Internal Error 0xFFFFFA27

Best I can tell this is only an issue with the NICI version 3.0.3.0 on that client. If I go back to Nici 2.77 I don't seem to have the same problems. I can leave the client on IR10 and just move back to that version of NICI without any issues. At least so far.
I did try to contact Lenovo on this. Their support was more then lacking and just wanted me to install the latest Wireless card driver and then told me to contact the software manufacture for additional help.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

Re: OES Client 2 SP4 (IR10) - Internal Error 0xFFFFFA27

On 10/15/2018 07:54 AM, rhuhman wrote:
>
> Best I can tell this is only an issue with the NICI version 3.0.3.0 on
> that client. If I go back to Nici 2.77 I don't seem to have the same
> problems. I can leave the client on IR10 and just move back to that
> version of NICI without any issues. At least so far.


Sounds like an okay workaround. If you have time to report it to Micro
Focus, I do not know that doing so would be a complete waste of time,
particularly since the 2.7.7 version works. If nothing else, a TID to
help others know of the workaround could be created, or maybe a MF/Lenovo
relationship could be leveraged to get a better result.

> I did try to contact Lenovo on this. Their support was more then lacking
> and just wanted me to install the latest Wireless card driver and then
> told me to contact the software manufacture for additional help.


I have seen the same with others when trying to use Lenovo's support, and
really a lot of vendors' support. Working at Novell as I did, I and now
being a partner, I appreciate the support that they offer a lot more than
I ever did before I realized it is not all done that way.

--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
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.