OT: URGENT - Need Input

[Richard Chidiak]

Tim

Check this

http://blogs.msdn.com/b/chinmay_palei/a ... entre.aspx

http://scorpionqa.wordpress.com/2010/01 ... windows-7/

http://www.interworks.com/blogs/dsmith/ ... tual-store

You can get rid of it changic UDC (rights) or writing to the registry (much better)

this is what i do when needed

Hth

Richard

Code: Select all  Expand view  RUN

   oReg := TReg32():Create( HKEY_LOCAL_MACHINE, "SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System" )  
   I := 0

   oReg:Get( "EnableVirtualization", @I )
   IF I # 0
      IF ! IsUserAnAdmin()
         MSGSTOP("Cette fonction nécessite des droits ADMINISTRATEUR , droits non détectés ! veuillez désactiver manuellement ")
         oReg:Close()
       ELSE
         oReg:Set( "EnableVirtualization", 0 )
         oReg:Close()
      ENDIF
   ENDIF
   oReg:Close()

 

[James Bott]

Tim,

It is sounding like there was a change to either FWH or xHarbour that is causing the problem. It is going to be hard to track down.

James

[Richard Chidiak]

James

A Ms update can also be the problem

Richard

[TimStone]

Although I have not yet solved the problem on site, I do have it isolated. I brought the consumer's entire database to my system ( which uses ADS 11 instead of their 8 ). I installed it on 3 devices ( desktop, notebook, tablet ). I had the exact same error.

Then, through the process of some experimenting, I found that my Windows 8.1 was not networking machines properly. It seemed to be originally, but all the automatic detection, etc. required some significant adjustments in the configuration. Ultimately the connectivity worked. With that done, the next step was to re-test the software, and suddenly it was working, untouched, on all of the computers.

My client is using WIn 7, but I think it is the same issue. I'll now let their IT guy try to get his side worked out.

Thanks everyone for the helpful ideas.

[Rick Lipkin]

Tim

Just a crazy idea .. I had some new 64 bit Windows 7 machines that my old employer called me about not connecting to Ads 9 .. and blaming it on my software not running on 64 bit .

As it turned out, the machines that caused problems .. we found that the User was not ADMINISTRATOR of their box.

It took me several days to troubleshoot that simple thing .. just never thought to ask that question.

Rick Lipkin

[TimStone]

The problem has been resolved. Although the problem occurs with software built using FWH 13.08 and above, it is not the cause of the problem.

The problem occurs as a result of user rights granted on the server to the various workstations. Some IT people setup various rights and limit what certain users can do.
People who had an Administrator profile were able to connect successfully.
People who had a more limited profile could not get access to the data files
The solution was to include everyone in the Administrator profile. Then the computers gained access and worked immediately.

This problem occurred on two computers using Windows Server 2003, and one using Windows Server 2008.

I will let the IT specialists determine which rights are being denied to users in the lesser groups. I now have everyone working at 100 % !

Tim

[James Bott]

Yea!