Question

Can not connect to DOCMAN after upgrading to IFS Cloud 22R1

  • 23 January 2023
  • 3 replies
  • 116 views
S
Rank
Userlevel 2
Badge +6

Hi

We've an issue with setting up DOCMAN file repository with shared option in IFS Cloud 22R1 Remote deployment.

We're upgrading from IFS Applications 10 to IFS Cloud 22R1. Current IFS installation uses a windows file share as the primary DOCMAN repository. We'd like have a similar setup for IFS Cloud as well. But after doing required configuration, we’re still unable to connect to the created repository.

We're getting the following error when attempting to attach a document.

Repository Address Setup

Repository setup

We noticed the below log entries in the Odata provider container when attaching files.
 

However, we've tested the same network share with the same credentials in IFS Connect (File Reader) and it works with no issues. Therefore we can guarantee that the directory, username & the password are correct



Any help is highly appreciated.

Thank you

3 replies

Mathias Dahl
Rank
Userlevel 7
Badge +30

It could be that the password is correct but that it's not correctly stored in IFS. Is it long and/or contain "special" (not letters or numbers) characters? To verify, could you temporarily change it to something short and simple (for example Test1234), just to see if this can be the cause?

/Mathias
S
Rank
Userlevel 2
Badge +6


@Mathias Dahl Thank you for the prompt reply. Password has 11 characters and it contains a special character, (‘@’ ). Password format is as below ‘password@100’. We will try again after changing the password as you’ve suggested


 

Mathias Dahl
Rank
Userlevel 7
Badge +30

Hi Sasanka,

I did a test and the password you mentioned should not be problematic. It's hard to describe this in a way that works as a recommendation but, the longer the passwords, the higher risk is that it's not saved correctly. And the more characters we use that are one of the punctuation characters (!"#$%&'()*+,-./) in the latter part of the password, the higher the risk.

So, short passwords in general is not a problem and if you have long passwords and need one of the separator characters, place them early in the password. As an example, this password should save correctly:

!"#$!"#$!"#$"#$"#$AAAAAAAAAAAAAAAAAAA

But this will not save correctly:

AAAAAAAAAAAAAAAAAAA!"#$!"#$!"#$"#$"#$

Did you try leaving out the domain name before the user name? A customer had problems with that (different ones though).

 

/Mathias

Reply


Terms & ConditionsCookie settings