Discussion Locked

Browse button within 3rd party applicaton crashes system

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

i've got a really baffling problem raging out of control here at the offices where I am head system administrator. here is the scenario:

we run a program called Fabritraks, a manufacturing database application written in Visual FoxPro, which runs on a central file server. All workstations are mapped to it's installation folder which is shared on the Windows 2003 Domain. A shortcut to the main .EXE is then placed upon each user's desktop for them to access the application. All user's can get into the program and function almost flawlessly except for one small, but very important function.

There is a function within the program that allows us to attach files (any type) to our work order templates. That way, the next time we get an order for a part, we can pull the template up, and the drawing PDFs will be attached to it.

So, to cut to the chase, to add these attachments to the work order templates, you have to hit a '+' button with the program. When about 50% of our users hit this button, their workstation completely locks up and I have to do a hard reboot.

I have spent hours on the phone with Fabritraks tech support, and they are now telling me that this is some sort of an error on my network because the code behind the '+' button is only trying to open up a Open File browse dialog box and it should work just fine. The code behind the button is simple:
-----------------------------------------------
LOCAL xlsfilename

xlsfilename=GETFILE('*', "Locate location of test file")

thisform.text1.Value=xlsfilename
-----------------------------------------------

This is where it gets more technical. The Open File dialog box, since it is being run from one of the problem workstations, is defaulting to the Fabritraks installation folder on the File Server. Their tech support is telling me that the reason the lockup is occurring is because the workstation cannot resolve the name/ip/location of the File Server and thus is locking up indefinitely. My problem with that scenario is that if the workstation couldn't resolve the File Server's location, then how could it be running the application in the first place?

So how is my network setup you may ask? Well, for one, we have two W2K3 Domain Controller's, one main one, and the other replicating. DNS is setup and functioning properly and passing all NETDIAG tests. The DCs are also passing all DCDIAG tests. The workstations are both Static IP and DHCP and we have WINS running too.

There is no rhyme or reason as to what is causing this if it is indeed network related as they are claiming. I have compared the TCP/IP settings on a working system to a non-working system, and there are minor differences, but nothing that illustrates a pattern or cause. The netbios cache tables are different on each system, would that be something to look into?

Please help. I have exhausted all of my ideas and I can usually resolve any IT related issue. This one has got me stumped. Any and all ideas greatly appreciated as this problem is going to cause me to have to postpone my birthday vacation if I don't get it resolved before Friday :(

Pulling my hair out in Austin!!

2 replies

by williamsanders

1. turn opportunistic locking OFF on the server.

2. Is the folder on the server being access via a UNC or a drive letter thats been mapped? Take a look at the icon on a user workstation, lemme know what's going on.

HTH - Regards [Bill]

by deepsand

Suggest that you try the "Questions" forum.
The "Discussion" forum is for matters of general discussion, not specific problems in search of a solution.

Post problems such as this to the "Question" forum, rather than the "Discussion" forum. There are those who specifically seek out problems in need of a solution, and that's where they go to look for such.

Additionally there are the benefits that:

1) The "Questions" forum provides for your feedback, by way of your being able to mark "helpful" responses as such. This does not necessarily mean that a given response contained the complete solution to your problem, but only that it served to guide you toward it. This is intended to serve as an aid to those who may in the future have a problem similar to yours, so that they might have a ready source of reference available, thereby perhaps obviating the need for them to repeat questions previously asked and answered.

2) The revised TR makes it quite difficult to find both "Discussions" and "Questions" that have not had a fairly recent post, owing to some functions comingling them in the listings. By keeping each type in their respective forums, it is easier for all to find what they are looking for.

This discussion is closed to new replies.