OES11sp1

Anyone running messenger on oes11sp1 (64 bit)? I recently upgraded my
test messenger server from sles11sp1/oes11 to sles11sp2/oes11sp1.
Everything seems fine except messenger will not start. Contents of
/var/opt/novell/log/messneger/nmma.err:
NMMA: Agent configuration failure [0xAE06]
NMMA:
NMMA: Cause: DCC: Referral contained an invald address
Suggestions?
Stevo

laurabuckley sounds like they 'said':
>
> Hi Stevo,
>
> In your Messenger startup file, double check the LDAP server entries
> and port numbers. If you are using SSL between Messenger and eDir
> check that the port is 636.
>
> Cheers,
So my response to laurabuckley's comment is...
Thanks much! That was the issue.
Stevo

Similar Messages

  • Anyone successfully migrated an existing DSfW server to an OES11SP1 server using the new migration wizard ?

    See above - I do not want to be the first one.
    W. Prindl

    I had a very bad experience migrating a simple file server from OES2SP3
    32-bit to OES11 (without SP).
    So I am a little bit cautious.
    I want to migrate a single DC DSfW server (OES2SP3 32-bit) in a multi
    server edir tree to a new OES11SP1 server. The only thing which runs in
    addition to DSfW on this server is an iprint server, which shall be
    migrated, too.
    W. Prindl
    hargagan wrote:
    >
    >Hi ,
    >
    >This is just to understand the status as of now :
    >
    >1. Are you able to migrate any DSfW successfully ?
    >
    >1. What is the source you are going to migrate ?
    >
    >2. How many servers are you planning to migrate ?
    >
    >Do you want us to address some specific issues like in documentation
    >etc, for increasing your confidence ?

  • Problem with OES11SP1/SLES11SP2/KANAKA 2.7

    the installation and configuration from Kanaka 2.7 have been done on OES11SP1 and Mac OSx10.8.2
    there was only one problem, but we can resolve it with tid 7010960
    The error message by starting the plug-in-console is:
    "the required user attribute could not be found !
    the user attribute "dsAttrTypeStandard: Realname' is required to use Plug-in-Console. Make sure that you are logged in via the Kanaka plug in"
    i can login with the Kanaka plug in, but don't see the volumes
    i have read the documentation and search in the knowledgbase, but i found nothing
    Thank you for help
    Claude

    Cgreiner,
    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/

  • ZEN7 on oes11sp1?

    In the past I have done zen7 to zen7 migrations from netware to oes2-linux, but I am in need of doing so to oes11sp1. Is that even supported? I do remember seeing recently that support for zen7 was recently extended so I am hoping that includes oes11sp1 support. The latest full installer I am seeing is NOVELL: Downloads - ZENworks 7 Desktop Management on Linux Support Pack 1 Interim Release 4b ISO ZEN7_with_SP1_IR4b_DesktopMgmtLinux.iso from 2010-08-25. I do see a ZENworks 7 Desktop Management on Linux Support Pack 1 Interim Release 4a Hot Patch 7 NOVELL: Downloads - ZENworks 7 Desktop Management on Linux Support Pack 1 Interim Release 4a Hot Patch 7 dated 2011-05-27 that brings oes2sp3 support, but nothing about oes11sp1. Guessing even though it says 4aHP7 it applies to the older 4b?
    Yes, I know migrate to ZCM11, that is in the cards but not for awhile.
    Thanks!

    Originally Posted by kkbass
    In the past I have done zen7 to zen7 migrations from netware to oes2-linux, but I am in need of doing so to oes11sp1. Is that even supported? I do remember seeing recently that support for zen7 was recently extended so I am hoping that includes oes11sp1 support. The latest full installer I am seeing is NOVELL: Downloads - ZENworks 7 Desktop Management on Linux Support Pack 1 Interim Release 4b ISO ZEN7_with_SP1_IR4b_DesktopMgmtLinux.iso from 2010-08-25. I do see a ZENworks 7 Desktop Management on Linux Support Pack 1 Interim Release 4a Hot Patch 7 NOVELL: Downloads - ZENworks 7 Desktop Management on Linux Support Pack 1 Interim Release 4a Hot Patch 7 dated 2011-05-27 that brings oes2sp3 support, but nothing about oes11sp1. Guessing even though it says 4aHP7 it applies to the older 4b?
    Yes, I know migrate to ZCM11, that is in the cards but not for awhile.
    Thanks!
    Not supported...
    Thomas

  • Iprintman oes11sp1 and IPP Error: 0x500

    Hi All,
    We are heavy users of the commandline iprintman util. After upgrading from oes2sp3 to oes11sp1 iprintman can no longer assign drivers to the print object.
    All other options work fine. grantmanager, location, etc.
    But when trying to assign a driver to the print object iprintman is throwing a IPP Error: 0x500
    Error - Operation failed, unknown errorRequest (SERVER_ERROR) - bad status code (0x500)
    IPP Error: 0x500
    Assigning drivers in iManager is working.
    We are running the latest iprint rpms
    novell-iprint-migration-6.5.1.20130430-0.3.3
    novell-iprint-server-6.5.1.20130430-0.3.4
    novell-iprint-iprntman-wrapper-1.0.0-29.49
    novell-iprint-management-6.5.1.20121218-0.2.19
    novell-iprint-iprntman-6.5.1.20130430-0.3.3
    novell-iprint-client-6.5.1.20130430-0.3.1
    log of the /var/opt/novell/log/iprintmgmt/iprintman0.log
    Jul 8, 2013 11:46:20 AM com.novell.service.iPrint.shared.iPrintException setErrorCodesFromIPPError SEVERE: iPrintException: Unexpected Exception:
    Request (SERVER_ERROR) - bad status code (0x500)
    at com.novell.service.iPrint.ipp.IPPAttributeSet.read Attributes(Unknown Source)
    at com.novell.service.iPrint.ipp.IPPIDSRepository.lis tResources(Unknown Source)
    at com.novell.service.iPrint.iprntman.Driver.list(Unk nown Source)
    at com.novell.service.iPrint.iprntman.Printer.validat eNewDriverName(Unknown Source)
    at com.novell.service.iPrint.iprntman.Printer.fillMod ifyDriverAttrs(Unknown Source)
    at com.novell.service.iPrint.iprntman.Printer.handleP aModifyAttrSetUtil(Unknown Source)
    at com.novell.service.iPrint.iprntman.Printer.modify( Unknown Source)
    at com.novell.service.iPrint.cli.CLIprinterHelper.pro cessCommand(Unknown Source)
    at com.novell.service.iPrint.cli.IPrintManCLI.main(Un known Source)
    Jul 8, 2013 11:46:20 AM com.novell.service.iPrint.cli.IPrintManCLI main SEVERE: Unhandled iPrintException.getLibError() : 1280
    Jul 8, 2013 11:46:20 AM com.novell.service.iPrint.cli.IPrintManCLI main SEVERE: iPrintException.getMessage() is : Request (SERVER_ERROR) - bad status code (0x500)
    IPP Error: 0x500
    and the /var/log/apache2/error_log
    [Mon Jul 08 11:46:20 2013] [error] IdsRequest : Request to IDS failed with 1349320722
    [Mon Jul 08 11:46:20 2013] [warn] IPP Operation error=SRVR_ERR_INTERNAL_ERR, operation=401E
    Any idea's ?

    Originally Posted by spcox
    Hi All,
    We are heavy users of the commandline iprintman util. After upgrading from oes2sp3 to oes11sp1 iprintman can no longer assign drivers to the print object.
    All other options work fine. grantmanager, location, etc.
    But when trying to assign a driver to the print object iprintman is throwing a IPP Error: 0x500
    Error - Operation failed, unknown errorRequest (SERVER_ERROR) - bad status code (0x500)
    IPP Error: 0x500
    Assigning drivers in iManager is working.
    We are running the latest iprint rpms
    novell-iprint-migration-6.5.1.20130430-0.3.3
    novell-iprint-server-6.5.1.20130430-0.3.4
    novell-iprint-iprntman-wrapper-1.0.0-29.49
    novell-iprint-management-6.5.1.20121218-0.2.19
    novell-iprint-iprntman-6.5.1.20130430-0.3.3
    novell-iprint-client-6.5.1.20130430-0.3.1
    log of the /var/opt/novell/log/iprintmgmt/iprintman0.log
    Jul 8, 2013 11:46:20 AM com.novell.service.iPrint.shared.iPrintException setErrorCodesFromIPPError SEVERE: iPrintException: Unexpected Exception:
    Request (SERVER_ERROR) - bad status code (0x500)
    at com.novell.service.iPrint.ipp.IPPAttributeSet.read Attributes(Unknown Source)
    at com.novell.service.iPrint.ipp.IPPIDSRepository.lis tResources(Unknown Source)
    at com.novell.service.iPrint.iprntman.Driver.list(Unk nown Source)
    at com.novell.service.iPrint.iprntman.Printer.validat eNewDriverName(Unknown Source)
    at com.novell.service.iPrint.iprntman.Printer.fillMod ifyDriverAttrs(Unknown Source)
    at com.novell.service.iPrint.iprntman.Printer.handleP aModifyAttrSetUtil(Unknown Source)
    at com.novell.service.iPrint.iprntman.Printer.modify( Unknown Source)
    at com.novell.service.iPrint.cli.CLIprinterHelper.pro cessCommand(Unknown Source)
    at com.novell.service.iPrint.cli.IPrintManCLI.main(Un known Source)
    Jul 8, 2013 11:46:20 AM com.novell.service.iPrint.cli.IPrintManCLI main SEVERE: Unhandled iPrintException.getLibError() : 1280
    Jul 8, 2013 11:46:20 AM com.novell.service.iPrint.cli.IPrintManCLI main SEVERE: iPrintException.getMessage() is : Request (SERVER_ERROR) - bad status code (0x500)
    IPP Error: 0x500
    and the /var/log/apache2/error_log
    [Mon Jul 08 11:46:20 2013] [error] IdsRequest : Request to IDS failed with 1349320722
    [Mon Jul 08 11:46:20 2013] [warn] IPP Operation error=SRVR_ERR_INTERNAL_ERR, operation=401E
    Any idea's ?
    Just for archive reasons ;)
    The defect associated to this SR has been updated with the following patch(es):
    July 2013 Scheduled Maintenance for OES11SP1 (Open Enterprise Server 11.1 x86-64)
    NOVELL: Downloads - July 2013 Scheduled Maintenance for OES11SP1 7889

  • DSfW Installation Simplified in OES11SP1

    Hi,
    We have done major changes in OES11SP1 to improve DSfW installation experience. Please check the following link to know more.
    DSfW Installation Simplified in OES11SP1
    Further, let us know your experience with DSfW installation and areas that can be further improved.

    Grohin,
    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/

  • Update problems sles11sp1/oes11 to sles11sp2/oes11sp1

    I setup a test server with sles11sp1 and oes11 (as I have servers from 2 years ago that I want to update to the same version as the main tree server which is sles11sp2 and oes11sp1.
    Did all the online updates.
    Then booted from the oes11-sp1-addon_with_sles11-sp2-x86_64-DVD.iso and chose installation > update on existing system
    Checked off "include addon...." (maybe shouldn't have done that since it was an all in one dvd?
    No to skip network setup
    Select for update screen showed sles
    Previously used repositories showed all the old repositories
    Addon product install showed media as cd for OES
    Installation settings - no errors there
    Started update
    Got errors for the following updates (a lot). It couldn't download them from the repository. I tried "retry and then chose skip".
    vim-data
    python-base
    xfsprogs
    utillinux
    taglib
    lima1-ca-mgm
    libtiff3
    libldapcpp1
    libjack0
    libboost-regex1_36_0
    mesa
    makedumpfile
    libebl1
    lima1-ca-mgm-perl
    mesa-32bit
    mono-core
    mozilla-xulrunner192
    mozilla-firefox-translations....
    parted-32bit
    yast2-pkg-bindings
    suseregister
    pulseaudio-module-x11
    pulseaudio-esound-compt
    pulseaudio-utils
    sax2-gui
    libgstinterfaces-0_10-0
    gnome-power-manager...
    mozilla-xulrunner192-gnome
    evolution-data-server
    yast2-storage....
    yast2-update
    Restarted server -- boot from hard disk selected
    Took a while to come up
    Desktop doesn't look right
    Yast errors when going into Software > repositories, updates, etc. -- doesn't work
    I haven't used zypper before, but I did try it.
    zypper up (saw 20 updates but got the same filed to provide package.... errors)
    Help. ;-)
    Thanks.
    Patty

    Sorry. There were a few scratches in the dvd I used (from last year). I made a new one and then ran zypper install yast* and it worked. (When I tried that with the other dvd I got the same errors.) Now yast works so I am doing the online updates. If you look at the list of things that didn't install above, is there anything in that list that I need to run the zypper install command with? Or will the online updates catch them all above?

  • OES2SP3 to OES11SP1 nss volumes on iscsi target, hints?

    Dear Colleagues,
    I'm looking for a best migration scenario for the following assumtions:
    One of SLES10SP3/OES2SP3 servers in my tree has file services and kanaka on it. Its nss volumes are located on iscsi targets attached from a Qnap storage. I'm migrating this server to a new hardware and SLES11/OES11SP1 and would like to transfer/switch volumes the easiest possible way. There is +/- 8TB of data to copy and I'm looking for a way around copynig it. Is it possible to perform the migration to newest SLES/OES on a different hardware and just re-attach iscsi target containing nss volumes, so all would stay consistent in the tree?
    Please advise...

    [QUOTE=mrosen;2266934]Hi.
    On 06.06.2013 12:06, mpytel wrote:
    > Is it possible to perform the migration to newest
    > SLES/OES on a different hardware and just re-attach iscsi target
    > containing nss volumes, so all would stay consistent in the tree?
    Absolutely! You do a regular transfer ID migration, *without* copying
    the NSS data that is on the iSCSI device. After the migration, bring up
    the new server, attach to iSCSI, go into NSSMU and activate/mount the
    partition once, and you're all set.
    Dear Massimo,
    I just finished TransferID migration and successfully re-attached iscsi targets containing NSS to the new server.
    Is there an additional step I should execute to 're-read' volumes/pools contents so they appear on the new server?
    M

  • OES2SP3 to OES11SP1 Sanity Check

    I have an OES2SP3 (SLES10SP4) server that I want to move to OES11SP1 (SLES11SP2). The tree is stable, but I am having some issues with the OES2SP3 server that I don't want to spend the time troubleshooting. My Master replica and all services is on a NW65 server and I have the luxury of being able to wipe the OES2 server. The OES2 server only does some file backups via scripts to an internal RAID and holds a RW replica. Looking for a sanity check on my process...
    1. copy scripts from server to backup
    2. remove eDir from server using nds-uninstall
    (the OES doc says that ndsconfig rm is not supported in OES2SP3)
    3. wait for replica ring to be stable - monitor via dsrepair on NW65 server
    4. remove any references to the OES2 server via ConsoleOne
    5. wait for replica ring to be stable - monitor via dsrepair on NW65 server
    6. fresh install of SLES11SP2 and OES11SP1 (eDir only) onto server
    7. add other OES11 services to server
    TIA
    -L

    Originally Posted by LarryResch
    I have an OES2SP3 (SLES10SP4) server that I want to move to OES11SP1 (SLES11SP2). The tree is stable, but I am having some issues with the OES2SP3 server that I don't want to spend the time troubleshooting. My Master replica and all services is on a NW65 server and I have the luxury of being able to wipe the OES2 server. The OES2 server only does some file backups via scripts to an internal RAID and holds a RW replica. Looking for a sanity check on my process...
    1. copy scripts from server to backup
    2. remove eDir from server using nds-uninstall
    (the OES doc says that ndsconfig rm is not supported in OES2SP3)
    3. wait for replica ring to be stable - monitor via dsrepair on NW65 server
    4. remove any references to the OES2 server via ConsoleOne
    5. wait for replica ring to be stable - monitor via dsrepair on NW65 server
    6. fresh install of SLES11SP2 and OES11SP1 (eDir only) onto server
    7. add other OES11 services to server
    TIA
    -L
    Hi Larry,
    If this is a regular fileserver (not housing iFolder and such special services)... your steps seem to cover the bases.
    As an extra preparation step, if the OES server has it's own eDir replica, I'd remove it at least an hour or so before moving on to removing the OES server from the tree. Also running a quick eDir health check after having done so and before moving on to remove the server is a good routine.
    Out of curiosity, do you have a link to the docs specifying 'ndsconfig rm' is unsupported? Have not run into issues with it but also had not seen that reference in the docs (not that I read them daily :P ).
    If you have NSS volumes, you can relink them to the new server using the update NDS option within nssmu. Do note that you will also have to relink object properties to the volumes (like the user home directories).
    Your tree CA configuration is also still valid (and not housed on the OES2 server)?
    Cheers,
    Willem

  • OES11sp1 CIFS Login Failed -nwLoginError is -1660, cifslogin err 0

    Hello,
    I recently set up an existing OES11sp1 server with CIFS.
    When attempting to log in the /var/log/cifs/cifs.log shows:
    Jan 21 11:17:15 lyfs01 CIFS: EVENT: ENTRY: ********** CIFS server
    started ************
    Jan 21 11:17:15 lyfs01 CIFS[26548]: WARNING: ENTRY: Auditing interface
    not initialized.
    Jan 21 11:17:15 lyfs01 CIFS[26548]: WARNING: RPC: requestNumber:
    fadebad1 events: 3ff domainpath /tmp/.ncp2cifs
    Jan 21 11:17:15 lyfs01 CIFS[26548]: ERROR: CODIR: Trustee file handle
    is not setup for volume 1
    Jan 21 11:17:16 lyfs01 CIFS[26548]: WARNING: ENTRY: Interface lo is
    skipped from populating for name resolution
    Jan 21 11:17:16 lyfs01 CIFS[26548]: WARNING: ENTRY: Interface lo is
    skipped from populating for name resolution
    Jan 21 11:17:16 lyfs01 CIFS[26548]: WARNING: ENTRY: Interface lo is
    skipped from populating for name resolution
    Jan 21 11:17:16 lyfs01 CIFS[26548]: EVENT: ENTRY: CIFS context list
    initialized
    Jan 21 11:20:36 lyfs01 CIFS[26548]: WARNING: AUTH: Authentication
    failed due to password mismatch for user , Err :-1660
    Jan 21 11:20:36 lyfs01 CIFS[26548]: WARNING: CODIR: SESNotLoggedIn:
    Failed to authenticate user: Scott from 192.168.1.121, nwErr: -1660,
    cifsErr:
    0
    I've changed my password through iManager -> Passwords -> Set Universal
    Password, which made no difference.
    I've also tried another user without success.
    I've looked at TID
    http://www.novell.com/support/kb/doc.php?id=7009224
    as it has been referenced in here a couple of times for OES11 issues.
    I was missing
    /var/opt/novell/eDirectory/data/nmas-methods/CIFSLINLSM_X64 which I
    copied from a test OES11sp1 where CIFS was working.
    lsof -p `pgrep ndsd` | grep CIFSLINLSM[_X64] produces no results so I
    used the ndstrace steps.
    When going in to iMonitor I am missing the "sasLoginServerMethodLinux"
    but have the "sasLoginServerMethodLinuxX64"
    Any suggestions where to look from here?

    Scott,
    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/

  • OES11SP1 LDAP issue on a node

    Hi,
    I have a 2 node cluster that we have upgraded from OES11 to OES11 sp1 at the beginning of august
    Last week we create a new ressource on the primary node (let's say NODE 1), but when we want to migrate this new ressource to the other node (let's say NODE 2), the ressource became comatose.
    On node 2 what i can see in /var/log/messages is the following
    Aug 20 16:42:17 node2 ncs-resourced: Try LDAP for POOLDATA20_SERVER
    Aug 20 16:42:17 node2 ncs-resourced: LDAP failed: <class 'ldap.SERVER_DOWN'>
    Aug 20 16:42:53 node2 ncs-resourced: Error preprocessing script POOLDATA20_SERVER.load
    Aug 20 16:42:53 node2 ncs-resourced: POOLDATA20_SERVER.load: CRM: Tue Aug 20 16:42:53 2013
    Aug 20 16:42:53 node2 ncs-resourced: POOLDATA20_SERVER.load: /bin/sh: /var/run/ncs/POOLDATA20_SERVER.load: No such file or directory
    Aug 20 16:42:53 node2 ncs-resourced: resourceMonitor: POOLDATA20_SERVER load status=127
    Aug 20 16:42:54 node2 ncs-resourced: Error preprocessing script POOLDATA20_SERVER.unload
    Aug 20 16:42:54 node2 ncs-resourced: POOLDATA20_SERVER.unload: CRM: Tue Aug 20 16:42:54 2013
    Aug 20 16:42:54 node2 ncs-resourced: POOLDATA20_SERVER.unload: /bin/sh: /var/run/ncs/POOLDATA20_SERVER.unload: No such file or directory
    Aug 20 16:42:54 node2 ncs-resourced: resourceMonitor: POOLDATA20_SERVER unload status=127
    I try to change the configuration using a new.conf file liket it is in the documentation :
    CONFIG_NCS_CLUSTER_DN="cn=svr1_oes2_cluster.o=cont ext"
    CONFIG_NCS_LDAP_INFO="ldaps://10.1.1.102:636,ldaps://10.1.1.101:636"
    CONFIG_NCS_ADMIN_DN="cn=admin.o=context"
    CONFIG_NCS_ADMIN_PASSWORD="password"
    As the root user, enter the following command at a command prompt:
    /opt/novell/ncs/install/ncs_install.py -l -f new.conf on node1 and on node2
    and then cluster exec "/opt/novell/ncs/bin/ncs-configd.py -init"
    I reboot node2 but it is exaclty the same.
    Any idea ?
    Stphane

    Originally Posted by changju
    Hi Stphane,
    This is the key of the failure,
    Aug 20 16:42:17 node2 ncs-resourced: LDAP failed: <class 'ldap.SERVER_DOWN'>
    Somehow, looks like the Python LDAP on node2 couldn't connect the LDAP servers (10.1.1.102:636 or 10.1.1.101:636).
    Please first make sure that LDAP is up and running on the two servers.
    Please check file "/etc/opt/novell/ncs/clstrlib.conf" to make sure that you have something like this,
    p4
    S'ldaps://10.1.1.102:636,ldaps://10.1.1.101:636'
    If not, you need to modify file "new.conf" and run command "/opt/novell/ncs/install/ncs_install.py -l -f new.conf" on node2 again.
    You can then check the result of the installation in file "/var/opt/novell/install/ncslog", or you can simply run command "/opt/novell/ncs/bin/ncs-configd.py -init" on node2 to try to pull down the latest NCS configuration.
    If "/opt/novell/ncs/bin/ncs-configd.py -init" churns out a bunch of "dos2unix" messages (and pulls down the scripts for the new resources at "/var/opt/novell/ncs"), you should be able to migrate the resource.
    Regards,
    Changju
    Thank you very much Changju.
    I was not aware of this log file it was very helpfull.
    Apparently a tls issue for my 2 ldap server. I change it to ldap instead of ldaps and it is working now.
    Strange because i was able to connect using ldaps with ldap browser to the 2 nodes.
    Again, thank you
    Stphane

  • EDirectory question about OES2SP3 to OES11SP1 upgrade

    My apologies if this is not the correct place to ask this question but I decided to ask here becuase my question involved OES.
    We are going to perform an offline upgrade to OES 11 SP1 of an OES2SP3 server that hasn't been patched in one year.
    Novell Tech support told has told us in the past that prior to any server upgrade the server being upgraded should be fully patched but our concern has to do with eDirectory versions.
    Our OES2SP3 server runs DS version 20608.00 (eDirectory 8.8.6 Patch7) but if we install all OES2 SP3 patches available prior to the upgrade OES 11 SP1 I'll be installing eDirectory 8.8.7 Patch4 and our understanting is that the version of eDirectory included in the OES 11 SP1 media is eDirectory 8.8.7 Patch1.
    Will installing all OES 2 SP3 patches on this server cause eDirectory compatibility or eDirectory downgrade problems during the upgrade to OES 11 SP1 ?

    There is code in eDirectory's pre_ndsd_start script in OES 11 SP2 to
    prevent eDirectory from loading if it detects a downgrade during this
    upgrade, for the exact reason you mentioned. Basically the code prevents
    loading and instructs you to apply all of the current OES 11 SP1 patches
    from the channel at which point eDirectory will load again.
    With that said, I wouldn't worry too much about having all of the latest
    patches before trying to migrate to OES 11, especially with a down server
    upgrade. Upgrading from where you are should be supported since that was
    an option back before all of the latest patches for OES 2 SP3 were available.
    Another option may be to wait a couple of months for OES 11 SP2 to be
    released, at which time you can upgrade to that directly with eDirectory
    8.8 SP8.
    Good luck.

  • While upgrading sles11sp1/oes11 to sles11sp2/oes11sp1

    After the reboot and during the Edirectory upgrade, I encountered an error "Authentication for user has failed due to the following error: 0". I was then confronted with a question as to continue anyway or not. (I have a screen shot of the issue, but it will not let me post it) After starting a call with Novell, and the 2nd engineer later (about 2 hours), the ip address of the ldap server it was trying to use did not exist anymore, but what ever address you put in the server section, it would keep saying it could not contact the non-existent one. They could not explain and or figure out why. Ultimately I told the install to continue anyway and all went fine.
    Here is a link to the screen shot, http://sdrv.ms/ZLP5fl
    Has anyone else seen this on an upgrade? By the way, using dvd as upgrade source and the server is my master holder.

    On Mon, 29 Apr 2013 17:36:01 GMT, shesser
    <[email protected]> wrote:
    >
    >After the reboot and during the Edirectory upgrade, I encountered an
    >error "Authentication for user has failed due to the following error:
    >0". I was then confronted with a question as to continue anyway or not.
    >(I have a screen shot of the issue, but it will not let me post it)
    >After starting a call with Novell, and the 2nd engineer later (about 2
    >hours), the ip address of the ldap server it was trying to use did not
    >exist anymore, but what ever address you put in the server section, it
    >would keep saying it could not contact the non-existent one. They could
    >not explain and or figure out why. Ultimately I told the install to
    >continue anyway and all went fine.
    >Here is a link to the screen shot, http://sdrv.ms/ZLP5fl
    >
    >Has anyone else seen this on an upgrade? By the way, using dvd as
    >upgrade source and the server is my master holder.
    Sounds similar to what happened to me. Server was master. This
    server has been migrated from Netware to OES11/SLES11 sp1. Then
    during the upgrade to OES11 sp1/SLES11 sp2, it tried to contact an IP
    address that was no longer in use. I contacted support and they tried
    every way they could to get it to use an available ldap server ip, but
    nothing worked. Finally we just told it to continue and the install
    worked fine. Nobody knew why the error occurred or why we were able
    to ignore it and still have everything upgrade properly. Just odd.

  • After upgrade from sles11sp2/oes11sp1 to sp3/sp2

    Just checking for anymore updates and there is one for gcc47 that throws a conflict error that is in the attached pic. Anyone seen this one yet? Not sure what to do.

    Ran into the same thing after upgrading a couple servers. I patched a couple several months ago and did not run into this. With the slessp3-cpp47-9125.noarch patch, however, I have A LOT more deinstallation packages listed under the first option. Which did you deinstall, the single item on the 2nd option ? I just skipped the slessp3-cpp47-9125.noarch patch for now.

  • Nss issue with an application

    HI,
    we are using an application since 10 years now. This application use a share on an oes11 cluster. (it was on a Netware 6 before)
    Workstation are Windows seven x64 mainly and some Windows XP (Novell Client 2sp3ir1+ Xp Workstation 4.91sp5ir1).
    The application is used to managed business case. For each business case it creates a directory and several files in it. When you open the application on a device it open the last business case you were working on last time. You can decide to open another case, so the application create the list of all the busness case, then you pick up a case to work on it.
    So our issue is the following :
    user A open a case
    user B launch the application and try to open a new case. When he do that the application failed when it browse the file system on a file from the case open by user A.
    Normally the application browse the file system and display the list of the case. If a case is open by another user it just show that this case number is in use.
    It used to work perfectly on a Netware 6 box, but it does not work on our OES 11 box.
    If i put the share on a Windows box, the application is working.
    This application is very important for us and our business, and i don't understand why it is not working anymore on an oes 11 share.
    Can you help me to find out what it is going wrong ? I pick up a procmon trace and it only show INVALID HANDLE on the file open by user A
    With Wireshark i don't see any error.
    Any idea ?
    NMAS is disabled, File caching is disable also.
    Stephane

    The application is a very specific one. The name is Winchant and has been done using Windev.
    I have open a case and i have done some trace using Wireshark and processmonitor.
    The application is presenting to the user a list of busness case. Each of this busness case are a directory with multiple files :
    OES11SHARE\WInchant\case001
    OES11SHARE\WInchant\case002
    OES11SHARE\WInchant\casexxx
    The application root directory settings is OES11SHARE\WInchant\
    So when you open the application it is browsing and after a few seconds you have a window with all the cases. Then you open a case. Let's say case010.
    On a second device you open Winchant, the application browse the directory and failed on a case10 file.
    In Wireshark and ProcessMonitor the error happen on the case10 file and it is : "Invalid File Handle"
    If i put the Winchant directory and subdirectory to a Windows Share, the application show you all he case with and grey line on the case010 to reflect the fact that it is open on another device.
    I have put the application directory on a OES11sp1 box with latest update (April Maintenance) but it is the same. I have disable Oplock, File caching and Cross protocol file locking.
    I have update the Novell client on the seven box to 2sp3ir1.
    No change.
    I will also update my SR number with yours (10813788341) and let you know.
    Thanks
    Stephane

Maybe you are looking for