Server "Not Responding" error

[newtofoxpro]

I have 4 Client + 1 Server setup installed with myapp.exe build on fpw2.6a. Problem is Client machine stuck-up/hang for 25-30 sec.approx. & continues normally. if I double click on myapp.exe's title, the error message appears "Not responding" and disappear after 25-30 sec.approx. it happens many times. I have installed myapp.exe on client machine & use only dbf from server. The server drive mapped as Z: When the client stuck-up immediatly I run CMD.exe & run the windows command < DIR z: > all files listed on server But still myapp.exe stuck-ups.

Thank you in advance
Regards.

 

[DSummZZZ]

The first thing that comes to mind is maybe an anti-virus app is scanning your .DBF when it gets opened?


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[newtofoxpro]

Thanks, but anti-virus is not installed at my server as well as client.

 

[newtofoxpro]

One more thing, when myapp.exe stuck-up/hang, immediatly I switch to already open \fpw26\foxprow.exe by <ALT+TAB> and browse the same DBF, it browsing normally. Even I issue the command <close data> & <USE same.DBF> again it browsing normally. immdiatly I switch by <ALT+TAB> to myapp.exe it still stuck-up.

I have experienced the stuck-up problem is not for specific module/.fxp it stuck-up anywhere.

As above stated, the same .dbf use by myapp.exe & foxprow.exe, when myapp.exe stuck-up, at the same time foxprow.exe do not.

But, when I run myapp.exe (as 1st instance) & again myapp.exe (as 2nd instance) when the 1st instance stuk-up switch by <ALT+TAB> for 2nd instance also stuck-up.

my config.fpw is as under

MEMLIMIT=60,4096,16384
REFRESH=0,0
MVCOUNT=2048
SYSMENU=OFF
RESOURCE=OFF
TITLE=myapplication
EDITWORK=C:\WINDOWS\TEMP
PROGWORK=C:\WINDOWS\TEMP
SORTWORK=C:\WINDOWS\TEMP
TMPFILES=C:\WINDOWS\TEMP

Please help me. many thanks in advance.

 

[NasibKalsi]

NewToFoxPro:

For testing purposes: Try bringing the databse to one of the four machine, and test it there. Does it still get stuck(up) ?

Also if your Station OS is Win95/Win98 and server is Win2000+, this behaviour may exist. I had similar situation with Fox 2.6a and upgraded all stations to Win2K/XP and resolved the problem.

Another possibility may be you have many files(2000+) in the same directory.

Another possibilty is cables are straight colors - this you can check. It should be (Cat5 and Cat5e)
Pair 1(Green) to 1, 2
Pair 2(Orange) to 3, 6 * Very Important
Pair 3(Blue) to 4, 5
Pair 4(Brown) to 7, 8

If Pair 1 is Orange then Pair 2 should be Green.
Both ends should be the same colors.

 

[DSummZZZ]

What sort of processing are you doing when it gets stuck? Is the app trying add a record? Run a query?
Can you step through the code and see exactly what command is causing it to hang?


-Dave Summers-

Even more Fox stuff at:

http://www.davesummers.net/foxprolinks.htm

 

[cricket]

Check your disk space.
You can also have the networking tab open on Task Manager to see your network traffic.

 

[newtofoxpro]

Many Many thanks,

1) Calling Database from Local HDD/Machine myapp.exe never stuck-up.
2) WinXp-SP-2 installed at all Machines i.e. Server & all Station/Client
3) The files are below 2000 in the same directory
4) Cable colors which I have to check.
5) Stuck-up when running query
6) There is no disk space problem.
7) Network traffic I have to check.

Thanks again
Regards.

 

[newtofoxpro]

Cable colors are setup as below Cat5

1)White Orange
2)Orange
3)White Green
4)White Blue
5)Blue
6)Green
7)White Brown

About Network traffic, I disconnected all stations by removing network cable and Server & only one station tried even myapp.exe is quit from Server and tested from one station only still stuck-up

Thank you
Regards.

 

[NasibKalsi]

Some other possibilities:

1. Create another Directory on drice c:\FoxTmp
and Set this as your temp directory in the config.fw

2. Check swap file on drive C: also check space available on the c: drive.

3. What is the name of the table/alias - should not be a reserve word.

4. Try creating temp directory on server z:\FoxTmp and set this as the temp directory in config.

5. Try putting most likely hangup process in a small prg and create MyApp.exe.