Welcome Serena Central users! CLICK HERE
The migration of the Serena Central community is currently underway. Be sure to read THIS MESSAGE to get your new login set up to access your account.
Highlighted
tech-man83 Absent Member.
Absent Member.
1975 views

LDAP Update Error

The periodic ldap update (and if you initiate it manually) fails. I noted the following in the logs.


[13:02:31] Failed running query:
{call spUpdateLDAPGroupForUser(?, ?, ?)}
SQLError:
ExecuteSQL returned status: -1
State: 42000
Native: 468
Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.
[13:08:02] Failed running query:
{call spUpdateLDAPGroupForUser(?, ?, ?)}
SQLError:
ExecuteSQL returned status: -1
State: 42000
Native: 468
Error: [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot resolve the collation conflict between "Latin1_General_CI_AS" and "SQL_Latin1_General_CP1_CI_AS" in the equal to operation.


Is this a bug somewhere or a misconfiguration of the database? Windows Server 2k8 R2, MS SQL Express Database, ZMM 2.7.0.
Tags (2)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: LDAP Update Error

tech-man83,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

Has your problem been resolved? If not, you might try one of the following options:

- Visit http://support.novell.com and search the knowledgebase and/or check all
the other self support options and support programs available.
- You could also try posting your message again. Make sure it is posted in the
correct newsgroup. (http://forums.novell.com)

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.novell.com/faq.php

If this is a reply to a duplicate posting, please ignore and accept our apologies
and rest assured we will issue a stern reprimand to our posting bot.

Good luck!

Your Novell Product Support Forums Team
http://forums.novell.com/

0 Likes
tech-man83 Absent Member.
Absent Member.

Re: LDAP Update Error

After opening an SR, it was concluded we could either wait for the update that fixes the issue or reinstall SQL server with the matching collation: SQL_Latin1_General_CP1_CI_AS

LDAP was a vital requirement going forwards for us, so we opted the more complicated path of re-installing sql. Backup/Restore/Fix logins etc were required, so some SQL knowledge (or Google Fu) required.
0 Likes
mmoshcs Super Contributor.
Super Contributor.

Re: LDAP Update Error

tech-man83;2260699 wrote:
After opening an SR, it was concluded we could either wait for the update that fixes the issue or reinstall SQL server with the matching collation: SQL_Latin1_General_CP1_CI_AS

LDAP was a vital requirement going forwards for us, so we opted the more complicated path of re-installing sql. Backup/Restore/Fix logins etc were required, so some SQL knowledge (or Google Fu) required.


For those of us very weak on MS SQL can someone give a basic guide, the information I'm getting from google is for various versions and gnerally all over the place?
0 Likes
tech-man83 Absent Member.
Absent Member.

Re: LDAP Update Error

Apologies for the Delay in reply, My MSSQL specific knowledge is also quite limited. The rest of our Zenworks stack is all hosted on linux! As such I don't really have a specific set of instructions that would be friendly enough that I could say works without issues. Supports recommendation was to wait for the version after 2.7.2 (as 2.7.2 doesn't contain the fix).

The basic steps were for us:

1. Took a snapshot of the VM
2. Stopped IIS
3. Backed up the Database
4. Uninstalled SQL server express.
5. Re-installed SQL Server express, changing the collation during install to: SQL_Latin1_General_CP1_CI_AS
6. Restored the database
7. Added the Zenworks User back with DB_Owner permissions on the database
8. Fixed the Orphaned user (How to fix orphaned SQL Server users)
9. Started IIS
10. Checked everything was happy.
11. Removed the Snapshot

Now the above may not be detailed enough, but it will be a good start. Hope that helps.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.