Jump to content

Special Characters in a SQL Password may cause Content Analyst Conflicts


Jason Lester
 Share

Recommended Posts

After experiencing this situation first hand during an installation, I wanted to share my findings with the Ipro Community.

 

Due to how some parts of Content Analytics within Eclipse access and use the SQL password in the environment (whether this is a unique Ipro SQL account or the regular "sa" account), special characters can create conflicts that will stop indexes from building successfully.

 

To avoid running in to these situations we recommend that the SQL password, whether it is randomly or manually generated, does not contain any of the following:

  • slashes ( \ or / )
  • commas ( , )
  • periods ( . )
  • greater-than or less-than ( < or > )
  • quotation marks ( ' or " )
  • colons ( : )
  • semicolons ( ; )
  • vertical bars ( | )
  • question marks ( ? )
  • equal signs ( = )
  • brackets ( [ ] or { } )

Edited by Jason Lester
  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...