PDA

View Full Version : New Server



Bob Worsley
18-Apr-2007, 08:02 PM
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.

Eddy Kleinjan
20-Apr-2007, 08:30 AM
Hi Bob,

Most probably the web service is not running or cannot be found. A good starting point is to go to http://localhost/yourapp/webservice.wso and see if it comes up. If you get some error 500 saying that it cannot find the extension or maybe that it shows you the .wso itself instead of processing it, then you need to make sure that the .wso extension is connected with our Visual DataFlex Web Service end-point. The simplest way to do this is by running Web App Administrator and creating the virtual directory that way. The Web App Administrator will register the ..wso extension automatically.

See also:
http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=2056

If this doesn't solve the problem, please let us know.

Eddy Kleinjan



"Bob Worsley" <bworsley@cox.net> wrote in message news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.

Bob Worsley
20-Apr-2007, 11:32 AM
Hi Eddy, thanks for the reply. I probably didn't explain myself very well. The WebApp does run (and so does the webservice) in that I can get to the login screen. I type in the user and password and then I wait for a while until some timeout occurs, and that's when I get the message below.

The webapp was working, what's happened is that I've been adding new functionality and somehow have broken it. Not knowing how all of it functions has been the reason for my question, and of course the documentation at this stage... <g>

For example I changed file "User" to my own security file and didn't realize that there was a field validation in the DD that didn't take blanks and I paid for that one with 3 days of trying to figure out the cryptic error messages I was getting, non of which had any mention of validation. Once I figured that bug out it all was back to working again. Now I've broken something else.

And, I'm not sure how to use http://localhost/yourapp/webservice.wso to good effect. Does this help?
Bob
"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:RrY6UA1gHHA.4972@dacmail.dataaccess.com...
Hi Bob,

Most probably the web service is not running or cannot be found. A good starting point is to go to http://localhost/yourapp/webservice.wso and see if it comes up. If you get some error 500 saying that it cannot find the extension or maybe that it shows you the .wso itself instead of processing it, then you need to make sure that the .wso extension is connected with our Visual DataFlex Web Service end-point. The simplest way to do this is by running Web App Administrator and creating the virtual directory that way. The Web App Administrator will register the ..wso extension automatically.

See also:
http://www.dataaccess.com/kbasepublic/KBPrint.asp?ArticleID=2056

If this doesn't solve the problem, please let us know.

Eddy Kleinjan



"Bob Worsley" <bworsley@cox.net> wrote in message news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.

Bob Worsley
20-Apr-2007, 11:49 AM
Running the login section of http://localhost/yourapp/webservice.wso with the current session key, the login ID and password gets me what looks like the same error.
Bob

Web Service Error
There is a problem with the page you are trying to reach and it cannot be displayed.

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

Technical Information (for support personnel)

a.. More information:
Application error occurred during processing.Technical details for the site administrator: Message time out. The child process did not process the message in a timely manner. Please check the Windows event log for further information about the problem.


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

HTTP 500 - Internal server error
Visual DataFlex Web Application Server

Anders Ohrt
21-Apr-2007, 06:46 AM
> 220: Webservice soap error: Faultcode: soap:Server Faultstring:
> Application
> error occurred during processing.Technical details for the site
> administrator: Message time out. The child process did not process the
> message in a timely manner. Please check the Windows event log for further
> information about the problem.

Have you checked with the debugger what happens in the web app? Sounds like
it's receiving the call but then getting stuck and timing out.

// Anders

Bob Worsley
21-Apr-2007, 06:57 AM
Nope, it all works fine on my development box. I tried deploying a few
examples on my customer's server under their license and that's where I'm
stuck. No debugger there...
Bob

"Anders Öhrt" <Anders.Ohrt@berendsen.se> wrote in message
news:EE9e$qAhHHA.3796@dacmail.dataaccess.com...
>
> > 220: Webservice soap error: Faultcode: soap:Server Faultstring:
> > Application
> > error occurred during processing.Technical details for the site
> > administrator: Message time out. The child process did not process the
> > message in a timely manner. Please check the Windows event log for
further
> > information about the problem.
>
> Have you checked with the debugger what happens in the web app? Sounds
like
> it's receiving the call but then getting stuck and timing out.
>
> // Anders
>
>
>

Anders Ohrt
21-Apr-2007, 06:59 AM
> Nope, it all works fine on my development box. I tried deploying a few
> examples on my customer's server under their license and that's where I'm
> stuck. No debugger there...

And nothing in the logs I assume... Have you enabled desktop interaction for
the service and checked if anything pops up? If not, add Info_Box'es to
trace that the called procedure is entered and exited as expected.

// Anders

Bob Worsley
21-Apr-2007, 08:15 AM
I will have to do that I guess, I was just hoping there was an easy answer
before having to resort to that since it means repetitively changing the app
on the dev box, and moving to the server.
Bob

"Anders Öhrt" <Anders.Ohrt@berendsen.se> wrote in message
news:mtIOWyAhHHA.5596@dacmail.dataaccess.com...
>
> > Nope, it all works fine on my development box. I tried deploying a few
> > examples on my customer's server under their license and that's where
I'm
> > stuck. No debugger there...
>
> And nothing in the logs I assume... Have you enabled desktop interaction
for
> the service and checked if anything pops up? If not, add Info_Box'es to
> trace that the called procedure is entered and exited as expected.
>
> // Anders
>
>
>

