Area = not found

I am working on a wft and when testing I am getting the following error and am having difficulty finding where to look to eliminate the error. Suggestions?

Thank you.

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment
SingleServerFileListDeploy2608673.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
***ERROR - Starting deployment.
Reason from server: DEPLOY_CONFIG_FILE
Details : Area = not found.

Find more posts tagged with

Comments

BlueWhale

Your deployment config file is looking for "area" parameter from the command line from which the deployment got invoked.

Example: ODHOME\bin\iwodcmd start Common/WebAssets.xml -k source_branch=/default/main/US/Web/LogoLibrary/en -k source_area=WORKAREA/Publishers -k replication_farm=QA3_Web1-k filelistname=IWHOME\local\logs\fileassetslist2145339.txt

The above bolded area parameters in the command will be used in the deployment config file.

Hope this helps.

nipper

Post your XML, there is a variable in the OD config file that needs to be set to the current workarea.

You need to figure out what that variable is and then supply it with the -k switch.

SethHickel

Thanks - attached.

I'm following what you are saying - looked for that - just can't seem to find the error.

BlueWhale

Post your $iwhome/custom/LowesCom/workflowDeploy.ipl file too. This ipl is invoking the deployment command. This command is missing the -k flag for the area.

SethHickel

Attached - thanks

SethHickel

This may help too

nipper

The code looks correct, you are not missing any variables.

Can you see if there is a log file:

$iwhome\\custom\\LowesCom\\lowescom_deploylog.txt

BlueWhale

hmmm..the ipl looks good to me.

Can you post your $iwhome\\custom\\LowesCom\\lowescom_deploylog.txt file which shows the logs for this deployment that failed.

Also, append //IWSERVER to the $area_path in the deployment config xml. So, it should be like:

[HTML]
sourceFilesystem area="//IWSERVER$area_path^" filelist="$filelist^"

[/HTML]

rodigz

you don't have to have seperate source branch and workarea.
You can get the info in one variable.

It is better to have a log file. Output the command you are running.
See if you are getting all the necessary variable. Better to test it running through the command line.
/opt/iw-home/OpenDeployNG/bin/iwodcmd start test/dev_filelist -k area=/default/main/To/2009/WORKA
REA/los_angeles -k filelist=/tmp/filelist/dev_filelist_712380.txt -inst 712378 -sim

SethHickel

The following three entries are from my log file. They are the only reference to my deployments. The last one is from a run this morning.

### Start Task 2608673

deploy command=D:\Interwoven\OpenDeployNG/bin/iwodcmd start LowesComSingleServerFileListDeploy -inst lowescom2608673 -k area_path="Y:\default\main\lowescom\content\WORKAREA\site_content" -k filelist="D:\Interwoven\TeamSite\custom\temp\file_list_for_task2608673.txt" -V verbose 2>&1

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment LowesComSingleServerFileListDeploylowescom2608673.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
***ERROR - Starting deployment.
Reason from server: DEPLOY_CONFIG_FILE
Details : Area = not found.

### End Task 2608673

### Start Task 2610126

deploy command=D:\Interwoven\OpenDeployNG/bin/iwodcmd start LowesComSingleServerFileListDeploy -inst lowescom2610126 -k area_path="Y:\default\main\lowescom\content\WORKAREA\site_content" -k filelist="D:\Interwoven\TeamSite\custom\temp\file_list_for_task2610126.txt" -V verbose 2>&1

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment LowesComSingleServerFileListDeploylowescom2610126.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
***ERROR - Starting deployment.
Reason from server: DEPLOY_CONFIG_FILE
Details : Area = not found.

### End Task 2610126

From this morning:

### Start Task 2620181

deploy command=D:\Interwoven\OpenDeployNG/bin/iwodcmd start LowesComSingleServerFileListDeploy -inst lowescom2620181 -k area_path="Y:\default\main\lowescom\content\WORKAREA\site_content" -k filelist="D:\Interwoven\TeamSite\custom\temp\file_list_for_task2620181.txt" -V verbose 2>&1

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment LowesComSingleServerFileListDeploylowescom2620181.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
***ERROR - Starting deployment.
Reason from server: DEPLOY_CONFIG_FILE
Details : Area = not found.

### End Task 2620181

rodigz

Please make sure area is valid/exist area_path="Y:\default\main\lowescom\content\WORKAREA\site_con tent"

There's a space in the "con tent". Or try to use other workarea.

nipper

Please make sure area is valid/exist area_path="Y:\default\main\lowescom\content\WORKAREA\site_con tent"

There's a space in the "con tent". Or try to use other workarea.

That is *probably* a feature of the forum software, it happens often.

Seth, copy/paste the command into a DOS command line and see if it works.

If it does, then you need to see if the user the external task is running as has permission to read the folder.

SethHickel

Well - interesting - from a command line it worked. Still fails from the GUI.

Ok - ran the following
iwodcmd start LowesComSingleServerFileListDeploy -inst lowescom2624300 -k area_path="Y:\default\main\lowescom\content\WORKAREA\site_content" -k filelist="D:\Interwoven\TeamSite\custom\temp\file_list_for_task2624300.txt" -V verbose 2>&1

Got the following

Locating OpenDeploy service.
Got OpenDeploy service
>>>>>-- Start deployment LowesComSingleServerFileListDeploylowescom2624300.
iwodstart running in default synchronous mode.
Need to wait for deployment to complete.
>>>>>-- Deployment LowesComSingleServerFileListDeploylowescom2624300 finished:
ID: m2524 Start time: Fri Oct 16 17:08:38 EDT 2009
Status: Completed
Status details:
All targets got completed status

nipper

I assume this is a yes, but did you log on to the server with your normal Windows login ?

nipper

Well - interesting - from a command line it worked. Still fails from the GUI.

When you say from the GUI you mean from a workflow and not the OpenDeploy GUI....

SethHickel

Yes - I did log onto the server with my normal windows login ID and password - same as I use for the ContentCenter GUI. And yes when I say GUI I am talking about from a workflow that I kick off from the ContentCenter GUI. (Sorry for the lack of clarification)

nipper

Yes - I did log onto the server with my normal windows login ID and password - same as I use for the ContentCenter GUI. And yes when I say GUI I am talking about from a workflow that I kick off from the ContentCenter GUI. (Sorry for the lack of clarification)

No I meant OpenDeploy GUI, you are NOT using that.

Can you dump your environment variables in the perl script ? Everything you post looks correct.

If you have a chance you can email stuff to me and I can try to load it on a VM.

SethHickel

Sorry - no - actually I have not run this deployment from OD - I could set up a file list and do so. I have been instantiating the workflow from TeamSite ContentCenter.

I thought I had posted the variable values in the perl script - let me make sure I have what you are asking for and post.

Thank you.

(Not spent much time today on this - nice big fat Monday morning production issue!! :-) )

SethHickel

Applicable files ...

SethHickel

A note: I do not want to submit this to TeamSite staging - looking to see if somewhere in this partially borrowed code I am still adding a submit and therefore causing the AREA to be incorrect.

This looks like a dual post but I am actually trying to work this out with both a WFT and a WFM

ErrorEclipsePreview.png

ErrorBIRTViewer.png

SethHickel

Fixed. We basically re-wrote the ipl file.

Thanks for all the help.