Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.lang.clipper.visual-objects > #8957 > unrolled thread
| Started by | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| First post | 2016-02-10 16:06 +0100 |
| Last post | 2016-02-18 09:33 +0100 |
| Articles | 6 — 2 participants |
Back to article view | Back to comp.lang.clipper.visual-objects
More about the In page error D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2016-02-10 16:06 +0100
Re: More about the In page error "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> - 2016-02-12 16:35 +0100
Re: More about the In page error D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2016-02-12 19:46 +0100
Re: More about the In page error "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> - 2016-02-16 17:54 +0100
Re: More about the In page error D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2016-02-18 11:56 +0100
Re: More about the In page error "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> - 2016-02-18 09:33 +0100
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Date | 2016-02-10 16:06 +0100 |
| Subject | More about the In page error |
| Message-ID | <p4kmbbtu5dt1cm5504e1l8racgl06tq7a5@4ax.com> |
Earlier I wrote that my program gave a 5333 In page error on a button in the program which hadn't changed for maybe years. It can be found in the application Windows log and MSDN writes about this: The thread tried to access a page that was not present, and the system was unable to load the page. For example, this exception might occur a network connection is lost while running a program over the network. Camille Kater wrote that their clients solved it by re-running the program. This did not work for us; the error repeated on the same place, but replacing the exe (with basically the same exe...) worked until they had the same problem a few days later elsewhere in the program. We reset the file+RD server and the problem was gone. All work as Hyper-V virtual machines. I have not seen this In page error before at other clients. I wonder if this is a specific problem with Hyper-V combined with VO programs, or a Hyper-V problem which could also cause problems to other programs. I ask anyone who experienced this problem to post some details so we can maybe find a common factor in it. Dick
[toc] | [next] | [standalone]
| From | "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> |
|---|---|
| Date | 2016-02-12 16:35 +0100 |
| Message-ID | <n9ktu3$805$1@dont-email.me> |
| In reply to | #8957 |
Hi Dick, we have (had) a lot of these errors. Most of the errors happen because the exe is on a file server. And most of the errors can be resolved by making local copies. So we have made a system of local installations where the exe/dlls are copied automatically to a directory of a local drive when trying to start the program. The errors do not seeem to be real network errors. Of course restarting the file server without restarting the client computers can generate these errors. It seems that there are sometimes small delays so that the operating system generates errors instead of waiting. But there is also another phenomenon that had increased the errors on newer machines: Since Windows 2008 in terminal server mode exe/dll are cached automatically for further callings. And unfortunately only code is cached and not the ressources (windows dialog ressources and images). It seems that the Inpage errors can happen if a user starts a program, other users start the same program, the first user finishes his session, the other users use ressources that the first user has not used. We have not found a simple possibility to switch off this caching. Restarting the complete Terminalserver resolves the errors, it is not sufficient to stop single sessions. Installing a new exe/dll resolves this because the OS sees that a new version has been installed. Now the colleages have found also a tricky solution to convince the OS that it always should reload the files from a network because via Active Directory a link to a farm of servers is simulated. But until now for normal customer solutions the local copies have been the best solution. I do not believe that it is a problem of the virtualization. We are using VMWARE and we had these errors. Arne Ortlinghaus ACS Data Systems "D.J.W. van Kooten" <vankooten@removethis.ic2.com> schrieb im Newsbeitrag news:p4kmbbtu5dt1cm5504e1l8racgl06tq7a5@4ax.com... > Earlier I wrote that my program gave a 5333 In page error on a button > in the program which hadn't changed for maybe years. It can be found > in the application Windows log and MSDN writes about this: > > The thread tried to access a page that was not present, and the > system was unable to load the page. For example, this exception might > occur a network connection is lost while running a program over the > network. > > Camille Kater wrote that their clients solved it by re-running the > program. This did not work for us; the error repeated on the same > place, but replacing the exe (with basically the same exe...) worked > until they had the same problem a few days later elsewhere in the > program. > > We reset the file+RD server and the problem was gone. All work as > Hyper-V virtual machines. I have not seen this In page error before at > other clients. > > I wonder if this is a specific problem with Hyper-V combined with VO > programs, or a Hyper-V problem which could also cause problems to > other programs. > > I ask anyone who experienced this problem to post some details so we > can maybe find a common factor in it. > > Dick
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Date | 2016-02-12 19:46 +0100 |
| Message-ID | <js9sbbtbpl229sk0ecjik42kfuvivohv7u@4ax.com> |
| In reply to | #8963 |
On Fri, 12 Feb 2016 16:35:13 +0100, "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> wrote: Hello Arne, > >we have (had) a lot of these errors. >Most of the errors happen because the exe is on a file server. And most of >the errors can be resolved by making local copies. So we have made a system >of local installations where the exe/dlls are copied automatically to a >directory of a local drive when trying to start the program. Thanks a lot for your extensive reply. You've done an awful lot of research and I directly believe that what you wrote is the cause. Only not sure why it started to appear more recently. Also the local copies are no solution for our client as they work via Remote desktop. The exe runs on a file server together with ADS. >Now the colleages have found also a tricky solution to convince >the OS that it always should reload the files from a network because via >Active Directory a link to a farm of >servers is simulated. But until now for normal customer solutions the local >copies have been the best solution. Do you happen to have more details about this trick? It seems that working in the ever more complicated network (Windows and other) environments yield more and more problems not directly related to the program - and requires more and more tricks to run... Dick
[toc] | [prev] | [next] | [standalone]
| From | "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> |
|---|---|
| Date | 2016-02-16 17:54 +0100 |
| Message-ID | <n9vk2b$rsi$1@dont-email.me> |
| In reply to | #8965 |
Hello Dick, > Do you happen to have more details about this trick? Yes, I will fetch some details. Unfortunately the colleague who made the work isn't present in the company currently. I have to wait until I can speak personally with him. I remember only the following phrases: - creation of a symbolic share with help of SMB 3.0 and Active directory - Redirection of this symbolic share to a "farm" of file server shares also there may only be one file server behind. - The symbolic shares are not bad. We have them on different systems. So the name of real server is hidden and can be changed. There were some problems with servers/computers older than Windows 7/Windows Server 2008. But having a new environment can help make distributed installations a bit more flexible. > It seems that working in the ever more complicated network (Windows and > other) > environments yield more and more problems not directly related to the > program - and requires more and more tricks to run... In my eyes the Server development and the Microsoft operating systems have had a wonderful development in the last years allowing our programs to do much more than before without many changes in the programs. The reason seems to be that on one hand the innvotion cycles become always shorter and shorter so that the experience for resolving an issue looses worth quickly. On the other hand the IT systems get always more complex. Also what makes work difficult are the many hard virus attacks. I must say that Microsoft makes a great job helping us with all the frequent system updates although sometimes we get problems with these update. Arne "D.J.W. van Kooten" <vankooten@removethis.ic2.com> schrieb im Newsbeitrag news:js9sbbtbpl229sk0ecjik42kfuvivohv7u@4ax.com... > On Fri, 12 Feb 2016 16:35:13 +0100, "Arne Ortlinghaus" > <Arne.Ortlinghaus@acs.it> wrote: > > Hello Arne, > >> >>we have (had) a lot of these errors. >>Most of the errors happen because the exe is on a file server. And most of >>the errors can be resolved by making local copies. So we have made a >>system >>of local installations where the exe/dlls are copied automatically to a >>directory of a local drive when trying to start the program. > > Thanks a lot for your extensive reply. > > You've done an awful lot of research and I directly believe that what > you wrote is the cause. Only not sure why it started to appear more > recently. Also the local copies are no solution for our client as they > work via Remote desktop. The exe runs on a file server together with > ADS. > >>Now the colleages have found also a tricky solution to convince >>the OS that it always should reload the files from a network because via >>Active Directory a link to a farm of >>servers is simulated. But until now for normal customer solutions the >>local >>copies have been the best solution. > > Do you happen to have more details about this trick? It seems that > working in the ever more complicated network (Windows and other) > environments yield more and more problems not directly related to the > program - and requires more and more tricks to run... > > > Dick
[toc] | [prev] | [next] | [standalone]
| From | D.J.W. van Kooten <vankooten@removethis.ic2.com> |
|---|---|
| Date | 2016-02-18 11:56 +0100 |
| Message-ID | <hk7bcbhebbbtqjkd8tlqn1a9ghqta8q9c9@4ax.com> |
| In reply to | #8975 |
On Tue, 16 Feb 2016 17:54:20 +0100, "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> wrote: >Yes, I will fetch some details. Thanks for the time you took to explain me all details. I am still wondering why it hasn't happened for 1,5 year on the same server and seems to stay away most of the time now. After Camille's message I've urged the users to shutdown all programs when they leave the office as maybe that (partly) influences the occurance of this error. However, if it gets worse (again) it's good to know the basics of the workaround from your reply. >In my eyes the Server development and the Microsoft operating systems have >had a wonderful development in the last years allowing our programs to do >much more than before without many changes in the programs. That's an interesting remark. I must say I haven't seen anything in later server versions which I consider a benefit - from a software supplier point of view. Compared to Server 2003, Server2012 is much slower in most respects. E.g. if I want to transfer files from my PC using \\tsclient I get a box which says "waiting" for a long time and then it suddenly starts showing a progress bar on about 3/4 of the width. All that time the server is frozen - I can not open any other windows. In Server 2003, you can both see the whole progress, do something else in between and it's finished faster. I guess the programmers of Server 2012 have never heard about asyn programming <g>. Also the Server Manager makes it more difficult to configure things compared to Server 2003. And that is basically all I see. Oh yes, I realize there's a whole bunch of new features not present in Server 2003 but my only concern is that my programs runs equally reliable (which it doesn't) and I can transferfiles fast (which I can't) and can quickly access basic data and logs (which I can't because everything is hidden deep into the"Server manager") >The reason seems to be that on one hand the innvotion cycles become always >shorter and shorter so that the experience for resolving an issue looses >worth quickly. On the other hand the IT systems get always more complex. >Also what makes work difficult are the many hard virus attacks. I must say >that Microsoft makes a great job helping us with all the frequent system >updates although sometimes we get problems with these update. > That's definitely true. I run system updates every few weeks or sometimes months only which seems an acceptable balance between solving the problems of faulty updates and the -small- chance that something goes wrong which could have been prevented with the latest update. Dick
[toc] | [prev] | [next] | [standalone]
| From | "Arne Ortlinghaus" <Arne.Ortlinghaus@acs.it> |
|---|---|
| Date | 2016-02-18 09:33 +0100 |
| Message-ID | <na3ver$knc$1@dont-email.me> |
| In reply to | #8965 |
Hello Dick, I can tell you something more now. It is quite a lot of work to install everything. - The share to the fileserver link must not point to the fileserver but must point to a domain. - A "DFS" (Distributed File System", also named DFS-N) must be enabled although it is not really used - The file server must make part of the DFS as the only member. - The domain for the link must point to the DFS Al this serves only to convince the terminalserver that it has always to reload the file and not to use the cache. So it is only a work around. Probably with Windows 2016 there will be changes again, positive or negative... My colleague told me that it is quite a lot of work to install all this. We have a type of datacenter where this has been made. For all other situations we use local installations and we will still use them in the future because of the high amount of work needed. Arne "D.J.W. van Kooten" <vankooten@removethis.ic2.com> schrieb im Newsbeitrag news:js9sbbtbpl229sk0ecjik42kfuvivohv7u@4ax.com... > On Fri, 12 Feb 2016 16:35:13 +0100, "Arne Ortlinghaus" > <Arne.Ortlinghaus@acs.it> wrote: > > Hello Arne, > >> >>we have (had) a lot of these errors. >>Most of the errors happen because the exe is on a file server. And most of >>the errors can be resolved by making local copies. So we have made a >>system >>of local installations where the exe/dlls are copied automatically to a >>directory of a local drive when trying to start the program. > > Thanks a lot for your extensive reply. > > You've done an awful lot of research and I directly believe that what > you wrote is the cause. Only not sure why it started to appear more > recently. Also the local copies are no solution for our client as they > work via Remote desktop. The exe runs on a file server together with > ADS. > >>Now the colleages have found also a tricky solution to convince >>the OS that it always should reload the files from a network because via >>Active Directory a link to a farm of >>servers is simulated. But until now for normal customer solutions the >>local >>copies have been the best solution. > > Do you happen to have more details about this trick? It seems that > working in the ever more complicated network (Windows and other) > environments yield more and more problems not directly related to the > program - and requires more and more tricks to run... > > > Dick
[toc] | [prev] | [standalone]
Back to top | Article view | comp.lang.clipper.visual-objects
csiph-web