wila
21-Apr-2007, 08:51 AM
Anders,

Info_boxes? in a web app? That's a weird suggestion. In that case it is
better to use showln's or redirect that output to a textfile if you like
( i have code for that if you need it)

An info_box would stop your webapp executing, generating the exact same
error that Bob is trying to cure...

He could also change the webapp administrator to log/report errors ONLY.
This is my preferred setting as it highlights potential problems.
Bob, btw, did you check the windows event log?

The inability of Vdf/Webapp to initiate a remote debug session is
sometimes VERY VERY frustrating.

Gosh... i'm sounding a bit negative today eh? It's not all that serious
guys, but the ability for remote debugging would have helped me quite a
few times. My guess is that it would probably also help for the
sillyness with the studio blocking ajax calls.
--
Wil

Anders Öhrt wrote:
>> Nope, it all works fine on my development box. I tried deploying a few
>> examples on my customer's server under their license and that's where I'm
>> stuck. No debugger there...
>
> And nothing in the logs I assume... Have you enabled desktop interaction for
> the service and checked if anything pops up? If not, add Info_Box'es to
> trace that the called procedure is entered and exited as expected.
>
> // Anders
>
>

Bob Worsley
21-Apr-2007, 09:09 AM
Yeah, info_boxes wouldn't have been my choice, turning the desktop on and
showlns would have been better, or maybe my own logging.

As to the event log, no information there other than what's in the main
message, the child process isn't functioning in a timely fashion.

What would be extremely helpful to this relative newbie (to Ajax &
Javascript) is a description of how this all functions - it seems that a web
service is used for internal communications, but how, when, where, etc. I
know the Webapp itself is working since I can get to the login screen
without it whining too much, but something else is now amiss as the session
record isn't being created and I haven't had time to chase down why. I will
be doing so a little later this morning. I KNOW it's things I'm doing, but
it'll take some time to figure out why.
Bob

"Wil van Antwerpen" <info@antwise.com> wrote in message
news:osd42wBhHHA.4972@dacmail.dataaccess.com...
> Anders,
>
> Info_boxes? in a web app? That's a weird suggestion. In that case it is
> better to use showln's or redirect that output to a textfile if you like
> ( i have code for that if you need it)
>
> An info_box would stop your webapp executing, generating the exact same
> error that Bob is trying to cure...
>
> He could also change the webapp administrator to log/report errors ONLY.
> This is my preferred setting as it highlights potential problems.
> Bob, btw, did you check the windows event log?
>
> The inability of Vdf/Webapp to initiate a remote debug session is
> sometimes VERY VERY frustrating.
>
> Gosh... i'm sounding a bit negative today eh? It's not all that serious
> guys, but the ability for remote debugging would have helped me quite a
> few times. My guess is that it would probably also help for the
> sillyness with the studio blocking ajax calls.
> --
> Wil
>
> Anders Öhrt wrote:
> >> Nope, it all works fine on my development box. I tried deploying a few
> >> examples on my customer's server under their license and that's where
I'm
> >> stuck. No debugger there...
> >
> > And nothing in the logs I assume... Have you enabled desktop interaction
for
> > the service and checked if anything pops up? If not, add Info_Box'es to
> > trace that the called procedure is entered and exited as expected.
> >
> > // Anders
> >
> >
>

Anders Ohrt
21-Apr-2007, 10:59 AM
> Info_boxes? in a web app? That's a weird suggestion. In that case it is
> better to use showln's or redirect that output to a textfile if you like
> ( i have code for that if you need it)

I often prefer Info_Box, since it pauses execution while I think. Just
getting lines in a log means I have to figure out what's going after it's
happened, and I prefer to debug "online". In this case, I was assuming it
would just take a single run to pinpoint the error, so he wouldn't even need
to look at a log later. Maybe a bit presumption of me.

// Anders

wila
21-Apr-2007, 12:21 PM
Anders,

> I often prefer Info_Box, since it pauses execution while I think. Just
> getting lines in a log means I have to figure out what's going after it's
> happened, and I prefer to debug "online".

Well since he has the problem on a live server without a debugger i'd
guess that there are times you wouldn't want the process to stop.
Then again, the app might still be in beta and then it's not an issue.

The only time when i use an info_box in debugging scenarios is to get an
easy point of entry for attaching the debugger. So for example a windows
application with command line parameters and no UI, pretty close to a
webapp scenario now i come to think of it. Sometimes the option to be
able to restart an app -which is not in VDF12, nor would it help for a
webapp- just isn't enough.

Then again VDF12 doesn't have a separate debugger either so you can't
attach.

Using info_boxes for debugging purposes feels so 1985...
--
Wil

Anders Ohrt
21-Apr-2007, 12:34 PM
> Well since he has the problem on a live server without a debugger i'd
> guess that there are times you wouldn't want the process to stop.
> Then again, the app might still be in beta and then it's not an issue.

I'm hoping it's beta since it doesn't run... =)


> Then again VDF12 doesn't have a separate debugger either so you can't
> attach.

I've only needed the attach feature a handful of times, but it was nice to
have the option. I guess it's the price we pay for progress, or something.
But, I'm not using VDF12 yet, so I still have the option. But then again,
the VDF 11.1 studio/debugger does an even worse job at debugger the Ajax
library than the VDF12 one, so I'm very much running blind. In 11.1, you
don't even get the "another incomming call" box, it just doesn't attach at
all.


