search for: uniqui

Displaying 7 results from an estimated 7 matches for "uniqui".

Did you mean: unique
2017 May 22
3
attributeID is not known in our schema, not fixing replPropertyMetaData
Hi We migrated Windows 2003 with Exchange to Samba 4.2.14, 4.3.11 (we have few Samba DCs). Exchange is not needed. Joining was OK but replication is not working. Forcing sync with all attributes from the original WIN DC does not work Seems like the most accurate Samba 4.2.14 (used for changing passwords, adding users etc) has DB error: samba-tool dbcheck : ERROR(<type
2007 May 10
1
Softkey config example for Cisco 7941/7961
...tKeyFile" where you can specify an xml file for the softkeys. I couldn't find any examples of this softkey file or the format to this file. Does anyone have a call manager enviroment where they can look at this file and send me an example. Looks like it is typically it is called SK<uniquie-id>.xml -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20070510/a4201e95/attachment.htm
2017 May 26
2
attributeID is not known in our schema, not fixing replPropertyMetaData
...ntains the users. Other sections replicate fine. > > Promoting new DC also does not work. Data (both new and old) are > locked in this single DC 4.2.14. Exporting the database and importing > it in 4.6.3 fix some things but not this one. > > We found that replPropertyMetaData is uniquie for each user, setting > it empty "fix the error' but breaks the user object. Correct, if you delete replPropertyMetaData in any way, you totally break replication. > How to recreate this attribute properly? How to remove all entries > about attributeId 0XB7D8382? It was inher...
2017 May 27
1
attributeID is not known in our schema, not fixing replPropertyMetaData
On Sat, 2017-05-27 at 03:16 +0200, Karan Blas via samba wrote: > > > We found that replPropertyMetaData is uniquie for each user, setting > > > it empty "fix the error' but breaks the user object. > > > > Correct, if you delete replPropertyMetaData in any way, you totally > > break replication. > > > > dbcheck should wipe that part of replPropertyMetaData wit...
2017 May 26
0
attributeID is not known in our schema, not fixing replPropertyMetaData
...ation and the main one that contains the users. Other sections replicate fine. Promoting new DC also does not work. Data (both new and old) are locked in this single DC 4.2.14. Exporting the database and importing it in 4.6.3 fix some things but not this one. We found that replPropertyMetaData is uniquie for each user, setting it empty "fix the error' but breaks the user object. How to recreate this attribute properly? How to remove all entries about attributeId 0XB7D8382? It was inherited from Exchange. > Sent: Monday, May 22, 2017 at 10:10 AM > From: "Karan Blas via samb...
2017 May 27
0
attributeID is not known in our schema, not fixing replPropertyMetaData
> > We found that replPropertyMetaData is uniquie for each user, setting > > it empty "fix the error' but breaks the user object. > > Correct, if you delete replPropertyMetaData in any way, you totally > break replication. > dbcheck should wipe that part of replPropertyMetaData with --fix but it is not implemented....
2010 Jun 09
0
AMI Queue information about incoming call's channel before link
...getting now: 1. Newchannel event for incoming call followed by Newstate and Join. All these events can be identified with uniqueid 001 2. Newchannel event for outgoing channel to queue member followed by Newstate State: Ringing => that's what I need. But this channel (of course) has another uniquied 002. 3. Link. That's the place where channels are get bridged and I can find out which member (by channel) answered the call (002 answered 001 in this example). The problem is that I need to get information about call 001 at stage 2 that is currently possible only at stage 3, when channels g...