\\win_domain_controller\PIPE\lsarpc: Device busy

Hello Everyone,
I have installed Solaris 11.1 fine on one machine; but after installing Solaris 11.0 on another machine, the connection locks up with
file_server_01 smbd: daemon.notice: \\win_domain_controller\PIPE\lsarpc: Device busy (message from /var/adm/messages).
As a result, all zfs smb shares are off-line; the smbd server service does not restart when attempting to restart the service. The only temporary fix is to restart the file-server (not preferred).
Interestingly enough, the server shares remain active until a copy is performed--using Windows Explorer, rsync, or Robocopy. It takes about half-hour or so before the 'lsarpc' pipe becomes inactive (Device busy).
Thanks in advance
Edited by: 999003 on Apr 9, 2013 9:01 AM

Hello Mike,
Thanks for you fast reply and solution to my problem
I did exactly as you suggested and then I could access the port again.
I will modify the code so that when the error occurs again (port not found) I will force the port to close and then re-open it...
Many thanks,
Matthew

Similar Messages

  • Communication Channel error (Device busy)

    HI all,
    i have a problem with sender communication channel (CC) (type file) on PI 7.1
    The CC has follow error:
    Delivering the message to the application using connection File_http://sap.com/xi/XI/System failed, due to: com.sap.engine.interfaces.messaging.api.exception.MessagingException: java.io.FileNotFoundException: /IFR_PI/prd/out/TYPEB/SEDE_PV/PV_ART/VARGPV_I003 (Device busy).
    Anyone can help me to understand this error?
    Thanks in advance
    PM

    Hi,
          The file size is a drawback of file adapter.
          Check the note Note 821267 - FAQ: XI 3.0 / PI 7.0/ PI 7.1 File Adapter
         See point 14. Memory Requirements
    Indeed the error is IO Error and it is because the Adapter engine was not able to send the message to Integration server. But it happens due to memory/heap size issues.
    Look at these thread, they are having the same problem. Please try the remedy measures suggested by them
    Mail to Proxy scenario with attachment. AF channel error.
    Error with huge file
    problem with big file in file-to-proxy scenario
    regards,
    ganesh.

  • Device busy: 2nd hard drive (Ultra 10)

    Hi All:
    I'm working on a new Ultra 10 that came with two hard drives and
    pre-installed SunOS 7. I accidentally removed some configuration
    files and re-installed 5.8 BetaRefresh. Now the second hard drive
    is invisible to the OS. I would appreciate any pointers to have
    both drives working and formating hints ... Thanks.
    Here is what I did to find out what's going on:
    # uname -a
    SunOS home 5.8 Beta_Refresh sun4u sparc SUNW,Ultra-5_10
    # fmthard /dev/rdsk/c0t2d0s0
    fmthard: Cannot open device /dev/rdsk/c0t2d0s0 - Device busy
    # format
    Searching for disks...done
    AVAILABLE DISK SELECTIONS:
    0. c0t0d0 <ST39140A cyl 17660 alt 2 hd 16 sec 63>
    /pci@1f,0/pci@1,1/ide@3/dad@0,0
    Specify disk (enter its number): ^D
    # fsck /dev/dsk/c0t2d0s0
    Can't open /dev/dsk/c0t2d0s0
    # grep c0t2 /etc/*tab*
    # cfgadm -al
    Ap_Id Type Receptacle Occupant Condition
    c0 scsi-bus connected configured unknown
    c0::dsk/c0t0d0 unavailable connected configured unknown
    c0::dsk/c0t2d0 unavailable connected configured unknown
    # ls /dev/dsk
    c0t0d0s0 c0t0d0s2 c0t0d0s4 c0t0d0s6 c0t2d0s0 c0t2d0s2 c0t2d0s4 c0t2d0s6
    c0t0d0s1 c0t0d0s3 c0t0d0s5 c0t0d0s7 c0t2d0s1 c0t2d0s3 c0t2d0s5 c0t2d0s7
    # ls /dev/rdsk
    c0t0d0s0 c0t0d0s2 c0t0d0s4 c0t0d0s6 c0t2d0s0 c0t2d0s2 c0t2d0s4 c0t2d0s6
    c0t0d0s1 c0t0d0s3 c0t0d0s5 c0t0d0s7 c0t2d0s1 c0t2d0s3 c0t2d0s5 c0t2d0s7

    Update: The drive was reformatted on another g5 10.5 system and worked when I placed it back in my system. This leads me to believe that my install of 10.5 needs to be wiped clean and re-installed.

  • Solaris 8 IA "Device busy too long"

    The installation of Solaris 8/IA proceeds completely fine. However, when the system is to boot on it's own as the last step, I get the following error: "device busy too long." I've tried many different configurations for the SCSI card and I have followed the "device configuration guide." What could be causing this? It seems as though Solaris is completely happy with the hard drive and CD ROM during installation. Why are things different during runtime?
    I am using an Adaptec 2940AU SCSI card with a SCSI hard drive and with a SCSI CD ROM.
    Thanks in advance.

    Thanks for responding to my message concerning the "device busy too long."
    Before configuring the system I purchased components that were supported in the hardware compatibility list. Most importantly, the motherboard is an ASUS P3B-F and the SCSI card is an Adaptec AHA-2940AU. I read and followed the advice in the Solaris 8 Configuration Guide, the Adaptec literature, and the specs for the SCSI hard drive. I think I've tried every combination available.
    As a check I installed Windows 2000 on the system to make sure that there was fundamental compatibility. The OS installed without any problems the first time!! The system booted and operated completely stable. So I must assume that the components basically work together.
    I would like to know what Solaris is checking to arrive at a "device busy too long" state. If I knew this, perhaps I can solve the problem.
    Thanks again!! This sure is frustrating.

  • Cdrom device busy

    I try to install Oracle8i on Solaris 9.
    During Oracle installation, when it prompts me to insert CD #2, I can not eject CD. I typed # eject, then the "watch error" windows pops up as "/vol/dev/rdsk/c0t6d0/oracle8i: Device busy".
    I did use fuser -k /cdrom/cdrom0 and was able to eject it, but I have to restart the installation from beginning.
    I am new to Solaris and appreciate anyone here could advise me how to solve this matter.
    Thank you.
    solaris099

    Take a look to my system files:
    # /etc/fstab: static file system information
    # <file system> <dir> <type> <options> <dump> <pass>
    none /dev/pts devpts defaults 0 0
    none /dev/shm tmpfs defaults 0 0
    /dev/cdrom /media/cd iso9660 ro,user,noauto,unhide 0 0
    /dev/dvd /media/dvd udf ro,user,noauto,unhide 0 0
    #/dev/fd0 /media/fl auto user,noauto 0 0
    /dev/sda1 / ext4 defaults 0 1
    /dev/sda2 /var reiserfs defaults 0 2
    /dev/sda3 swap swap defaults 0 0
    /dev/sda4 /home jfs defaults 0 2
    My normarl user is called 'paneas', so take a loot to my /etc/group
    root::0:root
    bin::1:root,bin,daemon
    daemon::2:root,bin,daemon
    sys::3:root,bin
    adm::4:root,daemon
    tty::5:
    disk::6:root
    lp::7:daemon,paneas
    mem::8:
    kmem::9:
    wheel::10:root,paneas
    ftp::11:
    mail::12:
    uucp::14:
    log::19:root
    locate::21:
    smmsp::25:
    http::33:
    games::50:
    network:x:90:
    video:x:91:paneas
    audio::92:paneas
    optical::93:paneas,hal
    floppy:x:94:hal
    storage:x:95:paneas,hal
    scanner:x:96:
    power:x:98:paneas
    nobody::99:
    users::100:paneas
    dbus:x:81:
    rfkill:x:24:
    paneas:x:1000:
    hal:x:82:paneas,optical
    The hal daemon's auto hotplugging ISN'T working.
    Check it:
    [root@arch ~]# ls /media/cd
    [root@arch ~]# ls /var/run/daemons/
    alsa crond dbus hal netfs net-profiles network syslog-ng
    [root@arch ~]# /etc/rc.d/hal restart
    :: Stopping Hardware Abstraction Layer [DONE]
    :: Starting Hardware Abstraction Layer [DONE]
    [root@arch ~]# ls /media/cd

  • How to read Disk Device Busy (%) in GC?

    Hello All,
    I got the following alert in GC 10.2.0.3:
    Target Name=hostname
    Target Type=Host
    Host=mccmrkwbm007
    Metric=Disk Device Busy (%)
    Metric Value=95.31
    Disk Device=ssd31
    Timestamp=***
    Severity=Critical
    Message=Disk Device ssd31 is 95.31% busy.
    Notification Rule Name=Host Availability and Critical States
    Notification Rule Owner=SYSMAN
    Unfortunately, the disk device ssd31 doesn't correlate with any file system on this host. How did GC come up with the device name ssd31?
    Still researching in the documentation but thought I would post here just in case someone has seen this. I saw some posts about the documentation bug but that's about it so far.
    Cheers.

    I also saw under the metric Disk Activity the list of devices that GC can see...
    They are all identified as ssd#... how do i correlate this with the friendly file system?

  • QFS problem: Error: mount_samfs: mount() error: Device busy

    Hi:
    I setup the QFS on my two nodes sun cluster 3.2 environment. Everything works fine. But when i reboot both nodes, the QFS system cann't be mounted. it shows following error:
    Error: mount_samfs: mount() error: Device busy
    Following is my setup procedure:
    *2. Create the mcf file (on both nodes)*
    #cd /etc/opt/SUNWsamfs/
    #vi mcf
    # Equipment Eq Eq Family Device Additional
    # Identifier Ord Type Set State Parameters
    archive 2 ma archive on shared
    /dev/did/dsk/d5s4 20 mm archive on
    /dev/did/dsk/d5s3 21 mr archive on
    *3. Create the hosts file (on both nodes)*
    #cd /etc/opt/SUNWsamfs/
    #vi hosts.archive
    #HostName NetworkInterface ServerPriority Unused Server
    xenon 172.16.0.129 1 0 server
    arsenic 172.16.0.130 1 0
    *4. modify the /etc/vfstab file (on both nodes)*
    #vi /etc/vfstab
    #device device mount FS fsck mount mount
    #to mount to fsck point type pass at boot options
    archive - /archive samfs - no shared,notrace
    *5. create the mount point (on both nodes)*
    #mkdir /archive
    #chmod 755 archive
    *6. create the file system (on the server node)*
    [root@xenon:/etc/opt/SUNWsamfs #]samd config
    Configuring SAM-FS
    [root@xenon:/etc/opt/SUNWsamfs #]sammkfs -S -a 64 archive
    Building 'archive' will destroy the contents of devices:
    /dev/did/dsk/d5s4
    /dev/did/dsk/d5s3
    Do you wish to continue? [y/N]y
    total data kilobytes = 68525248
    total data kilobytes free = 68525184
    total meta kilobytes = 1044224
    total meta kilobytes free = 1043680
    *7. mount the file system*
    on server side
    [root@xenon:/etc/opt/SUNWsamfs #]mount /archive
    [root@xenon:/etc/opt/SUNWsamfs #]chown �R oracle:dba /archive
    On client side
    [root@arsenic:/etc/opt/SUNWsamfs #]mount /archive
    mount_samfs: Configuring file system
    *8. Create the QFS metadata server (MDS) resource group for high availability.*
    From xenon do:
    # clresourcetype register SUNW.qfs
    # clresourcegroup create -p nodelist=xenon,arsenic archive-rg
    # clresource create -t SUNW.qfs -g archive-rg -p QFSFileSystem=/archive archive-rs
    # clresourcegroup online -emM archive-rg
    Actually, i did not do the step 8 (Create the QFS metadata server (MDS) resource group for high availability).
    then i reboot both nodes, the QFS failed to be mounted
    I found one doc is related to my problem.
    http://sunsolve.sun.com/search/document.do?assetkey=1-25-90055
    It suggests to restart the samfs-qfs Resource Group to fix the problem. But the problem is i haven't setup the "samfs-qfs Resource Group ".
    How can i do now? any advices?
    Many many thanks!
    Larry chen
    Edited by: chenjg00 on Nov 13, 2007 12:38 PM

    It looks like you have the wrong entries in your hosts.archive file.
    On a cluster, these should always reference the clusternode-priv names, e.g.
    -bash-3.00# cat hosts.rac_data
    pgyruss1 clusternode1-priv 1 0 server
    pgyruss2 clusternode2-priv 1 0
    These resolve to slight different addresses to the ones you are using and that might be the cause of your problem.
    -bash-3.00# getent hosts clusternode1-priv
    172.16.4.1 clusternode1-priv
    Try that and see if it works. You might have to fiddle about a bit and may need to run "samd config" again.
    Tim
    ---

  • New SCSI hard drive problem: Device busy too long

    I set up second SCSI hard drive for my sun box Sparc Station 20. The set up is as follows:
    New SCSI hard drive (ID #2) connects to Sun box and connects to tape drive (SCSI #4) with terminator.
    Hard drive is Seagate model ST15150N with J01 (open : means disable drive terminator) and J04 (jumper on second position, ID=2).
    I CAN format the hard drive and assign label etc.. but when I type the command : > newfs /dev/rdsk/c1t2d0s7 (I use whole slice 7 as one partition and c1 is my second controller).
    The following error displays continuously:
    WARNING: /iomnn@f,e0000000/sbus@f,e0001000/dma@1,81000/esp@1,80000/sd@2,0 device busy too long
    Is this error come from the wrong hardware set up or from other reason ? Any suggestion is welcome . Thanks in advance.
    William

    First of all, thanks for your reply. I appreciate it.
    A couple of things. I check my system profiler and I couldn't find out what kind of SCSI card I have. I even opened up my machine and there wasn't any writing on it. So how do I find out what type of card I have? My other question is if the same card worked for the SCSI drive I had before, why won't it work on the new drive. I've set it as the master at the end of the SCSI cord and like I said I used CCC. The drive shows up on my desktop but won't boot. Should I try loading OS from disks instead of using CCC?

  • Disk Utility - Device Busy

    I used to be able to burn and append CDs/DVDs using Disk Utility.
    Now for some reason my files are greyed out and when I do try
    to create an image to burn I get a Stop Sign followed by "device busy" -
    even though there is no disk in the optical drive. Can anybody help?
    Thanks/
    G-5   Mac OS X (10.3.9)  

    So, you're using DU to create an image for restore, is that correct? Is the external USB, FireWire, or both? The "device busy" indicates that something's either linked to that HD or something's writing to it. SystemPrefs->Spotlight->Privacy and add the ext HD to the window, restart, and try again. BTW, more details would be helpful; such as, computer, OS, etc.
    Finally, why an image? You have to restore it someplace to ensure that it's a viable clone, since it's not bootable. I'd suggest using Carbon Copy Cloner, SuperDuper!, etx. and make a bootable clone.

  • All Pipe Instances are Busy

    I am running an Oracle Server 7.3.3.0.0 on an Windows NT4.0 server.
    We currently are running about 30 small database instances on the NT box.
    When I try to start an additional Oracle instance, I get the message "Could not start the service on xxxxxx. Error 0231: All pipe instances are busy". If I shut down one of the currently running instances, I can start another one, I just can't go over a certain total number of these services.
    I have found some references that say that Oracle creates a Named Pipe ("ORAPIPE") and that it has a parameter called nMaxInstances which can be set to "PIPE_UNLIMITED_INSTANCES", but I can't figure out where to make this configuration change. Would changing my protocol to straight TCP/IP solve this issue? I have also found a parameter called "USE_SHARED_SOCKET" but am uncertain of where to set this.
    Any help would be appreciated.

    You may be running into an NT4 internal limit; I have checked the W2K resource kit though and can't find anything about max. number of pipes.

  • LaserJet M1212NF MFP "DEVICE BUSY" FREQUENTLY

    We have a LaserJet M1212NF and it seems almost after every other fax or scan it says "Device is Busy" and the only way we can clear the message and use the fax machine is to turn it off and wait a few minutes before turning it back on.  I have checked the driver and few other things and they seemed to be up to date and normal. 

    Hi @anna37020 ,
    I see that you are experiencing issues with the printer going into a error of "Device Busy" after every other fax, then you have to restart the printer to clear the message. I will certainly do my best to help you.
    Check these fax settings on the printer:
    Go to setup, (wrench) fax setup menu,OK, fax receive setup, OK, private receive, OK, turn if off.
    Go to setup, (wrench) fax setup menu,OK, all faxes, OK, error correction, OK, turn it off.
    Go to setup, (wrench) fax setup menu,OK, all faxes, OK, fax speed, set it to medium.
    Go to setup, (wrench) fax functions, clear saved faxes, OK to clear.
    Test the fax now.
    Update the printer's firmware. HP LaserJet Firmware Update Utility.
    I will send you another step to try in a private message.
    In the forum beside your handle name just click on the envelope to view it.
    If you need further assistance, just let me know.
    Have a great day!
    Thank You.
    Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
    Click the “Kudos Thumbs Up" on the right to say “Thanks” for helping!
    Gemini02
    I work on behalf of HP

  • CSCtq10477 - Callmanager 9.1 can't make outbound calls, Route List gets error 41 - All devices busy

    Hi all
    I seem to have run into bug CSCtq10477 and maybe CSCul71689 and CSCum85086, where calls can be received from an MGCP gateway, but fail outbound with Callmanager logs showing
    03095771.002 |17:34:14.103 |AppInfo  |RouteListCdrc::null0_CcSetupReq - Terminating a call after the RouteListCdrc cannot find any more device.
    03095771.003 |17:34:14.103 |AppInfo  |RouteListCdrc::terminateCall - No more Routes in RouteListName = RL_OUTBOUND.  Rejecting the call
    03095771.004 |17:34:14.103 |AppInfo  |RouteListCdrc::terminateCall - Sending CcRejInd, with the cause code (41), to RouteListControl because all devices are busy/stopped.
    03095771.005 |17:34:14.103 |AppInfo  |GenAlarm: AlarmName = RouteListExhausted, subFac = CALLMANAGERKeyParam = , severity = 4, AlarmMsg = RouteListName : RL_OUTBOUND, Reason=41, RouteGroups(RG_OUTBOUND)
    and a Route List exhausted alarm appearing in RTMT.
    Resetting the MGCP gateway in Callmanager, bouncing the serial interface, E1 controller and No MGCP/MGCP has no impact.  I could also see the circuit was not full.
    We have got round this by removing the gateway from the Route Group and pointing the Route Patterns directly at the gateway and this works.  I can see two of the bugs above are fixed in the latest 9.1.2SU3 code (9.1.2.13900-10), but I don't see CSCtq10477.  This bug document shows some 9.1 code is OK, but not this one.
    9.1(1.21020.1) - Not listed for download, is this an ES?
    9.1(2.10000.11) - Not listed for download, is this an ES?
    9.1(2.10000.28) - 9.1(2) - but not shown in the release notes for 9.1(2) either.
    Does anyone know if the Release notes just missed this out, or does the bug document need the Fixed versions to be updated?
    Thanks

    Hi,
    9.1(1.21020.1)  is an ES.
    9.1(2.10000.28) is the base version of 9.1(2) so this bug will be fixed in this version or any higher version of 9.1(2).
    Upgrading to the latest ES or 9.1(1) or 9.1(2)SU3 would take care of this bug.
    HTH
    Manish

  • ALSA device busy for normal user (not root) after systemd [resolved]

    I'm not able to get audio when using a normal user (device or resource busy) but root works just fine. I think I've messed something up since I just removed consolekit and switched to systemd.
    Here's what my .xinitrc looks like
    #!/bin/sh
    # ~/.xinitrc
    # Executed by startx (run your window manager from here)
    if [ -d /etc/X11/xinit/xinitrc.d ]; then
    for f in /etc/X11/xinit/xinitrc.d/*; do
    [ -x "$f" ] && . "$f"
    done
    unset f
    fi
    #exec gnome-session
    #exec startkde
    #exec startxfce4
    #exec enlightenment_start
    # ...or the Window Manager of your choice
    #exec ck-launch-session startlxde
    exec dbus-launch startlxde
    I use LightDM via systemd service and LXDE. My devices in /dev/snd aren't actually busy. Nobody is using them and they work fine for root.
    Where else should I be looking for trouble? Anyone have a similar experience?
    Last edited by royallthefourth (2013-06-12 17:32:20)

    It says I'm in the audio group. Here's the permission on the audio devices:
    crw-rw----+ 1 root audio 116, 6 Jun 12 03:45 controlC0
    crw-rw----+ 1 root audio 116, 9 Jun 12 03:45 controlC1
    crw-rw----+ 1 root audio 116, 11 Jun 12 03:45 controlC2
    crw-rw----+ 1 root audio 116, 8 Jun 12 03:45 hwC1D0
    crw-rw----+ 1 root audio 116, 5 Jun 12 03:45 pcmC0D0c
    crw-rw----+ 1 root audio 116, 4 Jun 12 03:45 pcmC0D0p
    crw-rw----+ 1 root audio 116, 3 Jun 12 03:45 pcmC0D1c
    crw-rw----+ 1 root audio 116, 2 Jun 12 03:45 pcmC0D1p
    crw-rw----+ 1 root audio 116, 7 Jun 12 03:45 pcmC1D3p
    crw-rw----+ 1 root audio 116, 10 Jun 12 03:45 pcmC2D0c
    crw-rw----+ 1 root audio 116, 1 Jun 12 03:45 seq
    crw-rw----+ 1 root audio 116, 33 Jun 12 03:45 timer
    I ought to have access to these, right?

  • [help] / device busy when shutting down.

    After update to .38 kernel, I meet this problem: root filesystem busy.
    I have tried these way,
    1, umount -l all device
    2, stop all daemon
    but no use.
    my fstab:
    none                   /dev/pts      devpts    defaults            0      0
    none                   /dev/shm      tmpfs     defaults            0      0
    /dev/sda1 / ext4 defaults 0 1
    tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0
    tmpfs /home/[user]/.mozilla/firefox/p8bx55da.default/Cache tmpfs defaults,noatime,mode=1777,noexec 0 0
    my rc.conf:
    MODULES=(!snd_pcm_oss !snd_mixer_oss !snd_seq_oss !thinkpad_ec tp_smapi hdaps acpi-cpufreq !tpm_tis)
    USELVM="no"
    DAEMONS=(syslog-ng dbus acpid hdapsd tpfand networkmanager hddtemp alsa laptop-mode sysfsutils ufw)

    Laptop Mode Tools

  • Ppp daemon has died/device busy

    Hi
    Im trying to connect my usb modem for internet access and i think im almost there i have wvdial installed and was able to connect for about 2 seconds before i got a message saying ( ppp daemon has died exit code 127 ).When i rebooted and typed in wvdial i got another message saying ( ttyUSB0 device or resource busy )and after that i got ( cannot get info for serial port - initializing modem )
    these are the versions packages im using:
    wvdial-1.60-1.pkg.tar
    wvstreams-4.4-1.pkg.tar
    xplc-0.3.13-1.pkg.tar
    openslp-1.2.1-1.pkg.tar
    ppp-2.4.4-4.pkg.tar
    Im not sure if this helps
    Thanks
    Last edited by unilx (2009-10-26 17:55:06)

    codycarey wrote:
    It looks like pppd is fine, but it's trying to use a device that doesn't exist.
    --> Cannot open /dev/rfcomm0: Input/output error
    --> Cannot open /dev/rfcomm0: Connection reset by peer
    --> Cannot get information for serial port.
    These errors occur on _redial_ attempt.
    (I have to execute "/etc/rc.d/bluetooth restart" after every wvdial attempt but I think it's OK).
    codycarey wrote:What is the GPRS device you're using?
    Samsung SGH-D830 (via Bluetooth).

Maybe you are looking for