Script porting issues

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (1 revision)
m (1 revision)
 
(One intermediate revision not shown)
Line 1: Line 1:
-
Scripts which use windows paths, for e.g- c:\asdf\sdf.txt, to pick up information() or to write information(write document step) will fail. This is due to the fact the directory structure in VOS is very different from that in windows. And also due to the fact that we dont allow data to be written or picked up from anywhere in the box. There is a specific folder for these operations and its called the Customer folder. So all the hardcoded or passed windows paths will need to be changed in the scripts.
+
== Script porting issues ==
-
This information will also be put in the release notes.
+
{| border="1"
 +
|-
 +
! '''Problem Summary'''
 +
| Scripts which use windows paths, for e.g- c:\asdf\sdf.txt, to pick up information() or to write information(write document step) will fail.
 +
|-
 +
! '''Error Message'''
 +
| Security Violation exception or file not found exception in MIVR logs
 +
|-
 +
! '''Possible Cause'''
 +
|  This is due to the fact the directory structure in VOS is very different from that in windows. And also due to the fact that we allow data to be written or picked up only from a particular folder in the server.
 +
|-
 +
! '''Recommended Action'''
 +
|
 +
Performs these actions:
 +
# There is a specific folder for these operations and its called the Customer folder. So all the hardcoded or passed windows paths will need to be changed in the affected scripts.
 +
|-
 +
! '''Release'''
 +
| Release 8.0(1)
 +
|-
 +
! '''Associated CDETS #'''
 +
| None.
 +
|-
 +
|}
 +
 
 +
[[Category:Unified CCX, Release 8.0]]
 +
[[Category:Unified CCX, Release 8.5]]

Latest revision as of 06:07, 3 March 2011

Script porting issues

Problem Summary Scripts which use windows paths, for e.g- c:\asdf\sdf.txt, to pick up information() or to write information(write document step) will fail.
Error Message Security Violation exception or file not found exception in MIVR logs
Possible Cause This is due to the fact the directory structure in VOS is very different from that in windows. And also due to the fact that we allow data to be written or picked up only from a particular folder in the server.
Recommended Action

Performs these actions:

  1. There is a specific folder for these operations and its called the Customer folder. So all the hardcoded or passed windows paths will need to be changed in the affected scripts.
Release Release 8.0(1)
Associated CDETS # None.

Rating: 5.0/5 (1 vote cast)

Personal tools