NetTalk Central

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - oeb

Pages: [1] 2 3
1
Hi Bruce,
I was finally able to test this now.

>>ok, well then if you've removed all your own windows from the app perhaps the next question is whether the program still exhibits the error?
>
Yes, any window will trigger the error. But when I also disable NetTalk the service works as expected.


2
Thanks for your reply.

a) What version of Clarion
Clarion version does not appear to make a difference. Confirmed to occur with both Clarion 6 and 9.1.

Windows version could be more relevant. The error started to appear on Windows Server 2008/ 2012 in autumn 2014. Our software was unchanged since the end of 2013 (and been in development and use several years prior to that). Of course there is a chance we didn't notice it before, but I suspect some sort of change in these versions of Windows caused this. Since changing the user the service runs under sometimes help it makes me think that some sort of resources are running out - but this is just speculation.

b) What version of NetTalk
NetTalk 4.58 is used in production. I have upgraded to NetTalk 8 in development. But so far the error has only occured on the production version.
Please note that I don't suspect that the NetTalk windows in particular have anything to do with the problem - the error fires on the first OPEN(Window) in the program and so far that has not been the NetTalk windows. The error has also occured in a pure source-code project without NetTalk.

c) "How" are you making the program a Service? (SelfService or something else?)
SelfService yes. I should mention that I have seen one (1) occurrence of the error when the app was running as a regular program, but that could have been a different reason of course (the error description "Unable to open window" is pretty generic).

d) Have you played with the PROP:Threading property at all - like setting PROP:Threading to false?
No, but I can try that. This app has no MDI window. Why do you think that could make a difference?

>>windows are not primarily there for "inter thread communication" but rather because they process events. In other words if you have "event driven" code then you need an ACCEPT loop and by implication a WINDOW.
Well, in our own code that was really the only purpose of the windows. We used Event:Notify and GUTS was fine for replacing that.

>>The app one isn't really "hidden" - although of course when running as a service you can't see it.
I know it's not by default - but I have hidden it  :)

>> Is this at all possible to do -
no.
>>Unfortunately that's not an option.
Okay, thanks for clearing that up. I will probably move NetTalk so a separate app.

>>Perhaps the real question to ask is why you are getting this effect with your app, but everyone else who is running Clarion programs as Windows services has not noticed it?
Even though this error happens often enough that we want to find a solution it is still pretty rare. On machines that are frequently rebooted you would probably never notice it. Then error tends to reappear on the same machine, but there could be months in between. For 95% of our clients (very rough estimation) it does not happen at all.

The error might not always be identified though since we only recently added LibHook to the services - this makes it possible to output the error message to a file. Previously the service would just freeze on OPEN(Window) (because the Clarion runtime attempted to open a message box).

3
At several client sites we experience that opening a hidden window in a service cause Clarion runtime error 501 "Internal Error 01: WSLCLASS" or error 529 "Unable to open WINDOW" on OPEN(Window). The only way to temporarily fix this is to reboot the machine or change the user the service is running under - but the problem will eventually return. This service runs on central servers that should not be frequently rebooted so this is not ideal.

SoftVelocity recommended that we replaced the hidden windows with another solution for inter-thread communication and after experimenting with other solutions that is what we decided to do. I use CapeSoft GUTS for this and this works very well.

But I notice that the NetTalk Web Server uses at least two hidden windows. One in the application and at least one internal callback window in the DLL (referenced in the log). I have tried to replace the window in the app with a source procedure. The web server appears to start ok according to the log, but Chrome fails with ERR_CONNECTION_REFUSED when attempting to connect.

Is this at all possible to do - and is the callback window a regular Clarion window or does it use winapi directly? If it is a Clarion window I suspect it will also cause the error and the only remaining solution is to run the service with DebugView as the only GUI option ;)

4
Web Server - Ask For Help / Re: Problem with form in IE8
« on: February 06, 2014, 12:46:46 AM »
That explains it then  :)

5
Web Server - Ask For Help / Re: Problem with form in IE8
« on: February 05, 2014, 04:40:05 AM »
This is NetTalk 7.34. I attempted to re-create the problem with example 21, but the refresh button worked fine there. It turns out that the problem is triggered by including a form (containing two other forms with some display fields) on the same form as the button. It doesn't matter if the form is on another tab. If I place the form below the button (in the form fields list) it works fine, but if I put it above it does not.

I suppose I should not really attempt to "design" the layout using multiple forms, but rather update my CSS knowledge and use DIV to place things where I want them.

6
Web Server - Ask For Help / Problem with form in IE8
« on: February 04, 2014, 12:42:05 AM »
I have a form with some radio controls etc. to set up a filter for a browse on the same form. There is also a refresh button. The refresh button resets the browse and "Send new value to server" is ticked. This works fine on the latest Chrome, Firefox and IE, but IE8 (the latest version supported on Windows XP) does not seem to trigger the [data-do="server"] javascript - nothing happens (no line in the server log). Other standard buttons work fine.

7
Web Server - Ask For Help / Re: Javascript issues with search and sort
« on: April 25, 2013, 03:17:23 AM »
Thanks for looking into this.

a) I had changed this because Scandinavian characters didn't appear correctly, but realize now I should only have changed the "Store Data As" setting.

b) Changing number of records per page fixes the problem indeed (along with correcting the charset setting). Obviously the table will fill with data pretty quickly, but I think it would be confusing for the users if  the locator does not appear before a certain number of records are available - it certainly confused me :). So please let me know how to make it behave differently.

- Ole

8
Web Server - Ask For Help / Re: Javascript issues with search and sort
« on: April 08, 2013, 12:16:38 AM »
I've sent an example by e-mail.

9
Web Server - Ask For Help / Re: Javascript issues with search and sort
« on: March 04, 2013, 02:19:25 AM »
Thanks. Adjusting "packet size" does not appear to have any impact though. I was able to re-create the issue with the locator box not appearing by adding some more columns to the mailboxes browse in NetTalk example 2. I have not yet been able to re-create the issue with sort not working.

10
Has this been implemented (using NT 6.51)?

11
Web Server - Ask For Help / Javascript issues with search and sort
« on: March 01, 2013, 02:32:18 AM »
I'm experiencing some trouble getting javascript search locator and sort to work correctly. It appears that with many columns (in this case 38) in the browse the locator does not appear at all (wizard-generated application with no changes at all). Of course I'm not really going to have 38 columns in the browse, but I don't seem to get any errors anywhere except that it simply doesn't work. When I reduce the number of columns to approx. screen width search/ sort appears, but it still does not always react until I manually refresh the page, i.e. JavaScript is not working like it should. What is the best way to debug this behavior? I'm using NetTalk 6.51/ Clarion 8.0.9759.

12
No, form buttons appear fine - I just have a problem with one of them so that must be another reason. Browse buttons work fine now  :).

13
Thanks. I believe this wasn't really limited to browse buttons - but also affected form buttons?

14
I use the latest build (6.07 from Dec 2).

15
I have a button on a browse and I use "Send Button Click to server" to run some code on the server when this button is clicked. However, I can't get the embedded code to fire in NT6 (Validate::[Button] routine). I ran with the debugger and the routine is simply not run at all. This worked with NT5. Are there any changes related to this in NT6 I should be aware of?

Pages: [1] 2 3