AppData environment variable doesn't work on Server 2003

[hawkun]

Hi,

I'm using the AppData environment variable in the Source path (<appdata>), but it doesn't seem to expand correctly on Windows Server 2003. It works just fine on Server 2008, Windows 7 etc.

From the log:

[TGRMN Software]

Hi, that's strange, it works on my 2003... can you try running a custom script before ViceVersa (profile settings -> advanced settings) and check the appdata value?

thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

[hawkun]

I solved the problem. It turned out I ran the VVEngine service as one account (local administrator), and was logged on to the server with another (domain administrator). I was handling the scheduled profiles as domain administrator so the settings XML file probably got stored in another "<appdata>\VVEngine" folder than expected.

When VVEngine runs the profile it looks for the non existing source folder "<appdata>\VVEngine". Not finding the source folder ("VVEngine") seems to make <appdata> not expand to the correct value (it seems to be ""), resulting in ViceVersa to generate a somewhat misleading error message (syntax error).

I changed the VVEngine service to run as domain administrator and now it works like a charm.

[hawkun]

Hm.. not working so well after all.

Because the folder where VVEngine stores application data is %user% dependent I have to use <appdata> in the path in my ViceVersa profile. But to make <appdata> work I have to be logged in to the machine, even if VVEngine runs as a service and don't need anyone to be logged in.

The VVEngine service runs as "domain administrator", but if I'm not logged in as "domain administrator" at the machine ViceVersa seems to expand <appdata> to "" instead of the correct "domain administrator" appdata folder.

Possible solution 1: You correct this in an VVEngine/ViceVersa update.

Possible solution 2: You give me instructions how to change the path to the folder where VVEngine stores its application data. Then I can select a folder that is not %user% dependent, and the whole problem will be gone .

Thanks!