Hope you are using the same Excel versions on both PCs. Also, if you use multiple users to login to your Windows 10 PC, make sure you have installed the IBMi Access components either for all users or with the same user id that works with Excel; UAC is much more stringent in Windows 10.

Thank you,

<http://www.touchpath.com/> Venkatesan Srinivasan ( pka VENKY )

Solutions Architect | Senior Consultant | App Developer <#> Mobile/Text

+1 (336) 456 9795 <tel:3364569795> <http://touchpath.com/about-2/partnership/> Office

+1 (336) 885 1373 x13 <tel:3368851373>

Delivering Support from our High Point Offices in NC, USA <http://maps.google.com/?q=2638 Willard Dairy Road, Suite 102, High Point, NC 27265, USA>

This email and any attachments transmitted with it from TouchPath are confidential and intended solely for the use of the individual or entity to whom they are addressed, and may be legally privileged. It may contain confidential, proprietary or legally privileged information. No confidentiality or privilege is waived or lost by any transmission errors. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. You must not, directly or indirectly, use, disclose, distribute, print, or copy any part of this message if you are not the intended recipient. TouchPath and each of its subsidiaries reserve the right to intercept and monitor all e-mail communications through its networks if legally allowed. Message transmission is not guaranteed to be secure.

On 3/30/2020 8:52 PM, Zimmer, Michael wrote:
I have an odd issue happening with iSeries logon, BPCS and Windows 10.
With Win7, I'm able to logon to the BPCS server via the iSeries logon window, start BPCS and work. One of the things I do is run queries on an excel spreadsheet that accesses the BPCS data via an ODBC connection. This set-up has been working for years.
However, now with Windows 10, I logon to the AS400 and start BPCS and I can run multiple sessions just like with Win7. The difference now is that when I run queries using my excel spreadsheet the iSeries logon window pops up (even if I have logged on prior) and requires me to login again. Most times it says that my password is incorrect (even though it is correct). Then I have to close out of all BPCS sessions, and then try to use my spreadsheet.
If I go to a PC that is running Win7, I can use the spreadsheet like I said in my second sentence. Switch to a Win10 PC and the logon problems start.
I have tried amending the connection script in the ODBC, and have tried to make sure all reg keys are the same as a Win7 set-up. But the problem persists.

Has anyone else run into problems with this logon issue and Win10?

Kindest personal regards,

Michael S. Zimmer
IT Service Engineer Rings & Liners
BPCS & Future 3 System Analyst
Information Systems - Tenneco

T: +1 920 686-2269
M: +1 920 629-3359


Please note: Following the acquisition of Federal-Mogul by Tenneco Inc. my email address has changed tomichael.zimmer@xxxxxxxxxxx<mailto:michael.zimmer@xxxxxxxxxxx>. Messages sent to me @federalmogul.com will continue to be delivered for a limited time. Please update my address in your system to ensure your messages will be delivered.

This email may contain privileged or confidential information and is for the sole use of the intended recipient(s).
Any unauthorized use or disclosure of this communication is prohibited. If you believe that you have received
this email in error, please notify the sender immediately and delete it from your system.


For more information regarding our company, please visitwww.tenneco.com
(c) Copyright Tenneco Inc. and/or its affiliates. All rights reserved.

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.