Level Extreme platform
Subscription
Corporate profile
Products & Services
Support
Legal
Français
Application configuration incorrect error message
Message
From
17/02/2005 17:44:49
 
General information
Forum:
Visual FoxPro
Category:
Troubleshooting
Miscellaneous
Thread ID:
00985839
Message ID:
00988144
Views:
56
Sergey,

This doesn't seem to be the same problem. In this office we just had nother computer that has been running the program start to get the message. It also is XP Pro. There are other computers that seem to be the same that are still running fine. Just as this one was yesterday. No apparent changes on either computer or on the application. Obviously something changed, but not intentionally.

No new program installed or intentional program or software changes. Is there some new Microsoft XP update that has been causing problems. I think both of these may be set to get automatic updates to Windows.

>Alan,
>
>See if mskb #812696 is relevant to your situation.
>
>>I have a user running an application that is installed on a peer-to-peer network. The application is installed on a computer running Win98. He is running WinXP Pro. He was able to run the appplication just fine up until today. Now he is getting an error message:
>>
>>The Application has failed to start because the application configuration is incorrect. Reinstalling the application may fix the problem.
>>
>>The Application is written in VFP6.
>>
>>There are two other VFP6 applications installed on the same computer and he can run those just fine. Other users on the network are able to run the failing application just fine. His computer is the only one that is running XP, so I was looking to that as being significant. This application has not been rebuilt for some time, and it was running for him early this morning and then stopped with the error for no apparent reason.
>>
>>The XP system has the VFP6 development package as well as the VFP8 development package installed but they have both been installed as they are for several months.
>>
>>I have tried running as a mapped drive and using the full windows naming \\server\share addressing and get the error both ways of reference.
>>
>>Any thoughts would be appreciated.
Previous
Next
Reply
Map
View

Click here to load this message in the networking platform