× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



These are C# programs using OLE-DB connection.
They may have found some security issues on their site and are testing.
We do have test win servers and test partition on i, and all works well
there.
Something got lost in the move.
From my side I see the jobs run in QZDASOINIT.
Jim



On Wed, Jul 23, 2014 at 10:44 AM, Richard Schoen <richard@xxxxxxxxxxxxxxx>
wrote:

Jim,

Are you using Client Access/400 or what for connectivity ?

I would have a hard time attributing it directly to a framework update
because unless your app is actually using 4.5.1 and was changed it would
seem suspect that this is the issue.

Make sure you have current service packs and maybe start logging all
transactions on the PC if you can.

That's my two cents without knowing more.

Regards,

Richard Schoen | Director of Document Management Technologies, HelpSystems
T: + 1 952-736-5800
F: + 1 952-736-5801
RJS Software Systems | A Division of HelpSystems
richard@xxxxxxxxxxxxxxx
www.rjssoftware.com

------------------------------

message: 7
date: Wed, 23 Jul 2014 10:16:40 -0400
from: Jim Franz <franz9000@xxxxxxxxx>
subject: windows app problems with .net framework 4.5.1

We are seeing odd failures in database updates from win clients when their
server framework updated to 4.5.1.

Not finding job log info that points to the failures, but database updates
that have worked for years are having issues (example: large strings of
text passed to stored procedure only updating some of the text).
Looking for what server jobs are best to monitor.
Anyone else seen similar issue.
It is certainly possible the whole issue on Win side, but I'm asked to
monitor i side.
Jim Franz


------------------------------

Subject: Digest Footer

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



------------------------------

End of MIDRANGE-L Digest, Vol 13, Issue 1138
********************************************


--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

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

This mailing list archive is Copyright 1997-2024 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.