It is not the length of the database name. It is not the DEP
settings. I've tried those. Any client machine not running Server
2003, the client resources are created and it accesses the 4D server
just fine.
I'm out of options. Any suggestions?
you need to make sure that the directory to which 4D is trying to
write its application support files (.res and.rex files) - not sure
where on windows server 2003 this will be - has write permission
(probbably simplest to give everyone write access) once you find out
where this is.
Since there IS a permission issue - maybe 4D is trying to create the
application support directory somewhere windows doesnt like - like All
Users, or maybe in the windows directory