nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

OpenDeploy hanging trying to synchronize workareas

Grandjean

Hi

We have two TeamSite environments. I've created a deployment in OpenDeploy synchronizing content between two branches. The log shows that the error might be due to special characters (danish æ,ø,å). Is there a way to workaround these files, ex. skip them?

Error in log:
LIB 00015: 2010-08-31 14:33:29 Error locating:[Y:\default\main\ejendomsportal\nykredit\WORKAREA\wa_nykredit\resources\nykredit\dokumenter\Positiv carry og stigende BEI pÃ¥ TIPS.pdf] [2006].
LIB: 2010-08-31 14:33:29 ERROR: Could not write EA to output.

I've also attached the od logfile and the deployment.xml.

TeamSite 7.1
OpenDeploy 7.1
Windows Server 2008

Thank you

Find more posts tagged with

Comments

Bhargav Coca

[QUOTE=Grandjean]Hi

We have two TeamSite environments. I've created a deployment in OpenDeploy synchronizing content between two branches. The log shows that the error might be due to special characters (danish æ,ø,å). Is there a way to workaround these files, ex. skip them?

Error in log:
LIB 00015: 2010-08-31 14:33:29 Error locating:[Y:\default\main\ejendomsportal\nykredit\WORKAREA\wa_nykredit\resources\nykredit\dokumenter\Positiv carry og stigende BEI pÃ¥ TIPS.pdf] [2006].
LIB: 2010-08-31 14:33:29 ERROR: Could not write EA to output.

I've also attached the od logfile and the deployment.xml.

TeamSite 7.1
OpenDeploy 7.1
Windows Server 2008

Thank you

My bad

Grandjean

You missed the attachments.

Attached

Bhargav Coca

Attached

More than special character i am worried about the spaces in your filename.
"Positiv carry og stigende BEI pÃ¥ TIPS.pdf" Did you put everything in quotes before executing the OD? Try running Deployment from commandline with the filename enclosed in double quotes.

Thank You

Grandjean

More than special character i am worried about the spaces in your filename.
"Positiv carry og stigende BEI pÃ¥ TIPS.pdf" Did you put everything in quotes before executing the OD? Try running Deployment from commandline with the filename enclosed in double quotes. Thank You

I simply execute OD by this perl command: $cmd = qx($odhome/iwodcmd start $odclient_cfg -inst $info -k "sourcearea=$sourcearea" -k "targetarea=$targetarea");
where sourcearea = y:/default/main/branch1/WORKAREA/workarea1 and targetarea = y:/default/main/branch2/WORKAREA/workarea2

I don't know how you want me to put in quotes for any files since OD is simply synchronizing workarea1 with workarea2 (due to "dodelete")?
A simple and acceptable solution would also be to simply skip the files with either spaces and/or special characters.

Adam Stoller

The spaces in the filenames, though "bad", should not be a problem for OpenDeploy if it is doing it's own internal comparison deployment - it might be an issue for file list deployments but even there I believe OD can handle it.

The non-ascii characters in the file names could be a problem, though I see no mention of that as a "known issue" in any of the 7.1 OD manuals. You should probably check with Support, provide them a tar or zip file with several such named files included so that they can attempt to reproduce the problem in-house (include files that actually fail for you since it may be one or two specific characters in those file names and not all "odd" characters)

Grandjean

The spaces in the filenames, though "bad", should not be a problem for OpenDeploy...

I know, but try telling that to non-technical users Smiley Happy

We've added a check for both whitespaces and special characters 9 month ago to any new file entry, but there's still alot of files which needs to be changed.

The non-ascii characters in the file names could be a problem, though I see no mention of that as a "known issue" in any of the 7.1 OD manuals. You should probably check with Support, provide them a tar or zip file with several such named files included so that they can attempt to reproduce the problem in-house (include files that actually fail for you since it may be one or two specific characters in those file names and not all "odd" characters)

I've now created a support case. I'll write there response later...