DSXchange

Posted: **Thu Apr 23, 2015 10:51 am**

Hi Experts,

I have done a fresh Installation of IIS 9.1.2 on AIX server. Installation went well without any errors.
I can log in to Webconsole, OPS console and clients with dsadm.

But when I try to save a job in designer I get below error.
In Administrator client the project path is not displayed below when i click on a project and also ADD, Properties tabs do not work [Nothing happens after we click these tabs].

Please can you Identify what user configuration I would have missed or something else !! ??

Error" Error on SET.FILE.MAP RT_BP3 NONE FORCE command (Failed to set file's NLS map. ) "

Note: Given full 777 permisions to the Projects folder path.

Posted: **Thu Apr 23, 2015 4:45 pm**

What are the permissions to the RT_BP3 directory? When you use the SET.FILE.MAP command, it has to write a hidden file called .nlsmap into the directory. If you don't have write permission to the directory, then the command will fail.

Posted: **Fri Apr 24, 2015 3:32 am**

I have given chmod -R 777 <ProjectName> in the Projects directory. But still the issue.

Also I get below error many times. Even when restarting the IIS components, I get this error:
"du: 0653-175 Cannot find the current directory."

More details:
{pbhashdlpw001}/home/xmeta$ du
16 .
{pbhashdlpw001}/home/xmeta$ cd /IIS
{pbhashdlpw001}/IIS$ du
du: 0653-175 Cannot find the current directory.
{pbhashdlpw001}/IIS$ cd /IIS/Appl
{pbhashdlpw001}/IIS/Appl$ du
du: 0653-175 Cannot find the current directory.

Posted: **Fri Apr 24, 2015 5:27 am**

We were getting error "du: 0653-175 Cannot find the current directory." when stopping and starting the engine as root. Support said to stop and start it using the dsadm ID according to the doc, and that error went away.

Posted: **Fri Apr 24, 2015 5:45 am**

Ok, But I use 'dsadm' for engine and root for other apps while restarting.

Posted: **Wed May 06, 2015 5:34 am**

Hi,

Issue is now fixed. Giving full permisions to the install directories as suggested above were not enough.
We unmounted the file system where the installation was done. then gave full 777 permissions for the folder underneath that mount point.

Now it works fine. To be on the safer side I uninstalled IIS for this change and did re-install.