Unable to connect to local server

Folks:
When I tried to access an older Mac running Leopard (10.5.8) from my MacBook Pro running Mavericks (Finder: Go: Connect to Server: LocalServer), I was unable to connect and received a message,
'There was a problem connecting to the server "LocalServer".  The server may not exist or is unavailable at this time.  Check the server name or IP address, check your network connection, and then try again."
I tried deleting any keychain refrerence to local computer. 
I tried deleting the list of recent servers from the Finder. 
I tried restarting both my laptop and the local server.
Nothing, 
There is a local server icon under the "Shared" section of the sidebar of the Finder browsing window.  I can find no way to delete this listing. 
I can access the the Mavericks MBP from the old Leopard server via remote login, but I was unable access the old Leopard server from the new Mavericks running MBP. 
I finally achiveved access by
1) Turning on SMB sharing for my account on the local server
          System Preferences: Sharing: File Sharing: Options: SMB Sharing: MyAccount then storing my password.
2) On my MBP, connecting via smb.
          Finder: Go: Connect to Server: [Enter smb://Localserver.local]
It finally worked, BUT … after successfully connecting to the local server, I now have TWO listings for Localserver in my Finder browser window, the live link and the old link which still says "Connecting." 
I can't figure out how to get rid of the earlier afp link, OR how to make it work.  I would prefer to use AFP as the SMB notation from both computers indicates that the storage of my password is not as secure. 
Restaring the computer doesn't help.
I had a similiar problem when I upgraded to Mountain Lion, and I tried many of the same tricks to no avail.  That problem seems to have fixed itself. 
Anybody have any bright ideas?
Thanks much.

I should have been more clear. This is on an 8-core Intel XServe.
I was able to use Server Admin locally on the machine for weeks. Now I can't. Nothing has changed or been altered on the machine during that period.
I can not connect to the server via Server Admin remotely or locally. I can connect via SSH, ARD, etc. and the system is still serving NFS just fine, so it's just the process that handles communication with Server Admin that is non responsive.
Something interesting from the syslog:
qt1 servermgrd[44258]: servermgr_accounts: noteDirectorySearchPolicyChanged (reopening nodes)
qt1 servermgrd[44258]: -[AccountsRequestHandler(AccountsOpenDirectoryHelpers) openLocalLDAPNodeIfNeeded]: dsLocalLDAP = (null) , error = Error Domain=com.apple.OpenDirectory Code=2000 UserInfo=0x1066a16c0 "Unable to open Directory node with name /LDAPv3/127.0.0.1."
qt1 DirectoryService[31]: DirectoryService has 42000 internal references open (due to clients), warning limit is 2000.
These lines repeated apprx. every 30 secs until I bounced the servermgrd. Now, I see that entry whenever I try to connect to the local server via Server Admin.
Now, this system is not a LDAP server, but I understand OSXS still uses LDAP for local directory info... I've tried restarting the related directory services as well, but still no joy.
It looks like my only recourse is a reboot, which is really not a great option for a dedicated file server. Am I the only one who has ever encountered this issue of Server Admin eventually losing contact with a server?

Similar Messages

  • Server Admin unable to connect to local server

    Hey all. I've been using SLS to serve a Promise RAID via NFS for a few weeks now, and it's been stable and smooth. I've had Server Admin open all that time so I could watch the network usage graph via ARD. Today, Server Admin can no longer connect to the local server. I've tried stopping and starting com.apple.servermgrd but it still cannot connect. Is my only option at this point a reboot?
    Has anyone else experienced this on SLS? I've always had stability issues with Server Admin in the past, but I'd been told the issues had been addressed in SLS. Could someone verify this? Thanks

    I should have been more clear. This is on an 8-core Intel XServe.
    I was able to use Server Admin locally on the machine for weeks. Now I can't. Nothing has changed or been altered on the machine during that period.
    I can not connect to the server via Server Admin remotely or locally. I can connect via SSH, ARD, etc. and the system is still serving NFS just fine, so it's just the process that handles communication with Server Admin that is non responsive.
    Something interesting from the syslog:
    qt1 servermgrd[44258]: servermgr_accounts: noteDirectorySearchPolicyChanged (reopening nodes)
    qt1 servermgrd[44258]: -[AccountsRequestHandler(AccountsOpenDirectoryHelpers) openLocalLDAPNodeIfNeeded]: dsLocalLDAP = (null) , error = Error Domain=com.apple.OpenDirectory Code=2000 UserInfo=0x1066a16c0 "Unable to open Directory node with name /LDAPv3/127.0.0.1."
    qt1 DirectoryService[31]: DirectoryService has 42000 internal references open (due to clients), warning limit is 2000.
    These lines repeated apprx. every 30 secs until I bounced the servermgrd. Now, I see that entry whenever I try to connect to the local server via Server Admin.
    Now, this system is not a LDAP server, but I understand OSXS still uses LDAP for local directory info... I've tried restarting the related directory services as well, but still no joy.
    It looks like my only recourse is a reboot, which is really not a great option for a dedicated file server. Am I the only one who has ever encountered this issue of Server Admin eventually losing contact with a server?

  • [Solved] Samba log spam: Unable to connect to CUPS server

    Hi everyone,
    I'm running into an annoying issue with samba. I don't have any printers installed, and probably won't. However smbd complains to no end in /var/log/errors.log about not being able to connect to a cups server:
    Apr 18 12:30:05 asakura nmbd[4361]: *****
    Apr 18 12:30:05 asakura nmbd[4361]:
    Apr 18 12:30:05 asakura nmbd[4361]: Samba name server ASAKURA is now a local master browser for workgroup MYGROUP on subnet 192.168.1.121
    Apr 18 12:30:05 asakura nmbd[4361]:
    Apr 18 12:30:05 asakura nmbd[4361]: *****
    Apr 18 12:32:22 asakura smbd[4552]: [2009/04/18 12:32:22, 0] printing/print_cups.c:cups_connect(103)
    Apr 18 12:32:22 asakura smbd[4552]: Unable to connect to CUPS server localhost:631 - Connection refused
    Apr 18 12:32:22 asakura smbd[4553]: [2009/04/18 12:32:22, 0] printing/print_cups.c:cups_connect(103)
    Apr 18 12:32:22 asakura smbd[4553]: Unable to connect to CUPS server localhost:631 - Connection refused
    Those last two lines get spammed constantly.
    I've done a little bit of research into the matter, and followed the steps here to try to resolve the problem: http://www.davekb.com/browse_computer_t … server:txt
    Unfortunately it doesn't appear to make any difference.
    Here is my /etc/samba/smb.conf:
    # This is the main Samba configuration file. You should read the
    # smb.conf(5) manual page in order to understand the options listed
    # here. Samba has a huge number of configurable options (perhaps too
    # many!) most of which are not shown in this example
    # For a step to step guide on installing, configuring and using samba,
    # read the Samba-HOWTO-Collection. This may be obtained from:
    # http://www.samba.org/samba/docs/Samba-HOWTO-Collection.pdf
    # Many working examples of smb.conf files can be found in the
    # Samba-Guide which is generated daily and can be downloaded from:
    # http://www.samba.org/samba/docs/Samba-Guide.pdf
    # Any line which starts with a ; (semi-colon) or a # (hash)
    # is a comment and is ignored. In this example we will use a #
    # for commentry and a ; for parts of the config file that you
    # may wish to enable
    # NOTE: Whenever you modify this file you should run the command "testparm"
    # to check that you have not made any basic syntactic errors.
    #======================= Global Settings =====================================
    [global]
    # workgroup = NT-Domain-Name or Workgroup-Name, eg: MIDEARTH
    workgroup = MYGROUP
    # server string is the equivalent of the NT Description field
    server string = Samba Server
    # Security mode. Defines in which mode Samba will operate. Possible
    # values are share, user, server, domain and ads. Most people will want
    # user level security. See the Samba-HOWTO-Collection for details.
    security = user
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page
    ; hosts allow = 192.168.1. 192.168.2. 127.
    # If you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    load printers = no
    # you may wish to override the location of the printcap file
    ; printcap name = /etc/printcap
    # on SystemV system setting printcap name to lpstat should allow
    # you to automatically obtain a printer list from the SystemV spool
    # system
    ; printcap name = lpstat
    # It should not be necessary to specify the print system type unless
    # it is non-standard. Currently supported print systems include:
    # bsd, cups, sysv, plp, lprng, aix, hpux, qnx
    ; printing = cups
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    ; guest account = pcguest
    # this tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/%m.log
    # Put a capping on the size of the log files (in Kb).
    max log size = 50
    # Use password server option only with security = server
    # The argument list may include:
    # password server = My_PDC_Name [My_BDC_Name] [My_Next_BDC_Name]
    # or to auto-locate the domain controller/s
    # password server = *
    ; password server = <NT-Server-Name>
    # Use the realm option only with security = ads
    # Specifies the Active Directory realm the host is part of
    ; realm = MY_REALM
    # Backend to store user information in. New installations should
    # use either tdbsam or ldapsam. smbpasswd is available for backwards
    # compatibility. tdbsam requires no further configuration.
    ; passdb backend = tdbsam
    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting.
    # Note: Consider carefully the location in the configuration file of
    # this line. The included file is read at that point.
    ; include = /usr/local/samba/lib/smb.conf.%m
    # Configure Samba to use multiple interfaces
    # If you have multiple network interfaces then you must list them
    # here. See the man page for details.
    ; interfaces = 192.168.12.2/24 192.168.13.2/24
    # Browser Control Options:
    # set local master to no if you don't want Samba to become a master
    # browser on your network. Otherwise the normal election rules apply
    ; local master = no
    # OS Level determines the precedence of this server in master browser
    # elections. The default value should be reasonable
    ; os level = 33
    # Domain Master specifies Samba to be the Domain Master Browser. This
    # allows Samba to collate browse lists between subnets. Don't use this
    # if you already have a Windows NT domain controller doing this job
    ; domain master = yes
    # Preferred Master causes Samba to force a local browser election on startup
    # and gives it a slightly higher chance of winning the election
    ; preferred master = yes
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations.
    ; domain logons = yes
    # if you enable domain logons then you may want a per-machine or
    # per user logon script
    # run a specific logon batch file per workstation (machine)
    ; logon script = %m.bat
    # run a specific logon batch file per username
    ; logon script = %U.bat
    # Where to store roving profiles (only for Win95 and WinNT)
    # %L substitutes for this servers netbios name, %U is username
    # You must uncomment the [Profiles] share below
    ; logon path = \\%L\Profiles\%U
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    ; wins support = yes
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    # Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    ; wins server = w.x.y.z
    # WINS Proxy - Tells Samba to answer name resolution queries on
    # behalf of a non WINS capable client, for this to work there must be
    # at least one WINS Server on the network. The default is NO.
    ; wins proxy = yes
    # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
    # via DNS nslookups. The default is NO.
    dns proxy = no
    # These scripts are used on a domain controller or stand-alone
    # machine to add or delete corresponding unix accounts
    ; add user script = /usr/sbin/useradd %u
    ; add group script = /usr/sbin/groupadd %g
    ; add machine script = /usr/sbin/adduser -n -g machines -c Machine -d /dev/null -s /bin/false %u
    ; delete user script = /usr/sbin/userdel %u
    ; delete user from group script = /usr/sbin/deluser %u %g
    ; delete group script = /usr/sbin/groupdel %g
    #============================ Share Definitions ==============================
    ; [homes]
    ; comment = Home Directories
    ; browseable = no
    ; writable = yes
    # Un-comment the following and create the netlogon directory for Domain Logons
    ; [netlogon]
    ; comment = Network Logon Service
    ; path = /usr/local/samba/lib/netlogon
    ; guest ok = yes
    ; writable = no
    ; share modes = no
    # Un-comment the following to provide a specific roving profile share
    # the default is to use the user's home directory
    ;[Profiles]
    ; path = /usr/local/samba/profiles
    ; browseable = no
    ; guest ok = yes
    # NOTE: If you have a BSD-style print system there is no need to
    # specifically define each individual printer
    ; [printers]
    ; comment = All Printers
    ; path = /var/spool/samba
    ; browseable = no
    # Set public = yes to allow user 'guest account' to print
    ; guest ok = no
    ; writable = no
    ; printable = yes
    # This one is useful for people to share files
    ;[tmp]
    ; comment = Temporary file space
    ; path = /tmp
    ; read only = no
    ; public = yes
    # A publicly accessible directory, but read only, except for people in
    # the "staff" group
    ;[public]
    ; comment = Public Stuff
    ; path = /home/samba
    ; public = yes
    ; writable = yes
    ; printable = no
    ; write list = @staff
    # Other examples.
    # A private printer, usable only by fred. Spool data will be placed in fred's
    # home directory. Note that fred must have write access to the spool directory,
    # wherever it is.
    ;[fredsprn]
    ; comment = Fred's Printer
    ; valid users = fred
    ; path = /homes/fred
    ; printer = freds_printer
    ; public = no
    ; writable = no
    ; printable = yes
    # A private directory, usable only by fred. Note that fred requires write
    # access to the directory.
    ;[fredsdir]
    ; comment = Fred's Service
    ; path = /usr/somewhere/private
    ; valid users = fred
    ; public = no
    ; writable = yes
    ; printable = no
    # a service which has a different directory for each machine that connects
    # this allows you to tailor configurations to incoming machines. You could
    # also use the %U option to tailor it by user name.
    # The %m gets replaced with the machine name that is connecting.
    ;[pchome]
    ; comment = PC Directories
    ; path = /usr/pc/%m
    ; public = no
    ; writable = yes
    # A publicly accessible directory, read/write to all users. Note that all files
    # created in the directory by users will be owned by the default user, so
    # any user with access can delete any other user's files. Obviously this
    # directory must be writable by the default user. Another user could of course
    # be specified, in which case all files would be owned by that user instead.
    ;[public]
    ; path = /usr/somewhere/else/public
    ; public = yes
    ; only guest = yes
    ; writable = yes
    ; printable = no
    # The following two entries demonstrate how to share a directory so that two
    # users can place files there that will be owned by the specific users. In this
    # setup, the directory should be writable by both users and should have the
    # sticky bit set on it to prevent abuse. Obviously this could be extended to
    # as many users as required.
    ;[myshare]
    ; comment = Mary's and Fred's stuff
    ; path = /usr/somewhere/shared
    ; valid users = mary fred
    ; public = no
    ; writable = yes
    ; printable = no
    ; create mask = 0765
    [shared]
    path = /media/shared
    valid users = foosoft
    public = no
    writable = yes
    [tomato]
    path = /media/data1/tomato
    valid users = foosoft
    public = no
    writable = yes
    show add printer wizard = no
    printing = none
    printcap name = /dev/null
    disable spoolss = yes
    I'm totally out of ideas here, anyone have a tip on what I could try next?
    Last edited by FooSoft (2009-04-18 19:52:28)

    glad you posted it first i had the same problem.
    However, samba was complaining that
    printing = none
    was invalid. I removed that line and it works great.
    thanks
    Last edited by lio (2009-10-16 00:20:14)

  • [Forum FAQ] "Unable to connect to the server by using Windows PowerShell Remoting" error while installing RDS roles on Server 2012 R2

    When you try to install RDS role on server 2012 R2 using standard deployment, this issue may occur (Figure 1).
    “Unable to connect to the server by using Windows PowerShell remoting”.
    Figure 1: Unable to connect to the server by using Windows PowerShell remoting
    First of all, we need to verify the configurations as it suggested:
    1. The server must be available by using Windows PowerShell remotely.
    2. The server must be joined to a domain.
    3. The server must be running at least Windows Server 2012 R2.
    4. The currently logged on user must be a member of the local Administrators group on the server.
    5. Remote Desktop Services connections must be enabled by using Group Policy.
    In addition, we need to check if the “Windows Remote Management “service is running and related firewall exceptions have been created for WinRM listener.
    To enabling PowerShell remoting, we can run this PowerShell command as administrator (Figure 2).
    Enable-PSRemoting -Force
    Figure 2: Enable PowerShell Remoting
    However, if issue persists, we need to check whether it has enough memory to work.
    By default, remote shell allots only 150 MB of memory. If we have IIS or SharePoint App pool, 150 MB of memory is not sufficient to perform the remoting task. Therefore, we need to increase
    the memory via the PowerShell command below:
    Set-Item WSMan:\localhost\Shell\MaxMemoryPerShellMB 1000
    Then, you need to restart the server and the issue should be resolved.
    You can get more information regarding Remote Troubleshooting by below link:
    about_Remote_Troubleshooting
    If you need further assistance, welcome to post your questions in the
    RDS forum.
    Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

    i found another possible reason, this solution worked for me:
    http://oyvindnilsen.com/solution-for-powershell-remoting-error-it-cannot-determine-the-content-type-of-the-http-response-from-the-destination-computer/
    I tried to set up powershell remoting on a server and kept getting this error:
    Enter-PSSession : Connecting to remote server failed with the following error message : The WinRM client cann
    ot process the request. It cannot determine the content type of the HTTP response from the destination comput
    er. The content type is absent or invalid. For more information, see the about_Remote_Troubleshooting Help to
    pic.
    After a bit of troubleshooting I discovered that the problem was that the authentication packets was to big (over 16k), this will cause WinRM to reject the request. The reason for authentication packets getting too big can be because the user is member of very
    many security groups or in my case because of the SidHistory attribute.
    The solution was to increase the MaxFieldLength and MaxRequestBytes keys in the registry under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters
    If the keys does not exists you can create them, be sure to use the DWORD type.
    I sat MaxFieldLength to DEC value 40000 and MaxRequestBytes to DEC value 32768 and rebooted the server. Problem solved.

  • OD users unable to connect to a server via afp

    We have a Mac OS 10.9.2 with Server 3.1.2.  We are able to access the server for file sharing via smb with OD accounts just fine.  But we are unable to connect to the server using afp with any OD account, only local system accounts.  I have tried turning off SMB for all of the file shares, but this did not help resolve the issue.
    The log shows a login attempt immediately followed by a logout.
    Aug  7 13:40:33 server.company.com AppleFileServer[736] <Info>: IP 192.168.101.2 - - "Login -----" -5023 0 0
    Aug  7 13:40:33 server.company.com AppleFileServer[736] <Info>: IP 192.168.101.2 - - "Logout -----" -5023 0 0
    I did edit out the user and the server name.
    Any help would be greatly appreciated.
    Thank you.

    Many Open Directory problems can be resolved by taking the following steps. Test after each one, and back up all data before making any changes.
    1. The OD master must have a static IP address on the local network, not a dynamic address.
    2. You must have a working DNS service, and the server's hostname must match its fully-qualified domain name. To confirm, select the server by name in the sidebar of the Server application window, then select the Overview tab. Click the Edit button on the Host Name line. On the Accessing your Server sheet, Domain Name should be selected. Change the Host Name, if necessary. The server must have at least a three-level name (e.g. "server.yourdomain.com"), and the name must not be in the ".local" top-level domain, which is reserved for Bonjour.
    3. The primary DNS server used by the server must be 127.0.0.1 (that is, itself) unless you're using another server for internal DNS. The only DNS server set on the clients should be the internal one, which they should get from DHCP if applicable.
    4. Follow these instructions to rebuild the Kerberos configuration on the master.
    5. If you use authenticated binding, check the validity of the master's certificate. The common name must match the hostname and domain name. Deselecting and then reselecting the certificate in Server.app has been reported to have an effect in some cases.
    6. Unbind and then rebind the clients in the Users & Groups preference pane. Use the fully-qualified domain name of the master.
    7. Reboot the master and the clients.
    8. Don't log in to the server with a network user's account.
    9. As a last resort, export all OD users. In the Open Directory pane of Server, delete the OD server. Then recreate it and import the users. Ensure that the UID's are in the 1001+ range.

  • Debugger unable to connect to local process

    I am going thru the JDeveloper Introduction Tutorial and when I try to debug the application I get the following error in the message window:
    C:\JDev\jdk\bin\javaw.exe -ojvm -XXdebug,quiet,port1069 -classpath C:\JDev\jdev\mywork\MyFirstApp\MyProject\classes myproject.Dog
    Debugger unable to connect to local process.
    Process exited.
    I am using Windows XP Professional
    JDeveloper 10.1.3.4.3673
    If I just run the application then it works.
    I also have the Sun Java JDK installed, as well as Eclipse and NetBeans installed.
    I tried reinstalling JDeveloper but the debug function still does not work.
    Any help will be highly appreciated.
    Thanks,
    Raffy

    I am trying to debug a JSP application and each time I try to debug I get the error:
    [Starting OC4J using the following ports: HTTP=8989, RMI=23893, JMS=9239.]
    C:\oracle\jdk\bin\javaw.exe -ojvm -XXdebug,quiet,port2774 -classpath C:\oracle\j2ee\home\oc4j.jar com.evermind.server.OC4JServer -config C:\oracle\jdev\system\oc4j-config\server.xml
    Debugger attempting to connect to local process.[waiting for the server to complete its initialization...]
    Debugger unable to connect to local process. Go into the Tools > Preferences, and under Debugger, modify the "Connection Retry Setting" and increase the number of attempts.
    Hope this helps,
    Rob

  • I can't receive my incoming mail. ESP is yahoo.  Error msg says unable to connect with POP server.  Any solution?

    I can't receive my incoming mail in Mac Mail. ESP is yahoo.  Error msg says unable to connect with POP server.  Any solution?  I am able to get my incoming messages via yahoo website but not through the Mail app.

    Try this, if it is not the correct department, ask them for the number or to be transfered..
    Call 1-800-318-0612 for Login Help
    Also on most autmated systems, if you hit 00000, or ##### you can sometimes get thru to a person.
    Is Yahoo your Internet provider? Do you have  a local provider? ei:AT&T, SBC,  cable co, check who you make your check or epatment to...etc, If so I would start there, but if no joy go to the "Mothership"
    I may be wrong about this, (it's been a long time now) I may have deleted my mail account from Mail (after writing down all the info from all General/accounts, and the rest of the tabs, and then added a new account using my existing email address, and it may have "walked me thru the rest of the proceedure".
    But like I said it was a long time ago 3-4 years, but that may have been the path I ended up taking, make sure to write all the info down in case you need to re-enter it all manually. Then try calling them.
    All the best

  • UCCX 7 SR5 agent login gives timeout - unable to connect to UCCX server

    Team - running high availability. The CAD login for UCCX 7 SR5 gives occasionally timeout errors.
    Unable to connect to UCCX server. What is the root cause of this?
    on CAD client PC based on Cisco recommendation
    C:\Program Files\Cisco\Desktop\config, we changed PhoneDev.cfg.
    added ->
    [ReqTimeout]
    Milliseconds=30000
    While this helped it still happens. Is this a bug you have seen?
    What could be done for the root cause.

    Hello,
    This happens because the CAD client software is timing out due to not receiving a response from the UCCX server in the configured and default
    10 seconds. Increasing the timeout alleviates the symptom, but the root cause could be slowness or connectivity problems between CUCM and AD. The default timeout between them is 30 seconds. You can check if you have an DC/GC down or not responsive or point your CUCM to authenticate to a local DC/GC, but definitely need to check on the CUCM / AD side.
    CSCta49259    CAD client timeout value not present in PhoneDev.cfg
    Symptom:
    Per MIVR logs CAD side is timing out and changes to the server-side properties did not resolve the issue.
    Conditions:
    UCCX 7.0(1) CAD
    Workaround:
    on CAD client PC
    C:\Program Files\Cisco\Desktop\config, there should be a file
    called PhoneDev.cfg.
    add ->
    [ReqTimeout]
    Milliseconds=30000
    save then restart the CAD client .
    HTH
    Pablo

  • Unable to connect to local host

    Hi,
    I have 64 bit operating system and got installed SQL Server Management Studio of 64 bit and the problem I am facing is unable to connect to local host, I have database mdf/ldf files in my local system and unable to connect to local system
    tried localname/SQLEXPRESS and it did not work.

     SQL Server Management Studio is not enough, you also need to install SQL Server instance.
    http://www.orcsweb.com/blog/mark-newnam/how-to-install-sql-server-2012-express-edition/
    Keerthi Deep | Blog SQLServerF1 |
    Facebook

  • Error calling report FRM-41213 unable to connect to Report Server

    Hi,
    I have installed Oracle Database 10g R2 and Oracle Developer 10gR2.
    I installed it in both Windows 2000 SP4 and Windows XP SP2.
    I would like to call a Report using a button inside Oracle Form.
    I create my own Report Server, using : rwserver server=repsrv
    A Java-based window appear OracleAS Reports Sevice, and showed that repsrv is ready.
    In Form (inside a button -> WHEN-BUTTON-PRESSED) :
    1. Using RUN_REPORT_OBJECT()
       rep_id := find_report_object('REPORT10');
         if not id_null(rep_id) then
           v_rep := run_report_object(rep_id);
         else
              message('Null');
       end if;
       a. If I did not specify the name of the Report Server in Reports node of Form's property object
    (I leave it blank)
    The following error appear :
    FRM-41211: Integration error, SSL failure running another product
    b. If I specify the name of the Report Server : repsrv
    The following error appear :
    FRM-41213: Unable to connect to Reports Server repsrv
    2. Using WEB.SHOW_DOCUMENT()
    a. If did not I specify the server name in the parameter
    WEB.SHOW_DOCUMENT('http://localhost:8889/reports/rwservlet/getjobid'|| SUBSTR(v_rep,INSTR(v_rep,'_',-1)+1)||'?'||,'_blank');Another web browser appear and the following error appear :
    REP-51002: Bind to Reports Server rep_<computer_name> failed
    b. If I specify the server name in the parameter --> server='repsrv'
    WEB.SHOW_DOCUMENT('http://localhost:8889/reports/rwservlet/getjobid'|| SUBSTR(v_rep,INSTR(v_rep,'_',-1)+1)||'?'||'server=repsrv','_blank');Another web browser appear and the following error appear :
    REP-51002: Bind to Reports Server repsrv failed
    In Report :
    If I try to navigate manually to :
    1. http://localhost:8889/reports/rwservlet using web browser.
    It showed OracleAS Report Services - Servlet Command Help page.
    2. http://localhost:8889/reports/rwservlet?userid=scott/tiger@orcl&report=D:\PRACTICE\FORM\MODULE1.JSP&destype=cache&desformat=html
    The following error occured
    REP-51002: Bind to Reports Server rep_<computer_name> failed
    3. Finally,
    http://localhost:8889/reports/rwservlet?server=REPSRV&userid=scott/tiger@orcl&report=C:\PRACTICE\FORM\MODULE1.JSP&destype=cache&desformat=html
    The following error occured
    REP-51002: Bind to Reports Server repsrv failed
    4. Any attempt to different command (i.e showenv, showjobs, etc) seems failed
    If I did not specify the server then REP-51002: Bind to Reports Server rep_<computer_name> failed
    If I specify the server - 'repsrv' then REP-51002: Bind to Reports Server repsrv failed
    5. I have tried to use rwrun in command line.
    rwrun report="D:\My Documents\form\module1.jsp" userid=scott/tiger@orcl destype=file desformat=pdf desname="D:\My Documents\form\module2.pdf"
    The PDF file created and it looks exactly as the web layout as in Oracle Report Builder (Run Web Layout CTRL-R)
    Question :
    1. What supposed to be done?
    The Report server is ready, but the web browser seems unable to connect to Report Server.
    2. Can we used or call or executed an executable command line from Form (using PL/SQL inside button)?
    Any help would be grateful.
    Many thanks,
    Buntoro

    Hi,
    Problem solved.
    I got the solution from another post.
    Re: REP-51002: Bind to Reports Server rep failed
    Here are the step I did.
    Note : Please make backup for the following file : rwnetwork.conf
    - In file rwnetwork.conf, remove or commented the following
    <multicast channel="228.5.6.7" port="14021" timeout="1000" retry="3"/>
    - And then uncommented
    <namingService name="Cos" host="%NAMING_HOST%" port="%NAMING_PORT%"/>
    - replace the
    %NAMING_HOST% with your computer name or specify an IP address
    %NAMING_PORT% with 14021
    It should look like this :
    <namingService name="Cos" host="blahblah" port="14021"/>
    - I did not change the : name="Cos", since I do not understand what does it for
    - Save you changes.
    - Start the OC4J.
    - Find the location of : namingservice.bat (on Windows platform)
    - execute in the command line : namingservice.bat 14021
    - finally start the report in the web browser
    Note:
    To shutdown the namingservice, use : namingservice.bat 14021 shutdown
    Regards.
    Buntoro

  • There is a problem with the server's security certificate. The security certificate is not from a trusted certifying authority. SAP Business One is unable to connect to the server

    Hello,
    I have an issue with connecting client SB1H on Windows, the scenario is as follows:
    1.- Server:
         Suse Linux Enterprise Server 11.3 kernel version: 3.0.76-0.11 IBM
         NDB and Server are review 69 SP06
    2.- Client:
         Windows 8 Pro Virtual Machine on Microsoft Hyper-V
         SB1H PL 11 version 32bits    
         SAP HANA Studio version 1.0.60
    When I run SB1H the following message appears:
    There is a problem with the server's security certificate. The security certificate is not from a trusted certifying authority. SAP Business One is unable to connect to the server.
    Any idea what could be the solution?

    Hi,
    Please check SAP notes:
       1993392 - Server components setup wizard: New default values for certificates and single sign-on option
    1929288 - Do not configure SSL for XApp during installation or upgrade if XApp is installed on a different machine than the SAP HANA server
    Thanks & Regards,
    Nagarajan

  • I am wanting to update iphone to 4.3.3, however I am connected to the internet, yet itunes is telling me it is unable to connect to update server because i am not connected to the internet... please help

    I am wanting to update iphone to 4.3.3 software. however itunes is telling me it is unable to connect to update server as i am not connect to the internet. yet i clearly am connected... Please help

    Looks like I've asked a really old/common question - toonz posted the answer - I've copied it below.  Thanks toonz, everything now ok.
    Correct AnswerRe: Updating to 1.1.3                                                                        02-Feb-2008 23:19                                                    (in response to alibeau)                                       
                            You can fix this by following the steps in this article:
    http://docs.info.apple.com/article.html?artnum=304468                                                                   
                 Liked         (1)     

  • Unable to connect to SQL Server 2008 from OBIEE 11G(on 64 bit Linux box)

    We are unable to connect to connect to SQL Server 2008 from OBIEE 11G which is on 64 bit Red Hat Enterprise Linux.
    Infrastructure: OBIEE 11.1.1.5 64bit, on 64 bit Red Hat Linux Enterprise Linux 5.6 , MS SQL Server 2008 on 64 bit Microsoft Windows Server
    Issue Description: Unable to connect to SQL Server 2008 from OBIEE11G RPD
    Details: We are unable to connect to SQL Server 2008 from OBIEE which is on a 64 bit Linux box. We created the ODBC connection on Linux box to the SQL server. Whenever we try to import metadata it throws an error that says ‘Connection Failed’.
    Here are the steps we followed to setup the ODBC connection on Linux box.
    1) We updated the user.sh file with the LD_LIBRARY_PATH and LD_LIBRARY_PATH_64 values that point to $ORACLE_HOME/bifoundation/odbc/lib
    This is where we found the driver for SQL server SEmsss23.so.
    2) We updated the odbc.ini file with the entry for SQL server with the connection details
    SI_SQL_Server_DEV = SQL Server
    [SI_SQL_Server_DEV]
    Driver=/u001_OAS/Oracle/Middleware/Oracle_BI1/bifoundation/odbc/lib/SEmsss23.so
    Description=DataDirect 5.1 SQL Server Wire Protocol
    Address=10.230.216.52,54970
    AlternateServers=
    AnsiNPW=Yes
    ConnectionRetryCount=0
    ConnectionRetryDelay=3
    Database=SVBDW_NEW
    LoadBalancing=0
    LogonID=SIDatavalidation
    Password=~~~Password123
    QuoteID=No
    ReportCodePageConversionErrors=0
    3) We updated the IDENTIFIER_QUOTE_CHAR with single quotes instead of double quotes in the DB features of the RPD
    4) We updated the bash_profile file to point the ODBCINI variable to the path where the OBIEE odbc.ini file is present.
    Export ODBCINI=/u001_OAS/Oracle/Middleware/instances/instance1/bifoundation/OracleBIApplication/coreapplication/setup/odbc.ini
    The error in nqsserver.log file says “[nQSError: 16001] ODBC error state: IM002 code: 0 message: [DataDirect][ODBC lib] Data source name not found and no default driver specified.”

    Hi,
    Make sure SQL Configuration Manager make sure the TCP/IP enabled. please try below method
    Method 1
    Re Create a new ODBC & Oracle Bi Server DSN Configuration test it and use it in the connection pools.
    define your ODBC data source in your server where the BI Server is installed. Check your DB connections in your physical layer and make they are defined on your BI Server as well.
    Method 2:
    try using the complete TNS in below format in the datasource name section:
    (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP) (HOST =DB IP)(PORT = 1521)) ) (CONNECT_DATA = (SERVICE_NAME = ORCL) ) and provide the credentials.
    Method 3:
    To use the OCI call interface you need to have oracle client DB to be installed so that you can establish a connection using that DB credentials and connect to the remote dB and then import the tables.....this is the rule of thumb.
    hope helps you.
    Thanks
    Deva

  • Unable to connect to sql server database

    i run on CMD:
    aspnet_regsql -C "Data Source  =Davidchamoun/sqlexpress : intergrated security= true" -ssadd -sstype p
    i got 
    a network-related or instance-specific error occurred while establishing a connection to sql server. the server
    was not found or was not accessible. verify that the instance name is correct and that sql server is configured to allow remote connections. (provider: SQL Network interfaces . error: 25 – connection string is not valid
    unable to connect to sql server database.
    im using sql sever 2012 express, microsoft visual studio web 2008 express.
    please help me.

    i run it as :
    aspnet_regsql -C "Data Source =Davidchamoun\sqlexpress : integrated security= true" -ssadd -sstype p
    i got the same error :
    an error has occurred . details of the exception:
    a
    network-related or instance-specific error occurred while establishing a connection to sql server. the server was not found or was not accessible. verify that the instance name is correct and that sql server is configured to allow remote connections. (provider:
    SQL Network interfaces . error: 25 – connection string is not valid
    unable to connect to sql server database.
    im using also windows 8.1
    pls help me
    ty for ur reply

  • HP OfficeJet Pro 8500A Plus "unable to connect to the server"

    I have had this printer for a couple years and now it is saying it is unable to connect to the server.  The light under the wifi symbol is not lit up and nothing happens when I press that button.  
    I have restarted the printer, reinstalled the driver, restarted the router ... to no avail.
    The router is working properly as my 2 computers are both working.

    Hi bhappie,
    Welcome to the HP Support forums.  I gather that you are unable to connect your Officejet 8500A plus printer to your wireless network.
    This printer can be connected by an ethernet cable or connected to your wireless network but cannot support both simultaneously as referenced in the document The Printer Does Not Support Ethernet (Wired) and Wireless Network Connections at the Same Time.  To setup the wireless feature you will need to unplug the ethernet cable.  
    Your wireless printer can be easily connected to your wireless network from the front panel of your printer.  If you are unsure how to do this the instructions can be found in your User Guide on page 219 in the section titled “To set up a wireless communication using the Wireless Setup Wizard”.  
    Now that the printer has a wireless connection, any computer that uses the printer, will need to have the connection method updated.  The instructions on how to do this can also be found in your User Guide on page 221 in the section titled “Change the connection method”.  There is a sub-section dedicated to Windows operating systems and one dedicated to Mac operating systems.
    Regards,
    Happytohelp01
    Please click on the Thumbs Up on the right to say “Thanks” for helping!
    Please click “Accept as Solution ” on the post that solves your issue to help others find the solution.
    I work on behalf of HP

Maybe you are looking for