Hi all,
I'm testing out Tessitura Sync to see if we can move to it (we are still using IMPDEPL), however I'm running into some issues which prevent us from using it:
1. It's an unsigned app, so our UAC settings always asks if I want to run it. Our UAC settings are enterprise-controlled so there's no way around that;
2. It usually takes nearly two minutes to start after clicking "Yes" when Windows 7 warns me that it's unsigned and do I still want to run it. For about 75% of that time, the screen is covered with the shaded window (probably from the UAC message) and I can't click on anything (the Tessitura Reporting tool also does this);
3. When it finally does run, it always comes up and says the "From path does not exist or is not accessible". The From path does exist, and I get the error regardless if I use the drive letter or UNC path;
4. If I run Sync from my local drive, it launches immediately but I still get the same error as described in #3.
Does this app need special permissions to run correctly from a network drive, and does anyone have any idea why it would not be able to find the from path?
Thanks!
Kevin.
Ditto on the UAC issue, but it sounds like the rest of your problems are configuration issues. The long start time could be waiting on a timeout from a network resource.
I use a couple different configurations of TessituraSync for standard users as well as to automate installation and updates on managed machines. Maybe if we took a look at your .config file we'd be able to find the issue? To my knowledge, it looks for paths in the same context as the current user, so if you can access the "From" path in windows explorer, TessituraSync shouldn't have a problem. (The one caveat is that it only knows a couple of the environment variables like %USERNAME% -- not every var will work as expected.)
Here's my config file. It's pretty straightforward.
<?xml version="1.0"?><configuration> <configSections> <section name="syncSettings" type="Tessitura.Sync.Configuration.SyncSettingsConfiguration, TessituraSync" /> </configSections> <!-- Warning : If deleteOldFiles is set to true, Then all files and folders in the destination folder will be deleted. --> <syncSettings> <!-- Optional from and to path to sync the Tessitura application. --> <application from="I:\Tessitura\_Test\Client\" to="C:\Tessitura\Client (Test)" fileToCompare="imp_version.txt" deleteOldFiles="true" /> <!-- Optional from and to path to sync the PBVM. --> <pbvm from="I:\Tessitura\PBVM" to="C:\Tessitura\PBVM" deleteOldFiles="true" fileToCompare="pbvm12_version.txt" /> <launch executable="C:\Tessitura\Client (Test)\Tessitura.exe" iniFile="I:\Tessitura\_Test\Profiles\%USERNAME%\Tessitura1.ini" /> <!-- Additional Sync Options. The id's need to be unique. --> <additionalSyncOptions> </additionalSyncOptions> </syncSettings> <startup> <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.0" /> </startup></configuration>
Are you sure you're using the most recent version? Mine has a date modified of "10/16/2014" (our Tessi build is 12.1.2). I ask because I tested what would happen if I mangled the "From" property for the application key, and it gave me an error that was like yours except it output the attempted file path in the text of the error.
Like "From path \\blahserv\blah\foo\bar does not exist or is not accessible."
If that doesn't help, the next thing I would try would just be to test the sync application in isolation -- make it move around some files to different parts of your local C:\ drive without even touching the network, just to see if it'll do it. Then you can gradually start branching out from there once you have a baseline.