> Using info_boxes for debugging purposes feels so 1985...

Not having a debugger feels a bit 1985 too...

// Anders

wila
21-Apr-2007, 12:56 PM
Anders,

> I've only needed the attach feature a handful of times, but it was nice to
> have the option. I guess it's the price we pay for progress, or something.
> But, I'm not using VDF12 yet, so I still have the option.

[wil] Same here, i have the tendency to skip .0 products for serious work.

> But then again,
> the VDF 11.1 studio/debugger does an even worse job at debugger the Ajax
> library than the VDF12 one, so I'm very much running blind. In 11.1, you
> don't even get the "another incomming call" box, it just doesn't attach at
> all.

[wil] Weird, i used to see that kind of behavior in 11.1 and previously
just fine. Although sometimes the info_box is hidden underneath the browser.
The ajax samples i have only run under 12, so i don't know if it is ajax
specific but that seems strange as its just webservices.

>
>> Using info_boxes for debugging purposes feels so 1985...
>
> Not having a debugger feels a bit 1985 too...
[wil] very true

--
Wil

Anders Ohrt
22-Apr-2007, 04:22 AM
>> But then again,
>> the VDF 11.1 studio/debugger does an even worse job at debugger the Ajax
>> library than the VDF12 one, so I'm very much running blind. In 11.1, you
>> don't even get the "another incomming call" box, it just doesn't attach
>> at all.
>
> [wil] Weird, i used to see that kind of behavior in 11.1 and previously
> just fine. Although sometimes the info_box is hidden underneath the
> browser.
> The ajax samples i have only run under 12, so i don't know if it is ajax
> specific but that seems strange as its just webservices.

I have seen the box when playing with either legacy WebApp or with web
services, but in the Ajax that mixes the two it doesn't show. I have not
investigated it much, so it might be an easy fix.

// Anders

Steven Lemarr
23-Apr-2007, 01:05 PM
Bob,

Check the web site Properties on the IIS computer. On the "Virtual
Directory" tab press the "Configuration" button. then under the "Mappings"
tab check to see if you have a '.wso" entry under "Extension" should look
some like ".wso c:\vdf\12\bin\waswsvc.dll All"

Steve


"Bob Worsley" <bworsley@cox.net> wrote in message
news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
>I built a small WebApp which works on my development box and tried to move
>it to another test box, but when I run it and get to the login screen and
>log in, I get the error below. What am I missing? The event log simply
>says the child process isn't there.
>
> Bob
>
> 220: Webservice soap error: Faultcode: soap:Server Faultstring:
> Application error occurred during processing.Technical details for the
> site administrator: Message time out. The child process did not process
> the message in a timely manner. Please check the Windows event log for
> further information about the problem.
>
>
>

Bob Worsley
24-Apr-2007, 06:13 PM
Yep, it's there all right. Anything else? I've about given up...
Bob

"Steven Lemarr" <steve@jahl.com> wrote in message
news:DY3ySJdhHHA.5152@dacmail.dataaccess.com...
> Bob,
>
> Check the web site Properties on the IIS computer. On the "Virtual
> Directory" tab press the "Configuration" button. then under the
"Mappings"
> tab check to see if you have a '.wso" entry under "Extension" should look
> some like ".wso c:\vdf\12\bin\waswsvc.dll All"
>
> Steve
>
>
> "Bob Worsley" <bworsley@cox.net> wrote in message
> news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
> >I built a small WebApp which works on my development box and tried to
move
> >it to another test box, but when I run it and get to the login screen and
> >log in, I get the error below. What am I missing? The event log simply
> >says the child process isn't there.
> >
> > Bob
> >
> > 220: Webservice soap error: Faultcode: soap:Server Faultstring:
> > Application error occurred during processing.Technical details for the
> > site administrator: Message time out. The child process did not process
> > the message in a timely manner. Please check the Windows event log for
> > further information about the problem.
> >
> >
> >
>
>
>

Eddy Kleinjan
25-Apr-2007, 06:29 AM
Bob,

I would like to get complete picture of your environment in order to be able to help you out. For example, is all of your application running on the same server, or are for example data files included that come from a different server?

The first thing we need to find out (and you probably already did) is whether the WebApp is actually running or not.

