(Urgent-TeamSite 6.5)Open file in "<"

Hey

My TeamSite version is 6.5.0 Service Pack 1 . It is installed in C drv of Windows 2003 enterprise edition server.
Can somebody tell me why I am unable to create file in the specified location - please go through the attachment.
I have tried all possible combinations of forward slashes and back ward slashes. but still unable to succeed.

The $filename variable holds values like C:/iw-home/custom/wfmanifests/HotelCareer119194363638.mfst

Actually this file will be read by open deploy to find target paths.

Can it be an issue with permissions on the iw-home/custom folder, I have myself created the wfmanifests folder.

Find more posts tagged with

Comments

nipper

It certainly may be a permissions issue on the folder. Open the permissions wide.

Also, simplify the code: just try;

if (open (MANIFEST, ">c:/iw-home/custom/wfmanifest/temp.txt"))

Adam Stoller

Hey

My TeamSite version is 6.5.0 Service Pack 1 . It is installed in C drv of Windows 2003 enterprise edition server.
Can somebody tell me why I am unable to create file in the specified location - please go through the attachment.
I have tried all possible combinations of forward slashes and back ward slashes. but still unable to succeed.

The $filename variable holds values like C:/iw-home/custom/wfmanifests/HotelCareer119194363638.mfst

Actually this file will be read by open deploy to find target paths.

Can it be an issue with permissions on the iw-home/custom folder, I have myself created the wfmanifests folder.

I suggest making, at least, the following change to your code so that you can get better diagnostics:

sub main {
    my $jobid = lc($rootnme) . timelocal(localtime) . int(rand(100));
    (my $areavpath = $dcr_path) =~ s|^.*/default|/default|i;
    $areavpath =~ s|^(.*)/templatedata.*$|$1/WEB-INF|i;

    # Create Manifest for File Deployment
    my $filename = "$iwhome/custom/wfmanifests/$jobid.mfst";
    if (open MANIFEST, ">$filename") {
        chmod 0666, "$filename";
    }
    else {
        die " '$filename' ($!)"; # or dump into a log file
    }
}

Without that - we're just guessing as to what the problem is, and thus guessing even more as to what the solution might be.