Hi Christof,

Yes, this is an exe com server. My app is based on the west wind example of creating pdf's using vfp. I do believe it is hanging on the report form command. The code looks like:

SYS(2335,1)
REPORT FORM (lcReport) &lcExtraReportClauses NOCONSOLE NODIALOG TO FILE &lcTFile
SYS(2335,0)

Trying this in the past, it always crashed at this part because vfp was trying to display the printing dialog box. With vfp8, I added the NODIALOG clause thinking this would suppress this and the app would run. Like I mentioned, it works great on my xp machine, but I have tried it on server2000 and win2k machines with no luck.

Thanks for you help,
Kevin


>Hi Kevin,
>
>>It works great on my xp machine, but it hangs on my win2k machine.
>
>One effective way I found in debugging this kind of issues is using FILEMON from http://www.sysinternals.com. Search for any entry containing ACCDENIED in the result column. ASP pages by default require the IWAM_ account (or IUSR_ if you changed application protection to low).
>
>>Also, when it hangs, the only way to stop the process is to re-boot. When I try to stop it through task manager, it says it's unable to terminate the process.
>
>That's because the process is running as a different account than you. However, this raises another question...
>
>Is this an EXE COM server? And you are saying, the server is running, but than hangs? In this case, permissions to the server are probably not the problem, rather something in your code. What happens when you instantiate the component from a VFP application on the W2K machine and call the same methods as the ASP page. Do you get an error message? Or does the printer driver try to display a file open dialog?
>
>Having an error dialog is a common way to hang a process on the server. Because these objects run npn-interactive, you won't see the dialog, yet VFP waits. Make sure you enabled unattended server mode SYS(2335).
>
>Also check if both machines have the same version of the VFP runtime (SP1) installed.
>
>--
>Christof