If you go to the WebService.wso (using your local http:// ..../WebService.wso), does it present to you the screen with the functions that are available in the Web Service?

If you get this list of functions, then please click on one of the functions. When you do, you should be able to see an entrries in the 'Event Log' of the WebApp Administrator for your application (Note: Not the Windows Event Log, it's the WebApp Event Log). You should see two lines, one "Session Started" and one "Session Ended" (Assuming that your WebApp has been set to "Log all access to the Web Application" in the properties for your application). If you don't see those, or see other messages, then the chances are your WebApp cannot be started at all.

If your WebApp cannot be started at all, then this is most probably because of security rights. One of the things that might go wrong here is that the files you are accessing from your application are on a different computer. Other reasons might be that the account under with the "Visual DataFlex 12.0 Web Application Server" Service runs, doesn't have access to your Programs directory.

If your WebApp runs fine, then try to execute the function "ServiceMetaData" without filling in any of the fields. This should return with a XML message that has the text "Invalid WebObject:" somewhere. When this works, then there is probably nothing wrong with the WebApp itself. In that case you should try to debug the logic that you built in.

Once you have gotten this far, we can take further steps to see where and why things are failing.

Eddy Kleinjan
Data Access Europe

"Bob Worsley" <bworsley@cox.net> wrote in message news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.

Bob Worsley
25-Apr-2007, 05:30 PM
See below.
"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:JlCq0zyhHHA.4972@dacmail.dataaccess.com...
Bob,

I would like to get complete picture of your environment in order to be able to help you out. For example, is all of your application running on the same server, or are for example data files included that come from a different server?
I've got the files for the WebApp on a different server, but moved them to the webapp server just to try. No difference.

The first thing we need to find out (and you probably already did) is whether the WebApp is actually running or not.

If you go to the WebService.wso (using your local http:// ..../WebService.wso), does it present to you the screen with the functions that are available in the Web Service?
No, I get the Web Service Error detailed above

If you get this list of functions, then please click on one of the functions. When you do, you should be able to see an entrries in the 'Event Log' of the WebApp Administrator for your application (Note: Not the Windows Event Log, it's the WebApp Event Log). You should see two lines, one "Session Started" and one "Session Ended" (Assuming that your WebApp has been set to "Log all access to the Web Application" in the properties for your application). If you don't see those, or see other messages, then the chances are your WebApp cannot be started at all.
The Webapp does start, I get to my login screen, and I can see WebApp.exe running in Task Manager. I do get a bunch of errors first though:
Data type error - String used as Number
Session key not known (reload page to recreate session)
And the session record is not created.

If your WebApp cannot be started at all, then this is most probably because of security rights. One of the things that might go wrong here is that the files you are accessing from your application are on a different computer. Other reasons might be that the account under with the "Visual DataFlex 12.0 Web Application Server" Service runs, doesn't have access to your Programs directory.
Moved all files to this server, no difference. I've tried running the service with local system, an administrator account and also with my domain account and get the same results all ways.

If your WebApp runs fine, then try to execute the function "ServiceMetaData" without filling in any of the fields. This should return with a XML message that has the text "Invalid WebObject:" somewhere. When this works, then there is probably nothing wrong with the WebApp itself. In that case you should try to debug the logic that you built in.

Once you have gotten this far, we can take further steps to see where and why things are failing.

Eddy Kleinjan
Data Access Europe

"Bob Worsley" <bworsley@cox.net> wrote in message news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.

Eddy Kleinjan
26-Apr-2007, 05:38 AM
Bob,

I still have the feeling that your WebApp.exe is not 'running' like in 'functioning normally'. In such a case you might see a WebApp.exe in your tasklist, but it is hung or waits for something to happen. Let me try to explain what is going on:

When the WebApp.exe is started by the WebApp Server, it will start up like a normal VDF program and then wait for events to happen. One of the things the WebApp process needs to do during this startup process, is connecting to the WebApp Server process that started the WebApp.exe. I have the feeling that this is not happening. The reason for this might be that WebApp.exe is held up because of some kind of error, for example, because it cannot open a file.

I've enclosed a package that I use in these kinds of situations. This package installs an extra error object that is based on the cWebAppError object. It will log all errors in a file called "ErrorLog.txt" that will be put in your Programs folder. You can include the package just after your "Use AllWebAppClasses.pkg".

Please test this package first on your development machine. To test it, just put an "Error 123 'whatever'" somewhere in your code. It should show this error in the ErrorLog.txt file after you run the app. Don't forget to remove the error after you tested it.

Please let us know what you find out.

Eddy Kleinjan
Data Access Europe






"Bob Worsley" <bworsley@comcast.net> wrote in message news:aT37kk4hHHA.1652@dacmail.dataaccess.com...
See below.
"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:JlCq0zyhHHA.4972@dacmail.dataaccess.com...
Bob,

I would like to get complete picture of your environment in order to be able to help you out. For example, is all of your application running on the same server, or are for example data files included that come from a different server?
I've got the files for the WebApp on a different server, but moved them to the webapp server just to try. No difference.

The first thing we need to find out (and you probably already did) is whether the WebApp is actually running or not.

If you go to the WebService.wso (using your local http:// ..../WebService.wso), does it present to you the screen with the functions that are available in the Web Service?
No, I get the Web Service Error detailed above

If you get this list of functions, then please click on one of the functions. When you do, you should be able to see an entrries in the 'Event Log' of the WebApp Administrator for your application (Note: Not the Windows Event Log, it's the WebApp Event Log). You should see two lines, one "Session Started" and one "Session Ended" (Assuming that your WebApp has been set to "Log all access to the Web Application" in the properties for your application). If you don't see those, or see other messages, then the chances are your WebApp cannot be started at all.
The Webapp does start, I get to my login screen, and I can see WebApp.exe running in Task Manager. I do get a bunch of errors first though:
Data type error - String used as Number
Session key not known (reload page to recreate session)
And the session record is not created.

If your WebApp cannot be started at all, then this is most probably because of security rights. One of the things that might go wrong here is that the files you are accessing from your application are on a different computer. Other reasons might be that the account under with the "Visual DataFlex 12.0 Web Application Server" Service runs, doesn't have access to your Programs directory.
Moved all files to this server, no difference. I've tried running the service with local system, an administrator account and also with my domain account and get the same results all ways.

If your WebApp runs fine, then try to execute the function "ServiceMetaData" without filling in any of the fields. This should return with a XML message that has the text "Invalid WebObject:" somewhere. When this works, then there is probably nothing wrong with the WebApp itself. In that case you should try to debug the logic that you built in.

Once you have gotten this far, we can take further steps to see where and why things are failing.

Eddy Kleinjan
Data Access Europe

"Bob Worsley" <bworsley@cox.net> wrote in message news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.

Bob Worsley
26-Apr-2007, 09:17 PM
Hi Eddy. Tried the logger and turned up two bugs in my programming that didn't show up before. That's been one of my frustrations with WebApp, showing errors and tracking problems. I've fixed both and neither error was stopping the Web Service from running as it does run on my development box but not on the server with or without the errors. Anyway, thanks for the logging package it helps. As to what you're thinking, is it possible for the WebApp to run but the Web Service not to? That's what it feels like to me. How can I better test the Web Service alone? Not sure this helped...
Bob

"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:7V2X67%23hHHA.5880@dacmail.dataaccess.com...
Bob,

I still have the feeling that your WebApp.exe is not 'running' like in 'functioning normally'. In such a case you might see a WebApp.exe in your tasklist, but it is hung or waits for something to happen. Let me try to explain what is going on:

When the WebApp.exe is started by the WebApp Server, it will start up like a normal VDF program and then wait for events to happen. One of the things the WebApp process needs to do during this startup process, is connecting to the WebApp Server process that started the WebApp.exe. I have the feeling that this is not happening. The reason for this might be that WebApp.exe is held up because of some kind of error, for example, because it cannot open a file.

I've enclosed a package that I use in these kinds of situations. This package installs an extra error object that is based on the cWebAppError object. It will log all errors in a file called "ErrorLog.txt" that will be put in your Programs folder. You can include the package just after your "Use AllWebAppClasses.pkg".

Please test this package first on your development machine. To test it, just put an "Error 123 'whatever'" somewhere in your code. It should show this error in the ErrorLog.txt file after you run the app. Don't forget to remove the error after you tested it.

Please let us know what you find out.

Eddy Kleinjan
Data Access Europe






"Bob Worsley" <bworsley@comcast.net> wrote in message news:aT37kk4hHHA.1652@dacmail.dataaccess.com...
See below.
"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:JlCq0zyhHHA.4972@dacmail.dataaccess.com...
Bob,

I would like to get complete picture of your environment in order to be able to help you out. For example, is all of your application running on the same server, or are for example data files included that come from a different server?
I've got the files for the WebApp on a different server, but moved them to the webapp server just to try. No difference.

The first thing we need to find out (and you probably already did) is whether the WebApp is actually running or not.

If you go to the WebService.wso (using your local http:// ..../WebService.wso), does it present to you the screen with the functions that are available in the Web Service?
No, I get the Web Service Error detailed above

If you get this list of functions, then please click on one of the functions. When you do, you should be able to see an entrries in the 'Event Log' of the WebApp Administrator for your application (Note: Not the Windows Event Log, it's the WebApp Event Log). You should see two lines, one "Session Started" and one "Session Ended" (Assuming that your WebApp has been set to "Log all access to the Web Application" in the properties for your application). If you don't see those, or see other messages, then the chances are your WebApp cannot be started at all.
The Webapp does start, I get to my login screen, and I can see WebApp.exe running in Task Manager. I do get a bunch of errors first though:
Data type error - String used as Number
Session key not known (reload page to recreate session)
And the session record is not created.

If your WebApp cannot be started at all, then this is most probably because of security rights. One of the things that might go wrong here is that the files you are accessing from your application are on a different computer. Other reasons might be that the account under with the "Visual DataFlex 12.0 Web Application Server" Service runs, doesn't have access to your Programs directory.
Moved all files to this server, no difference. I've tried running the service with local system, an administrator account and also with my domain account and get the same results all ways.

If your WebApp runs fine, then try to execute the function "ServiceMetaData" without filling in any of the fields. This should return with a XML message that has the text "Invalid WebObject:" somewhere. When this works, then there is probably nothing wrong with the WebApp itself. In that case you should try to debug the logic that you built in.

Once you have gotten this far, we can take further steps to see where and why things are failing.

Eddy Kleinjan
Data Access Europe

"Bob Worsley" <bworsley@cox.net> wrote in message news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.

Bob Worsley
26-Apr-2007, 09:22 PM
Oh, and one other bit. The login screen has stopped working on the server and now it times out with this error:

Error Type:
WebAppServer.WebBusinessProcess.12.0 (0x80020009)
Application error occurred during processing.Technical details for the site administrator:
Message time out. The child process did not process the message in a timely manner.
Please check the Windows event log for further information about the problem.
/ServiceWeb/VdfAjaxLib/1.0/pagetop.inc.asp, line 18

Not sure why line 18...
Bob

"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:7V2X67%23hHHA.5880@dacmail.dataaccess.com...
Bob,

I still have the feeling that your WebApp.exe is not 'running' like in 'functioning normally'. In such a case you might see a WebApp.exe in your tasklist, but it is hung or waits for something to happen. Let me try to explain what is going on:

When the WebApp.exe is started by the WebApp Server, it will start up like a normal VDF program and then wait for events to happen. One of the things the WebApp process needs to do during this startup process, is connecting to the WebApp Server process that started the WebApp.exe. I have the feeling that this is not happening. The reason for this might be that WebApp.exe is held up because of some kind of error, for example, because it cannot open a file.

I've enclosed a package that I use in these kinds of situations. This package installs an extra error object that is based on the cWebAppError object. It will log all errors in a file called "ErrorLog.txt" that will be put in your Programs folder. You can include the package just after your "Use AllWebAppClasses.pkg".

Please test this package first on your development machine. To test it, just put an "Error 123 'whatever'" somewhere in your code. It should show this error in the ErrorLog.txt file after you run the app. Don't forget to remove the error after you tested it.

Please let us know what you find out.

Eddy Kleinjan
Data Access Europe






"Bob Worsley" <bworsley@comcast.net> wrote in message news:aT37kk4hHHA.1652@dacmail.dataaccess.com...
See below.
"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:JlCq0zyhHHA.4972@dacmail.dataaccess.com...
Bob,

I would like to get complete picture of your environment in order to be able to help you out. For example, is all of your application running on the same server, or are for example data files included that come from a different server?
I've got the files for the WebApp on a different server, but moved them to the webapp server just to try. No difference.

The first thing we need to find out (and you probably already did) is whether the WebApp is actually running or not.

If you go to the WebService.wso (using your local http:// ..../WebService.wso), does it present to you the screen with the functions that are available in the Web Service?
No, I get the Web Service Error detailed above

If you get this list of functions, then please click on one of the functions. When you do, you should be able to see an entrries in the 'Event Log' of the WebApp Administrator for your application (Note: Not the Windows Event Log, it's the WebApp Event Log). You should see two lines, one "Session Started" and one "Session Ended" (Assuming that your WebApp has been set to "Log all access to the Web Application" in the properties for your application). If you don't see those, or see other messages, then the chances are your WebApp cannot be started at all.
The Webapp does start, I get to my login screen, and I can see WebApp.exe running in Task Manager. I do get a bunch of errors first though:
Data type error - String used as Number
Session key not known (reload page to recreate session)
And the session record is not created.

If your WebApp cannot be started at all, then this is most probably because of security rights. One of the things that might go wrong here is that the files you are accessing from your application are on a different computer. Other reasons might be that the account under with the "Visual DataFlex 12.0 Web Application Server" Service runs, doesn't have access to your Programs directory.
Moved all files to this server, no difference. I've tried running the service with local system, an administrator account and also with my domain account and get the same results all ways.

If your WebApp runs fine, then try to execute the function "ServiceMetaData" without filling in any of the fields. This should return with a XML message that has the text "Invalid WebObject:" somewhere. When this works, then there is probably nothing wrong with the WebApp itself. In that case you should try to debug the logic that you built in.

Once you have gotten this far, we can take further steps to see where and why things are failing.

Eddy Kleinjan
Data Access Europe

"Bob Worsley" <bworsley@cox.net> wrote in message news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.

Bob Worsley
27-Apr-2007, 09:47 PM
Eddy, I solved part of it. On my development box I spelled the name of my Webapp virtual directory ServiceWeb, but on the server I named it Serviceweb. Reinstalling the service with the same name now permits the Web Service to run when I call it from http://localhost/yourapp/webservice.wso. So far so good.

Now, when I log in, I get to the login screen and enter my ID and password and wait.... and eventually get the attached error. I think I was here a week ago before I reinstalled the service and screwed up the name. I just uninstalled Ajax and reinstalled just in case, but no difference.

Good think the customer isn't sitting around waiting on me. ;-}
Bob

"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:7V2X67%23hHHA.5880@dacmail.dataaccess.com...
Bob,

I still have the feeling that your WebApp.exe is not 'running' like in 'functioning normally'. In such a case you might see a WebApp.exe in your tasklist, but it is hung or waits for something to happen. Let me try to explain what is going on:

When the WebApp.exe is started by the WebApp Server, it will start up like a normal VDF program and then wait for events to happen. One of the things the WebApp process needs to do during this startup process, is connecting to the WebApp Server process that started the WebApp.exe. I have the feeling that this is not happening. The reason for this might be that WebApp.exe is held up because of some kind of error, for example, because it cannot open a file.

I've enclosed a package that I use in these kinds of situations. This package installs an extra error object that is based on the cWebAppError object. It will log all errors in a file called "ErrorLog.txt" that will be put in your Programs folder. You can include the package just after your "Use AllWebAppClasses.pkg".

Please test this package first on your development machine. To test it, just put an "Error 123 'whatever'" somewhere in your code. It should show this error in the ErrorLog.txt file after you run the app. Don't forget to remove the error after you tested it.

Please let us know what you find out.

Eddy Kleinjan
Data Access Europe






"Bob Worsley" <bworsley@comcast.net> wrote in message news:aT37kk4hHHA.1652@dacmail.dataaccess.com...
See below.
"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:JlCq0zyhHHA.4972@dacmail.dataaccess.com...
Bob,

I would like to get complete picture of your environment in order to be able to help you out. For example, is all of your application running on the same server, or are for example data files included that come from a different server?
I've got the files for the WebApp on a different server, but moved them to the webapp server just to try. No difference.

The first thing we need to find out (and you probably already did) is whether the WebApp is actually running or not.

If you go to the WebService.wso (using your local http:// ..../WebService.wso), does it present to you the screen with the functions that are available in the Web Service?
No, I get the Web Service Error detailed above

If you get this list of functions, then please click on one of the functions. When you do, you should be able to see an entrries in the 'Event Log' of the WebApp Administrator for your application (Note: Not the Windows Event Log, it's the WebApp Event Log). You should see two lines, one "Session Started" and one "Session Ended" (Assuming that your WebApp has been set to "Log all access to the Web Application" in the properties for your application). If you don't see those, or see other messages, then the chances are your WebApp cannot be started at all.
The Webapp does start, I get to my login screen, and I can see WebApp.exe running in Task Manager. I do get a bunch of errors first though:
Data type error - String used as Number
Session key not known (reload page to recreate session)
And the session record is not created.

If your WebApp cannot be started at all, then this is most probably because of security rights. One of the things that might go wrong here is that the files you are accessing from your application are on a different computer. Other reasons might be that the account under with the "Visual DataFlex 12.0 Web Application Server" Service runs, doesn't have access to your Programs directory.
Moved all files to this server, no difference. I've tried running the service with local system, an administrator account and also with my domain account and get the same results all ways.

If your WebApp runs fine, then try to execute the function "ServiceMetaData" without filling in any of the fields. This should return with a XML message that has the text "Invalid WebObject:" somewhere. When this works, then there is probably nothing wrong with the WebApp itself. In that case you should try to debug the logic that you built in.

Once you have gotten this far, we can take further steps to see where and why things are failing.

Eddy Kleinjan
Data Access Europe

"Bob Worsley" <bworsley@cox.net> wrote in message news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.

Bob Worsley
28-Apr-2007, 12:11 PM
It's beginning to feel like I'm writing a blog. I just figured out the next piece. Logging in with an incorrect ID/Password combination on the server gives me the error I posted last night, and never gives me the error that I get on my dev box, "Username or password invalid!" In all of this fooling around I'd forgotten that I'd changed the login info on the server. The one big difference between the server and my dev box is that I use FireFix in development, and was using IE on the server. I've just corrected that but I get the same behavior with either browser on the server, never says the ID/password is bad.

So, barring the unforseen, it seems to be sorta working as intended at the moment. Thanks for the help, and see you at Synergy, I've signed up for the Ajax class on Monday.
Bob

"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:7V2X67%23hHHA.5880@dacmail.dataaccess.com...
Bob,

I still have the feeling that your WebApp.exe is not 'running' like in 'functioning normally'. In such a case you might see a WebApp.exe in your tasklist, but it is hung or waits for something to happen. Let me try to explain what is going on:

When the WebApp.exe is started by the WebApp Server, it will start up like a normal VDF program and then wait for events to happen. One of the things the WebApp process needs to do during this startup process, is connecting to the WebApp Server process that started the WebApp.exe. I have the feeling that this is not happening. The reason for this might be that WebApp.exe is held up because of some kind of error, for example, because it cannot open a file.

I've enclosed a package that I use in these kinds of situations. This package installs an extra error object that is based on the cWebAppError object. It will log all errors in a file called "ErrorLog.txt" that will be put in your Programs folder. You can include the package just after your "Use AllWebAppClasses.pkg".

Please test this package first on your development machine. To test it, just put an "Error 123 'whatever'" somewhere in your code. It should show this error in the ErrorLog.txt file after you run the app. Don't forget to remove the error after you tested it.

Please let us know what you find out.

Eddy Kleinjan
Data Access Europe






"Bob Worsley" <bworsley@comcast.net> wrote in message news:aT37kk4hHHA.1652@dacmail.dataaccess.com...
See below.
"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:JlCq0zyhHHA.4972@dacmail.dataaccess.com...
Bob,

I would like to get complete picture of your environment in order to be able to help you out. For example, is all of your application running on the same server, or are for example data files included that come from a different server?
I've got the files for the WebApp on a different server, but moved them to the webapp server just to try. No difference.

The first thing we need to find out (and you probably already did) is whether the WebApp is actually running or not.

If you go to the WebService.wso (using your local http:// ..../WebService.wso), does it present to you the screen with the functions that are available in the Web Service?
No, I get the Web Service Error detailed above

If you get this list of functions, then please click on one of the functions. When you do, you should be able to see an entrries in the 'Event Log' of the WebApp Administrator for your application (Note: Not the Windows Event Log, it's the WebApp Event Log). You should see two lines, one "Session Started" and one "Session Ended" (Assuming that your WebApp has been set to "Log all access to the Web Application" in the properties for your application). If you don't see those, or see other messages, then the chances are your WebApp cannot be started at all.
The Webapp does start, I get to my login screen, and I can see WebApp.exe running in Task Manager. I do get a bunch of errors first though:
Data type error - String used as Number
Session key not known (reload page to recreate session)
And the session record is not created.

If your WebApp cannot be started at all, then this is most probably because of security rights. One of the things that might go wrong here is that the files you are accessing from your application are on a different computer. Other reasons might be that the account under with the "Visual DataFlex 12.0 Web Application Server" Service runs, doesn't have access to your Programs directory.
Moved all files to this server, no difference. I've tried running the service with local system, an administrator account and also with my domain account and get the same results all ways.

If your WebApp runs fine, then try to execute the function "ServiceMetaData" without filling in any of the fields. This should return with a XML message that has the text "Invalid WebObject:" somewhere. When this works, then there is probably nothing wrong with the WebApp itself. In that case you should try to debug the logic that you built in.

Once you have gotten this far, we can take further steps to see where and why things are failing.

Eddy Kleinjan
Data Access Europe

"Bob Worsley" <bworsley@cox.net> wrote in message news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.

Eddy Kleinjan
1-May-2007, 08:53 AM
Hi Bob,

It's good to hear that you where able to solve the problem with the name mismatch. For some reason, the Web App Server does not do a case insensitive compare.

The error message that you got is more or less still the same thing. The key here is that it says "The child process did not process the message in a timely manner". This means that the Web Service has been called, but that the function doesn't return within the 120 seconds (by defaults) that a transaction is allowed to be taken.

It might be a good idea to declere 'errors' when the function is being called, together with the errorlogger I sent earlier. You should then be able to find exactly where this process is hanging. For example:

Function bla...
Error 123 "Starting function"
Call Function 1
Error 123 "Ending functïon"
End_Function

This way you should be able to look in the .txt file that the errorlogger makes to see what is going on.

Good that you join us for the conference and the training!

Eddy Kleinjan
Data Access Europe

"Bob Worsley" <bworsley@comcast.net> wrote in message news:k%235uPgbiHHA.5596@dacmail.dataaccess.com...
It's beginning to feel like I'm writing a blog. I just figured out the next piece. Logging in with an incorrect ID/Password combination on the server gives me the error I posted last night, and never gives me the error that I get on my dev box, "Username or password invalid!" In all of this fooling around I'd forgotten that I'd changed the login info on the server. The one big difference between the server and my dev box is that I use FireFix in development, and was using IE on the server. I've just corrected that but I get the same behavior with either browser on the server, never says the ID/password is bad.

So, barring the unforseen, it seems to be sorta working as intended at the moment. Thanks for the help, and see you at Synergy, I've signed up for the Ajax class on Monday.
Bob

"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:7V2X67%23hHHA.5880@dacmail.dataaccess.com...
Bob,

I still have the feeling that your WebApp.exe is not 'running' like in 'functioning normally'. In such a case you might see a WebApp.exe in your tasklist, but it is hung or waits for something to happen. Let me try to explain what is going on:

When the WebApp.exe is started by the WebApp Server, it will start up like a normal VDF program and then wait for events to happen. One of the things the WebApp process needs to do during this startup process, is connecting to the WebApp Server process that started the WebApp.exe. I have the feeling that this is not happening. The reason for this might be that WebApp.exe is held up because of some kind of error, for example, because it cannot open a file.

I've enclosed a package that I use in these kinds of situations. This package installs an extra error object that is based on the cWebAppError object. It will log all errors in a file called "ErrorLog.txt" that will be put in your Programs folder. You can include the package just after your "Use AllWebAppClasses.pkg".

Please test this package first on your development machine. To test it, just put an "Error 123 'whatever'" somewhere in your code. It should show this error in the ErrorLog.txt file after you run the app. Don't forget to remove the error after you tested it.

Please let us know what you find out.

Eddy Kleinjan
Data Access Europe






"Bob Worsley" <bworsley@comcast.net> wrote in message news:aT37kk4hHHA.1652@dacmail.dataaccess.com...
See below.
"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:JlCq0zyhHHA.4972@dacmail.dataaccess.com...
Bob,

I would like to get complete picture of your environment in order to be able to help you out. For example, is all of your application running on the same server, or are for example data files included that come from a different server?
I've got the files for the WebApp on a different server, but moved them to the webapp server just to try. No difference.

The first thing we need to find out (and you probably already did) is whether the WebApp is actually running or not.

If you go to the WebService.wso (using your local http:// ..../WebService.wso), does it present to you the screen with the functions that are available in the Web Service?
No, I get the Web Service Error detailed above

If you get this list of functions, then please click on one of the functions. When you do, you should be able to see an entrries in the 'Event Log' of the WebApp Administrator for your application (Note: Not the Windows Event Log, it's the WebApp Event Log). You should see two lines, one "Session Started" and one "Session Ended" (Assuming that your WebApp has been set to "Log all access to the Web Application" in the properties for your application). If you don't see those, or see other messages, then the chances are your WebApp cannot be started at all.
The Webapp does start, I get to my login screen, and I can see WebApp.exe running in Task Manager. I do get a bunch of errors first though:
Data type error - String used as Number
Session key not known (reload page to recreate session)
And the session record is not created.

If your WebApp cannot be started at all, then this is most probably because of security rights. One of the things that might go wrong here is that the files you are accessing from your application are on a different computer. Other reasons might be that the account under with the "Visual DataFlex 12.0 Web Application Server" Service runs, doesn't have access to your Programs directory.
Moved all files to this server, no difference. I've tried running the service with local system, an administrator account and also with my domain account and get the same results all ways.

If your WebApp runs fine, then try to execute the function "ServiceMetaData" without filling in any of the fields. This should return with a XML message that has the text "Invalid WebObject:" somewhere. When this works, then there is probably nothing wrong with the WebApp itself. In that case you should try to debug the logic that you built in.

Once you have gotten this far, we can take further steps to see where and why things are failing.

Eddy Kleinjan
Data Access Europe

"Bob Worsley" <bworsley@cox.net> wrote in message news:OA4b0XhgHHA.1652@dacmail.dataaccess.com...
I built a small WebApp which works on my development box and tried to move
it to another test box, but when I run it and get to the login screen and
log in, I get the error below. What am I missing? The event log simply
says the child process isn't there.

Bob

220: Webservice soap error: Faultcode: soap:Server Faultstring: Application
error occurred during processing.Technical details for the site
administrator: Message time out. The child process did not process the
message in a timely manner. Please check the Windows event log for further
information about the problem.