Documents not Opening, No connectivity with the server

Morning,
Strange problem we are encountering that seems to be with a specific image build we have of Windows 7 Enterprise x64, with and without Service Pack 1 using IE8 x32 and Office 2010 x64.  When we try to open Word, Excel, or specifically PowerPoint documents
on our new SharePoint 2010 server we get the following error: No connectivity with the server.
Here is a JPG of the error message:
http://www.gofsj.com/fsj/uploads/caa612c339cccaf12448e34a65c83d7d_erroropeningdocument.jpg
A "normal" install of Windows 7 Enterprise x64, with no custom configuration (but getting the domain group policies) can view the files on SharePoint 2010, no problems.  Unfortunately, we've already deployed the "odd" image out to 50+
machines.
We have tried resetting Internet Explorer, uninstalling Office 2010 x64 and installing Office 2010 x32 with no luck. 
What is really going on?  Is it a SharePoint plugin that isn't installed?  Is it Internet Explorer isn't configured correctly, or has DLLs that aren't registered?  Or something with Office 2010?  Is there a way to capture more than this
Error Message?  This is what pretty much stamps in the Event Viewer too...

This may be related to the Network and Sharing Center stating the computer is not connected to any network, and the Windows Firewall stating it is on a Public Network.  Even though the machine is connected and running on the LAN.
I added SERVICE with full control (and pushed it down to registry subkeys) on HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\NetworkList.  Then I Enabled/Disabled the LAN Adapter.  Could also reboot, or physically unplug the cable.  Not
sure if restarting a specific service would accomplish the same thing or not.
In the Network and Sharing Center it came up as on the domain.  Windows Firewall came up as being on a Domain.  And I was able to open PowerPoint and Excel documents on the SharePoint site. 
So for now, looks like this is fixed.

Similar Messages

  • Why does itune keep telling me it could not establish a connection with the software update server

    i have an iphone 3g running on 3.1.3 firmware and every time i plug into my pc running windows 7 it says that it is contacting the software update sever then after about ten seconds it says that update failed could not establish a connection with the server i have tried to disable my firewalls completely and it seems that nothing works nothing is wrong with the iphone it sync's properly and works fine someone plz help me so i can update

    Everybody is tryng to connect to apple,s servers. Try tomorrow, it will be quieter

  • "No connectivity with the server" error for one document but not the other, in the same document library

    We have a number of users all of a sudden getting "No connectivity with the server.  The file 'xxx' can't be opened because the server couldn't be contacted." errors trying to open MS Office docs (Word, Excel, etc.) in SharePoint with IE,
    just by clicking the link and selecting the "Read Only" option.  If they select the "Check Out and Edit" option, they can open the document no problem.  One of my customers gets the error on one document but not the other, in
    the same document library!  The older document (a weekly report) was copied and renamed as per standard procedure.  She can read the older document, but not the new one.
    It is definitely a profile issue, as other people have logged onto the machines of the users with problems and do not get the error.  We have also renamed people's c:\user profile folders and the corresponding Profilelist registry entry and the newly
    created profile does not experience the error for these people.  Renaming the profile back restores all their personal settings but the error reappears.  When we copied the old profile's folder structure into the new profile, many of the user settings
    were restored (but not all, like Dreamweaver settings) but the error did not appear.  We think that the system folders files (like AppData) weren't totally copied over so we're going to run another test using xcopy.  We are rebooting between
    logons to make sure all files are unlocked.
    The laptops and computers are mainly 32bit, Win7 Enterprise running IE9 and Office 2010 Professional Plus, but there's a few 64bit machines as well. The SharePoint farm has 1 WFE, 1 App Server running search and CA, and a shared database server running SQL
    2005 SP4.  SharePoint is 64bit MOSS 2007 with the latest CU.
    We've checked the logs on the client as well as on the server and there aren't any helpful entries.  We've also run Process Monitor, also with no helpful entries.  We're planning to run something like Fiddler next.
    It's not everyone, because there are many people are accessing the SharePoint system and the same files.  It is also not a permission thing, as we've tested by giving the users elevated permissions with no changes.  One person experiencing
    the errors is a Site Collection Admin.  That same person ran a test where I coped a simple Excel file into a Document Library which contained a problem file.  They were able to open it Read Only no problems that day, but the next day, the same
    file gave them an error.   In their case, they usually get a "xxx is not checked out" error and only occasionally get the "No connectivity with the server" error.
    We've tried lots of things including:
    Deleting IE cache
    Deleting SharePoint Drafts and webcache folder contents
    Running IE without add-ons
    Upgrading and Downgrading IE
    Uninstalling and re-installing IE
    Reinstalling our SSL certs
    Repairing Office
    Removing and then adding back in the Microsoft Office "Microsoft SharePoint Foundation Support" Office Tool 
    Deleting all HKLM and HKLU Office registry settings
    Toggling IE Compatibility Settings
    Toggling the IE Automatic Logon option
    Toggling the location of checked out files
    Adding the site in the trusted sites list
    Adding the site to the WebClient\Parameters registry locations
    Making sure the WebClient service is started
    Rebooting the machine (lol :)
    This is becoming a serious issue, not just because of the inconvenience for the users having to check out every document they want to read, but we have some files with macros that open up other documents to run which are now failing.  There aren't
    "check out" workarounds for some of those macros.
    We're planning to open a ticket with Microsoft, but I'm throwing it out here first in case someone has run into this before, or may have some suggestions on what to try next.  Thanks!
    -Richard.
    PS  I think this needs to be in the "General" forum instead?

    It took three days of dedicated troubleshooting, but I have found the cause of the errors, and a couple of fixes.  It helped tremendously that my own machine was throwing the error.  I have scheduled a couple of users to work with me to test the
    various fixes, to see which one works best, so the story isn't over yet.
    I had backed up my c:\users profile folder and HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList registry key so I could restore my profile after I was done.  I made a copy of the profile folder and was using that for awhile,
    but then made another copy where I had deleted a lot of content out of it so that the copies would go faster.  Since a newly created profile did not have errors, I was trying to copy back as much of the profile as possible to make it easier for our users
    to get back to work.  Instead of blowing away their profile and starting from scratch (which we know worked) I wanted to narrow down what was causing the error and just skip that from the restore.  The concept was to keep as much as the users profile
    in tact (application settings, etc.) not just restoring their desktop and My Documents folders.
    When we first tested a few weeks ago, simply copying the folder contents didn't reproduce the error.  I then tried xcopy, but got the "can't read file" error.  Then I tried robocopy, and ran into the "junction" problem. 
    I went back to xcopy, and found that placing the excludes.txt file in the windows/system32 folder eliminated the error.
    So the process went as follows: 
    Reboot and log into the machine as another user
    Delete the profile and associated registry key
    Reboot and log into the machine as the affected user, creating a new profile, and there is no error
    Reboot and log in as the other user
    xcopy the contents of the skinned-down backed-up profile to the newly created profile
    Reboot and log in as the affected user, and the error occurs
    Repeat the above, but add items in the excludes.txt file to see what, when eliminated, causes the error not to appear in the last step
    I eventually found that skipping the c:\users\<profile folder>\appdata\local\Microsoft\office\14.0 folder allowed the entire profile to be copied over without the error occurring.  That was strange, because we've cleaned out the cache folders
    before which didn't fix the issue. 
    So I went about it the opposite way, and tried to delete the 14.0 folder from the restored profile, and after reboot, the error still occurred.
    What eventually worked was deleting the 14.0 folder and copying over a 14.0 folder from a newly created profile!
    One way to do this was to:
    Reboot and log in as another user
    Rename the c:\users profile folder
    Rename the appropriate [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\ProfileList] registry key
    Reboot and log in as the affected user, confirm that there is no error
    Reboot and log in as the other user
    Copy the C:\Users\<profile folder>\AppData\Local\microsoft\Office\14.0 folder to the other user's desktop
    Delete new profile folder, and rename the backup to be the production folder
    Delete the C:\Users\<profile folder>\AppData\Local\microsoft\Office\14.0 folder and then paste the 14.0 copy from the desktop
    Reboot and log in as the affected user, confirm that there is no error
    We've tried this on a couple machines and it works.  I had to run Windows Explorer as Administrator to access the other profile's folders.
    We've also successfully copied a 14.0 folder created by one profile on one affected computer over another profile's folder on another computer, eliminating the error, so we're trying that first, as that is fewer steps.
    We may attempt to script this, but the self-help instructions are only 5 lines long:
    Reboot and log into the affected computer with another account
    Go to <link to location of 14.0 folder on network> and copy the 14.0 folder
    Run Windows Explorer as Administrator
    Go to c:\users\<profile folder>\appdata\local\microsoft\office and delete the 14.0 folder, and paste the copied 14.0 folder (trying to overwrite it makes Win7 want to merge the folders)
    Reboot and log into your normal account, and confirm the error is gone
    I'll come back and report after we go into the field with this fix, but after the few tests, I am cautiously optimistic that this is it.

  • Named Pipes provider, error:40 could not open a connection to sql server. Only happens on one of the front end SRS servers

    when testing a datasource connection I get the following error.
    Named Pipes provider, error:40 could not open a connection to sql server.
    I've read all the posts on this and nothing works.  This is a scale out deployment and the connection
    works from the other server I have setup with SRS that is connected to the same backend SRS databases.  It just doesn't work from one of the SRS front ends.  I'm at a loss..  please help

    Enable both named pipe and TCP communications.
    Make sure client is using the same (named) pipe name as server for connection.
    Kalman Toth Database & OLAP Architect
    Free T-SQL Scripts
    New Book / Kindle: Exam 70-461 Bootcamp: Querying Microsoft SQL Server 2012

  • HT5085 hi, i bought itunes match yesterday, and i can not connect with the server. Error 4010 appear ever time when i want to entry on Itunes match.Thanks

    i bought itunes match yesterday and i can not connect with the server. Error 4010 appear every tiem when i want to entry on itunes match.
    Thanks

    Here are some things to try:
    Close itunes
    Check your internet settings.
    Control Panel – Internet Options – Advanced
    Check SSL 3.0 and TLS 1.0
    Uncheck “Check for server certificate revocation (requires restart)”
    Click Apply
    Click Okay
    Open itunes and try again
    And, you don't need to turn off the firewall, just add itunes and itunes helper to your security software firewall.

  • Hyper-V could not replicate changes for virtual machine 'machinename': The connection with the server was terminated abnormally (0x00002EFE).

    I have a 3 node cluster that has replica setup to replicate to another cluster off-site.
    Suddenly one of the servers is not replicating with the error:
    Hyper-V could not replicate changes for virtual machine 'machinename': The connection with the server was terminated abnormally (0x00002EFE). (Virtual Machine ID CC0FD4CC-F9B7-4C68-ABE8-B7D52A87899F)
    All other servers are replicating fine so there cannot be a permissions or connectivity issue between the 2 clusters.
    This server has 2TB of data so I'd rather not have to start the replication again.
    Does anyone have any pointers?
    Thanks.

    Hi drensta,
    Based on my knowledge , "hyper-v replica broker " is needed for failover cluster replica .
    Here is a link for "Why is the "Hyper-V Replica Broker" required?"
    http://blogs.technet.com/b/virtualization/archive/2012/03/27/why-is-the-quot-hyper-v-replica-broker-quot-required.aspx
    Hope this hleps
    Best Regards
    Elton Ji
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • VPN Issue:  Could not Negotiate a connection with the remote PPP server

    Hello Folks,
    I setup VPN on Windows Server 2003 Enterprise R2. I am successfully able to connect to VPN via laptop internally and externally. However, on my iPhone I am not able to connect and receiving the following error "Could not Negotiate a connection with the remote PPP server".
    There doesnt seem to be a lot of documentation regarding this on Apple and or throughout the web.
    Anyone resolve this issue?
    Peace
    Phil C.

    I am not entirely sure my full setup. I had a friend help me set it up. Now for some reason when on WIFI on my own network I am able to connect to VPN ( I wasnt able to before), but when I switch to edge there is still no response for the PPP server. I even messed around with the PPP options still no response. Unfortunately I am not extremely server literate so my troubleshooting is limited. However it is now working via my own WIFI and will try it on another WIFI network tomorrow. I am wondering though if it connecting had to do with any updates from microsoft. Since this is a newly installed server 2003 it has been running updates. Some food for thought.
    Peace
    Phil

  • Named Pipes Provider: Could not open a connection to SQL Server

    We are running into an error on a SQL request from SQL-IDA to the SQL-IDB server. Both servers are on Windows 2005 with MS SQL Server 2003 SP3.
    OLE DB provider "SQL-IDA" for linked server "SQL-IDB" returned message "Login timeout
    expired".
    OLE DB provider "SQL-IDA" for linked server "SQL-IDB" returned message "An error has
    occurred while establishing a connection to the server. When connecting to SQL Server 2005,
    this failure may be caused by the fact that under the default settings SQL Server does not
    allow remote connections.".
    Msg 53, Level 16, State 1, Line 0
    Named Pipes Provider: Could not open a connection to SQL Server [53].
    It seems to suggest that SQL-IDA cannot find the network path to SQL-IDB. We've followed the steps in this article http://support.microsoft.com/default.aspx?scid=kb;EN-US;914277 but it did not resolve our issue. Is it possible that the MSDTC dynamic port range
    should be set to a specific range on both servers?
    Any help is greatly appreciated.
    Albert

    Hi Albert,
    Can you try to use the SQL Server Management Studio on server ‘SQL-IDA’ to connect to the instance on server ‘SQL-IDB’ to see if it works or not?
    There are possible reasons to error 53:
     a) typo in the server name, or using "/" rather than "\" between server name and instance name, e.g. "myserver/myinst" is not correct.
     b) name resolution to the server name is not correct, "ping -a yourserver" would tell if that's the case
     c) The server machine is firewall'ed and file sharing is not in the exception list. You need put "File and Printer Sharing" in exception.
    For more information:
    Named Pipes Provider, error: 40 - Could not open a connection to SQL Server (Microsoft SQL Server, Error: XXX).
    TechNet Subscriber Support
    If you are
    TechNet Subscription user and have any feedback on our support quality, please send your feedback
    here.
    Stephanie Lv
    TechNet Community Support

  • Dispatcher stopped and not able to connect with sql server

    Hi ,
                       In one of test system disp+work is started and then within no time its stopped.
    I am able to connect with  sql server 2005 database but while starting sap  dispatcher is stopping.
    Here is the log of  dev_wo
    trc file: "dev_w0", trc level: 1, release: "700"
    ACTIVE TRACE LEVEL           1
    ACTIVE TRACE COMPONENTS      all, MJ

    B Thu Jan 05 07:24:02 2012
    B  create_con (con_name=R/3)
    B  Loading DB library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' ...
    B  Library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' loaded
    B  Version of 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' is "700.08", patchlevel (0.72)
    B  New connection 0 created
    M sysno      11
    M sid        DE1
    M systemid   560 (PC with Windows NT)
    M relno      7000
    M patchlevel 0
    M patchno    75
    M intno      20050900
    M make:      multithreaded, Unicode, optimized
    M pid        988
    M
    M  kernel runs with dp version 217000(ext=109000) (@(#) DPLIB-INT-VERSION-217000-UC)
    M  length of sys_adm_ext is 572 bytes
    M  ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 988) [dpxxdisp.c   1299]
    I  MtxInit: 30000 0 0
    M  DpSysAdmExtCreate: ABAP is active
    M  DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
    M  DpShMCreate: sizeof(wp_adm)          23936     (1408)
    M  DpShMCreate: sizeof(tm_adm)          3994272     (19872)
    M  DpShMCreate: sizeof(wp_ca_adm)          24000     (80)
    M  DpShMCreate: sizeof(appc_ca_adm)     8000     (80)
    M  DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
    M  DpShMCreate: sizeof(comm_adm)          528064     (1048)
    M  DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
    M  DpShMCreate: sizeof(file_adm)          0     (72)
    M  DpShMCreate: sizeof(vmc_adm)          0     (1440)
    M  DpShMCreate: sizeof(wall_adm)          (38456/34360/64/184)
    M  DpShMCreate: sizeof(gw_adm)     48
    M  DpShMCreate: SHM_DP_ADM_KEY          (addr: 07F90040, size: 4659000)
    M  DpShMCreate: allocated sys_adm at 07F90040
    M  DpShMCreate: allocated wp_adm at 07F91E40
    M  DpShMCreate: allocated tm_adm_list at 07F97BC0
    M  DpShMCreate: allocated tm_adm at 07F97BF0
    M  DpShMCreate: allocated wp_ca_adm at 08366E90
    M  DpShMCreate: allocated appc_ca_adm at 0836CC50
    M  DpShMCreate: allocated comm_adm at 0836EB90
    M  DpShMCreate: system runs without file table
    M  DpShMCreate: allocated vmc_adm_list at 083EFA50
    M  DpShMCreate: allocated gw_adm at 083EFA90
    M  DpShMCreate: system runs without vmc_adm
    M  DpShMCreate: allocated ca_info at 083EFAC0
    M  DpShMCreate: allocated wall_adm at 083EFAC8
    X  EmInit: MmSetImplementation( 2 ).
    X  MM global diagnostic options set: 0
    X  <ES> client 0 initializing ....
    X  Using implementation flat
    M  <EsNT> Memory Reset disabled as NT default
    X  ES initialized.

    M Thu Jan 05 07:24:03 2012
    M  ThInit: running on host sugarland

    M Thu Jan 05 07:24:04 2012
    M  calling db_connect ...
    C  Warning: Env(MSSQL_SERVER) [SUGARLAND\DE1] <> Prof(dbs/mss/server) [SUGARLAND]. Profile value will be used.
    C  Thread ID:708
    C  Thank You for using the SLOLEDB-interface
    C  Using dynamic link library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll'
    C  dbmssslib.dll patch info
    C    patchlevel   0
    C    patchno      72
    C    patchcomment MSSQL: Thread check in DbSlDisconnect (969143)
    C  np:(local) connection used on SUGARLAND
    C  CopyLocalParameters: dbuser is 'de1'
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:24:19 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:24:34 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:24:49 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  failed to establish conn to np:(local).
    C  Retrying without protocol specifier: (local)
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:25:05 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:25:21 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  Using Provider SQLNCLI
    C  OpenOledbConnection: MARS property was set successfully.

    C Thu Jan 05 07:25:37 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  failed to establish conn. 0
    B  ***LOG BY2=> sql error 0      performing CON [dbsh#2 @ 1204] [dbsh    1204 ]
    B  ***LOG BY0=> <message text not available> [dbsh#2 @ 1204] [dbsh    1204 ]
    B  ***LOG BY2=> sql error 0      performing CON [dblink#3 @ 431] [dblink  0431 ]
    B  ***LOG BY0=> <message text not available> [dblink#3 @ 431] [dblink  0431 ]
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1411]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10156]

    M  Info for wp 0

    M    stat = 4
    M    reqtype = 1
    M    act_reqtype = -1
    M    rq_info = 0
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = 65535
    M    rq_source = 255
    M    last_tid = 0
    M    last_mode = 0
    M    semaphore = 0
    M    act_cs_count = 0
    M    control_flag = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M    vm = V-1

    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server sugarland_DE1_11 on host sugarland (wp 0)
    M  *  ERROR       ThInit: db_connect
    M  *
    M  *  TIME        Thu Jan 05 07:25:37 2012
    M  *  RELEASE     700
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          13
    M  *  MODULE      thxxhead.c
    M  *  LINE        10354
    M  *  COUNTER     1
    M  *
    M  *****************************************************************************

    M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   720]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  260]
    M  Entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  Entering ThReadDetachMode
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 988) [dpnttool.c   327]
    Please help me on this
    Thanks
    Srikanth

    Hi Amit, 
                 I restarted the system but dispatcher still in same stage.
    Here is the log for dev_w0
    ========================================
    Fri Jan 06 03:41:06 2012
    C  OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
    C  Procname: [OpenOledbConnection - no proc]
    C  sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
    C  Procname: [OpenOledbConnection - no proc]
    C  failed to establish conn. 0
    B  ***LOG BY2=> sql error 0      performing CON [dbsh#2 @ 1204] [dbsh    1204 ]
    B  ***LOG BY0=> <message text not available> [dbsh#2 @ 1204] [dbsh    1204 ]
    B  ***LOG BY2=> sql error 0      performing CON [dblink#3 @ 431] [dblink  0431 ]
    B  ***LOG BY0=> <message text not available> [dblink#3 @ 431] [dblink  0431 ]
    M  ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c   1411]
    M  in_ThErrHandle: 1
    M  *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c   10156]

    M  Info for wp 0

    M    stat = 4
    M    reqtype = 1
    M    act_reqtype = -1
    M    rq_info = 0
    M    tid = -1
    M    mode = 255
    M    len = -1
    M    rq_id = 65535
    M    rq_source = 255
    M    last_tid = 0
    M    last_mode = 0
    M    semaphore = 0
    M    act_cs_count = 0
    M    control_flag = 0
    M    int_checked_resource(RFC) = 0
    M    ext_checked_resource(RFC) = 0
    M    int_checked_resource(HTTP) = 0
    M    ext_checked_resource(HTTP) = 0
    M    report = >                                        <
    M    action = 0
    M    tab_name = >                              <
    M    vm = V-1

    M  *****************************************************************************
    M  *
    M  *  LOCATION    SAP-Server sugarland_DE1_11 on host sugarland (wp 0)
    M  *  ERROR       ThInit: db_connect
    M  *
    M  *  TIME        Fri Jan 06 03:41:06 2012
    M  *  RELEASE     700
    M  *  COMPONENT   Taskhandler
    M  *  VERSION     1
    M  *  RC          13
    M  *  MODULE      thxxhead.c
    M  *  LINE        10354
    M  *  COUNTER     1
    M  *
    M  *****************************************************************************

    M  PfStatDisconnect: disconnect statistics
    M  Entering TH_CALLHOOKS
    M  ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
    M  *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c   720]
    M  *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c  260]
    M  Entering ThSetStatError
    M  ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
    M  Entering ThReadDetachMode
    M  call ThrShutDown (1)...
    M  ***LOG Q02=> wp_halt, WPStop (Workproc 0 3632) [dpnttool.c   327]

  • I have a ipad mini and it says that it has perect wifi yet when i go into safari it says unable to connect with the server how can i fix this?

    I have a ipad mini and i have had it for less then a year, it says that i have perfect wifi up in the left corner where the wifi is always at  but when ever i go into the built in safari it says that it is unable to connect with the server. How can i fix this because with out it connecting to the server or internet it is kind of useless to me. I do have ios7 if that helps

    The wifi symbol only indicates the presence/signal strength of wifi. Not that you are connected.
    Some things to try first:
    1. Turn Off your iPad. Then turn Off (disconnect power cord for 30 seconds or longer) the wireless router & then back On. Now boot your iPad. Hopefully it will see the WiFi.
    2. Go to Settings>Wi-Fi and turn Off. Then while at Settings>Wi-Fi, turn back On and chose a Network.
    3. Change the channel on your wireless router (Auto or Channel 6 is best). Instructions at http://macintoshhowto.com/advanced/how-to-get-a-good-range-on-your-wireless-netw ork.html
    4. Go into your router security settings and change from WEP to WPA with AES.
    5.  Renew IP Address: (especially if you are droping internet connection)
        •    Launch Settings app
        •    Tap on Wi-Fi
        •    Tap on the blue arrow of the Wi-Fi network that you connect to from the list
        •    In the window that opens, tap on the Renew Lease button
    6. Potential Quick Fixes When Your iPad Won’t Connect to Your Wifi Network
    http://ipadinsight.com/ipad-tips-tricks/potential-quick-fixes-when-your-ipad-won t-connect-to-your-wifi-network/
    ~~~~~~~~~~~~~~~~~~~~~~~~~
    Fix WiFi Issue for iOS 7
    http://ipadnerds.com/fix-wifi-issue-ios-7/
    Fix WiFi Issue for iOS 7
    http://ipadnerds.com/fix-wifi-issue-ios-7/
    iOS 6 Wifi Problems/Fixes
    Wi-Fi Fix for iOS 6
    https://discussions.apple.com/thread/4823738?tstart=240
    How To: Workaround iPad Wi-Fi Issues
    http://www.theipadfan.com/workaround-ipad-wifi-issues/
    Another Fix For iOS 6 WiFi Problems
    http://tabletcrunch.com/2012/10/27/fix-ios-6-wifi-problems-ssid/
    Wifi Doesn't Connect After Waking From Sleep - Sometimes increasing screen brightness prevents the failure to reconnect after waking from sleep. According to Apple, “If brightness is at lowest level, increase it by moving the slider to the right and set auto brightness to off.”
    Fix For iOS 6 WiFi Problems?
    http://tabletcrunch.com/2012/09/27/fix-ios-6-wifi-problems/
    Did iOS 6 Screw Your Wi-Fi? Here’s How to Fix It
    http://gizmodo.com/5944761/does-ios-6-have-a-wi+fi-bug
    How To Fix Wi-Fi Connectivity Issue After Upgrading To iOS 6
    http://www.iphonehacks.com/2012/09/fix-wi-fi-connectivity-issue-after-upgrading- to-ios-6.html
    iOS 6 iPad 3 wi-fi "connection fix" for netgear router
    http://www.youtube.com/watch?v=XsWS4ha-dn0
    Apple's iOS 6 Wi-Fi problems
    http://www.zdnet.com/apples-ios-6-wi-fi-problems-linger-on-7000004799/
    ~~~~~~~~~~~~~~~~~~~~~~~
    How to Boost Your Wi-Fi Signal
    http://ipad.about.com/od/iPad_Troubleshooting/a/How-To-Boost-Your-Wi-Fi-Signal.h tm
    Troubleshooting a Weak Wi-Fi Signal
    http://ipad.about.com/od/iPad_Troubleshooting/a/Troubleshooting-A-Weak-Wi-Fi-Sig nal.htm
    How to Fix a Poor Wi-Fi Signal on Your iPad
    http://ipad.about.com/od/iPad_Troubleshooting/a/How-To-Fix-A-Poor-Wi-Fi-Signal-O n-Your-iPad.htm
    iOS Troubleshooting Wi-Fi networks and connections  http://support.apple.com/kb/TS1398
    iPad: Issues connecting to Wi-Fi networks  http://support.apple.com/kb/ts3304
    WiFi Connecting/Troubleshooting http://www.apple.com/support/ipad/wifi/
    How to Fix: My iPad Won't Connect to WiFi
    http://ipad.about.com/od/iPad_Troubleshooting/ss/How-To-Fix-My-Ipad-Wont-Connect -To-Wi-Fi.htm
    iOS: Connecting to the Internet http://support.apple.com/kb/HT1695
    iOS: Recommended settings for Wi-Fi routers and access points  http://support.apple.com/kb/HT4199
    How to Quickly Fix iPad 3 Wi-Fi Reception Problems
    http://osxdaily.com/2012/03/21/fix-new-ipad-3-wi-fi-reception-problems/
    iPad Wi-Fi Problems: Comprehensive List of Fixes
    http://appletoolbox.com/2010/04/ipad-wi-fi-problems-comprehensive-list-of-fixes/
    Connect iPad to Wi-Fi (with troubleshooting info)
    http://thehowto.wikidot.com/wifi-connect-ipad
    10 Ways to Boost Your Wireless Signal
    http://www.pcmag.com/article2/0,2817,2372811,00.asp
    Fix iPad Wifi Connection and Signal Issues  http://www.youtube.com/watch?v=uwWtIG5jUxE
    Fix Slow WiFi Issue https://discussions.apple.com/thread/2398063?start=60&tstart=0
    How To Fix iPhone, iPad, iPod Touch Wi-Fi Connectivity Issue http://tinyurl.com/7nvxbmz
    Unable to Connect After iOS Update - saw this solution on another post.
    https://discussions.apple.com/thread/4010130
    Note - When troubleshooting wifi connection problems, don't hold your iPad by hand. There have been a few reports that holding the iPad by hand, seems to attenuate the wifi signal.
    Some Wi-Fi losses may stem from a problematic interaction between Wi-Fi and cellular data connections. Numerous users have found that turning off Cellular Data in Settings gets their Wi-Fi working again.
    You may have many apps open which can possibly cause the slowdown and possibly the loss of wifi. In iOS 4-6 double tap your Home button & at the bottom of the screen you will see the icons of all open apps. Close those you are not using by pressing on an icon until all icons wiggle - then tap the minus sign. For iOS 7 users, there’s an easy way to see which apps are open in order to close them. By double-tapping the home button on your iPhone or iPad, the new multitasking feature in iOS 7 shows full page previews of all your open apps. Simply scroll horizontally to see all your apps, and close the apps with a simple flick towards the top of the screen.
    Wi-Fi or Bluetooth settings grayed out or dim
    http://support.apple.com/kb/TS1559
    ~~~~~~~~~~~~~~~
    If any of the above solutions work, please post back what solved your problem. It will help others with the same problem.
     Cheers, Tom

  • Re: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

    Hi,
    I'm encountering an issue with "Named Pipes Provider, error: 40 windows" and am having problems determining how to fix it due to the environment I'm using.  I have two SQL Servers installed on two separate Win2K3 Server boxes, one is SQL Server 2000 and the other is SQL Server 2005.  The SQL Server 2000 contains the actual application data.  The 2005 database is used only for Reporting Services.  I've set up the reports on SSRS such that their datasources hit the 2000 server.  This is using SQL Server authentication.
    When testing the reports via SSRS (in Visual Studio 2005), the connection to the data works and the reports are generated fine.  When I deploy them to the reporting server and launch IE to test locally (still on the 2005 box), I get this "Named Pipes Provider, error 40" issue.  I made sure that Named Pipes and TCP were enabled and the port set at 1433 (to match that on the 2000 box). 
    Now I changed the datasource's authentication from SQL Server to Windows authentication.  I tested this in SSRS and this works too.  When I redeployed the reports with this authentication change, testing the reports via IE locally (on the 2005 box) worked.  Great.  Now when I open IE on an external box, i.e. on the 2000 box, and try to test the reports, I get this same error 40 issue.  I've been through a few threads describing the error 40, fiddling around with the SQL Server configuration as well as SSRS, to no avail.  I have a feeling this error 40 issue has to due with permissions/authentication between the SQL Server boxes but I can't really be sure.  Anyone have any ideas on how to troubleshoot my situation.  Thanks.
    larry

    Named Pipes Provider, error: 40 - Could not open a connection to SQL Server :
    I.   Incorrect connection string, such as using SqlExpress.
    Check out: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=558456&SiteID=17
                    https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1245564&SiteID=1
    The typical error when dealing with Express includes:
    a.  User is not aware of SqlExpress was installed as a named instance, consequently, in his/her connection string, he/she only specify ".","localhost" etc instead of ".\SqlExpress" or "<machinename>\Sqlexpress".
    b. Np was disabld by default after installing SqlExpress.
    c. If Sqlexpress was installed on the remote box, you need to enable remote connection for Express.
    Please read the following blog for best practice of connecting to SqlExpress.
    http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
    II. Named Pipes(NP) was not enabled on the SQL instance.
    Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=136253&SiteID=1
    Oppose to SQL 2000 which turn on all protocols, SQL 2005 SKUs turn off NP by default. So, when you see this error, please check:
    1) Go to SQL Server Configuration Manager, See Server has NP enabled.
    2) %windir%\program files\microsoft sql server\mssql.1\mssql\log, notepad ERRORLOG, see whether Server is listening on NP.  You should see "Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ] or [\\.\pipe\mssql$<InstanceName>\sql\query]"
    3) Notice that "sql\query" is the default pipe name, so you need to know server is listening on which pipe name. eg: if you specify server pipe name is "sql\query1", then you would see in the errorlog that server listening on [ \\.\pipe\sql\query1 ], and go to SQL Server Configuration Manager, click client Named Pipe properties, see whether the pipe name is same with the one server listening on.
    4) If you are using SQL Native Client ODBC/OLEDB provider({SQL Native Client} or SQLNCLI), go to SQL Configuration Manager, click client protocols, make sure NP and TCP are both enabled. Right click properties of NP, make sure client is using the same pipe name as server for connection.
    5) If you are using MDAC ODBC/OLEDB({SQL Server} or SQLOLEDB) provider, in command line, launch "cliconfg.exe" and make sure NP enabled and right pipe name specified.
    III. Remote connection was not enabled. 
    Check out: when you right click on the Server in SQL Server Management Studio, in Connections, the Remote server connections part, you have enabled the "Allow remote connections to this server" check box
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322792&SiteID=1
    https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=763875&SiteID=1
    If you are making a remote connection, namely, your target SQL Server is on the different box as client application, you might need to check whether:
    a. "File and Printer Sharing" was opened in Firewall exception list.
    b. Please see the blog for enabling remote connection for express and troubleshooting tips of remote connection.
    http://blogs.msdn.com/sql_protocols/archive/2005/11/14/492616.aspx
    http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
    IV. Server not started, or point to not a real server in your connection string.
    Check out: Open SQL Server Surface Area Configuration and ensure all the required services are started, Remote Connections are configured.
    http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=348662&SiteID=1
    a. use "sc query mssqlserver" for default instance or "sc query mssql$<instancename>" to make sure SQL Server was started. Sometimes, reseason behind the broken of your client application w/ this error:40 might be SQL server restarted and failed, so, it'd better for you to double check.
    b. User specified wrong server in their connection string, as described in the forum discussion, "MSSQLSERVER" is an invalid instance name. Remember, when you connect to default instance, <machinename> could be best representitive for the instance, when you connect to a named instance such as sqlexpress, you should specify <machinename>\<instancename> as data source in your connection string.
     V. Other reasons such as incorrect security context.
    Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=192622&SiteID=1
    Such error also occured during user operation such as moving database or db mirroring or cluster, any DB OP that might invovle different sql instances, namely, the destination database is located in another sql instance and user is not aware of the state of the destination. I recommend you first isolate whether this fail is during connection stage or data operation stage.
    a. During data operation, you are normally asked to type in the destination server name whether it is default to "(local)" or another server "<remotemachinename>". So, remember the exact string that represent the target instance, then when the error repros, open command line, use "sqlcmd -S<representitive> -E" ,see what happens, if the connection fail, please follow up above I - IV troubleshooting lists. otherwise continue.
    b. If you can make basic conection, but still face the error, then there must be something that server reject the connection or client close the connection for some reason.
    VI. Please try basic connectivity tests between the two mahcines you are working on. One simple way to verifty connectivity is to use command line tools, such as osql.exe. For example, osql -E -Stcpervername\instancename. If it connects cross-machine successfully, please also verify that your connection string in your scenario is correct.
    Here are some blogs which could be helpful: just follow the basic connectivity troubleshooting guidelines on the SQL Protocols blog, see:
    SQL Server 2005 Connectivity Issue Troubleshoot - Part I
    http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
    and
    SQL Server 2005 Connectivity Issue Troubleshoot - Part II
    http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
    Hope this helps.

  • Linked Server "Could not open a connection to SQL Server [1909]" after reboot

    We have two production servers, with RCP [out] enabled linked servers set up back and forth between them. When they are rebooted at the same time one of the linked servers will throw this error:
    Named Pipes Provider: Could not open a connection to SQL Server [1909]. 767462021 OLE DB provider "SQLNCLI10" for linked server "server3" returned message "Login timeout expired".
    OLE DB provider "SQLNCLI10" for linked server "server3" returned message "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and
    if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
    I've been fixing it by dropping and re-creating the linked server. It's completely identical as before (in sp_linkedservers), so I'm thinking this shouldn't be necessary. My guess is it's only happening because during startup the other server was not available.
    If this is true, can I force a reset of the linked server, without having to restart the server instance, or recreate the linked server?

    Hi Chuck, thanks for the reply. Both servers were already set to 20. I think this might work if in the ensuing 10 seconds the other server happened to come on line.  I could also set it to 60, but then production queries would be waiting 60 seconds
    for timeout.  I'm really after a cause and solution. It's as though the server tries once, sees that the other server is unavailable, and henceforth refuses to try again. I'd like it to try again. Really, it should try every time.
    Could it be that upon startup SQL Server looks for all its linked servers and marks ones it can't reach in that moment as forever invalid?  I'm sure this doesn't happen after startup, only during.

  • Could not open a connection to SQL Server[2]

    There is a universe which is already created and now I added one table and one join to it but when I create a WEBI report based off the same universe, I am getting below error from launch pad.
    Database error: [Microsoft SQL Server Native Client 10.0] :
    Named Pipes Provider:Could not open a connection to SQL Server[2]..
    (IES 10901)(Error:INF)
    I checked all posts from scn but it seems this code [2] is unique while [53] was posted
    Environment:
    BI 4.1 SP03
    SQL server 2005.

    Hi
    Take a look at this - looks like someone fixed their issue with that error:
    http://www.forumtopics.com/busobj/viewtopic.php?t=156738
    Regards,
    Mark

  • Named Pipes Provider: Could not open a connection to SQL Server [2]

    Hi
    I'm a complete sql/asp.net newbie and want to try this tutorial:
    http://beta.asp.net/GuidedTour/
    First I installed:
    Visual Web Developer 2005 Express Edition Beta 2
    systemsettings\software shows the "sql server 2005 express edition ctp (sqlexpress)" installed
    mmc\service shows me the SQL Server (SQLExpress) is running
    Following the guided tour I use the commandline, type cmd, and type in the commandbox:
    "C:\Program Files\Microsoft SQL Server\90\Tools\binn\SQLCMD90" -S "localhost\SqlExpress"
    Instead of localhost I also tried computername.smallbusiness.local (thats my fully domain name).
    However I always receive the error:
    Named Pipes Provider: Could not open a connection to SQL Server [2]
    Thank you very much for all your help

    Typically I have found problems with connection strings as one of a few things:
    1. Your instance is named different than the default.  I labeled mine BrettSQLServer instead of the regular instance.
    2. Your default storage of the your database has a user the system does not like and won't give it access.
    3. You have ports blocked that SQL Server is trying to access.
    1. Your instance should show up under 'SQL Server Configuration Manager'.  Start>MS SQL Server 2008 > Configuration Tools> SQL Server Configuration Manager.  You should see a left view panel where you can click 'SQL Server Services'.  This
    will show on the right all of your SQL services that are running.  The most important one is SQL Server({Your SQL Server Name}).  You will see column headers's displaying: "Name, State, Start Mode, Log on as,  ProcessID" by default.  If
    you don't see a version of this you may have no installed SQL server properly and gotten SQL management studio but not the server.  If you have the server and it's off or not running that is another problem.  If your "LOG On AS" is a service account
    is "NT ...." or something besides "Local System" that may be a problem.  Without getting into the symantecs of protection suffice to say you log in with less than system, yes you are more secure but some built in functions for connections may not work.
    2. Going off of rights of your 'Log On As' I WOULD USE 'System' NOT "NT Authority....".  The reason is that you can access less things with 'NT Authority....' but yes you are more secure for that reason.  If you are just trying to connect at home
    to test non secure things I don't see the harm.  If you are setting up a database for a multinational corporation than, Yes I would use a more secure account.  If you need to change it while still in SQL Server Confi Manager: Right Click> SQL
    Server(Your Version) > On 'Log On' tab > Choose drop down for 'Built-in Account' select 'Local System'.  As extra steps make sure by some strange reason your database locales have this user by default(They should).  MS likes to install database
    as default to: C:\Program Files\Microsoft SQL Server\MSSQL10.{instanceName}\MSSQL.  If you go to this location by going: right click>Properties>Security Tab .. and you fail to see your user that SQL server is defined as you may have lots of
    issues.
    3. Turn off Windows Firewall during SQL installation.  If you are scared of being attacked during this down window, disconnect your NIC and reconnect later.  I have not added a port manually in a while but it is simply easier to just
    turn off your firewall during install.  Having your TCP/IP connection from SQL Server blocked is kind of bad if you need to connect to it that way later.
    Problems most commonly encountered with SQL Server by users I have seen and I myself encountered a lot with full blown SQL Server Enterprise as well as Express versions of SQL:
    Connection string DO not work for BIDS, ADO.net, Linq, etc...
    Once you follow steps above just go {ComputerName}\{SQL Server Instance} as your connection name.   That mostly always works.  As a preliminary test you should install SQL Management Studio first before doing connection strings for a basic test
    that it can access your server.  When you first boot it up and click 'New Database Engine Query' it will display Server Type: "Database Engine" and a blank field or autopopulated field for 'Servername'.  The {ComputerName}\{SQL Server Instance} almost
    always works.  If it works and you can connect, you know that you have access, if you don't start there first before getting into connection strings through .NET languages.   I suggest just adding an easy alias, my local SQL box is simply called
    'Brett'.  Go again back to SQL Server Configuration Manager.  On the left side click 'SQL Native Client ...' > 'Aliases' > New > type in whatever you want.  Go back to the left pane click on 'SQL Server Services' ensure the service
    'SQL Server Browser' is running and set to run automatic.  Have fun accessing SQL Server with your alias.  
    Help I can't get FileStream to work and I ran 'spconfigure' in SQL and it still doesn't work.
    Kind of annoying that more sites don't list that it is entirely in the Configuration manager and has zilch to do with setting the option if the config has it off.  I am not a master of the sp_configure TSQL access method but I know during installs turning
    it on fails to REALLY turn it on.  Once again go to SQL Config Manger > SQL Server Services > Right click your instance > Select FILESTREAM tab > enable both check boxes.  Restart SQL Server.  Install Adventureworks 2008 and whatever
    else failed due to filestream access levels.
    Medium to Advanced on some things, but always wanting to know more

  • Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

    This was originally posted in the SSIS Forum, but a member of the IS team suggested it be moved here.  "Most recently I got this error (Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) so does this mean that SQL Server is still trying to use named pipes even if I only have TCP/IP enabled in SQL Server Configuration Manager?"
    I'm having the same issue, and here's our scenario:
    Installed SQL Server 2005 Developer Edition on a machine with WinXP SP2 and enabled remote connections over TCP/IP
    Installed SQL Server 2005 Standard Edition on a machine with Win2003 SP1 (remote connections over TCP/IP enabled by default)
    Attempted to 'Copy Database' from Developer Edition TO Standard Edition using 'Detach and Attach' method and recieved the error on the Win2003 machine: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
    Attempted to 'Copy Database' from Developer Edition TO Standard Edition using 'SQL Management Objects' method and recieved the error on the Win2003 machine: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
    Reinstalled Standard Edition on the Win2003 SP1 machine
    Checked all the settings on both machines several times, restarted services etc., and read every post I could find referencing the error.
    Same error
    Lost my last hair
    Thanks in advance,
    Steve

    Nan,
    Before I get on with this post - thank you for your reply.
    The XPSP2 machine actually had the firewall disabled, and I verified that it could accept connections on the the associated ports with the Shields Up utility.  I tested this on both machines.
    I can connect to the server from the XPSP2 machine, Import / Export, manage, view logs, and do everything EXCEPT get the Copy Database package to run.  SQL Server Agent always fails on the last step with the following error:
    Event Type: Error
    Event Source: SQLISPackage
    Event Category: None
    Event ID: 12550
    Date:  1/10/2006
    Time:  1:34:15 PM
    User:  NT AUTHORITY\SYSTEM
    Computer: 401SERVER
    Description:
      Event Name: OnError
     Message: Failed to connect to server BETHESDA.
    StackTrace:    at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
       at Microsoft.SqlServer.Dts.Tasks.TransferObjectsTask.TransferObjectsTask.OpenConnection(Server& server, ServerProperty serverProp)
    InnerException-->An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
    StackTrace:    at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
       at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
       at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)
       at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
       at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
       at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
       at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
       at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
       at System.Data.SqlClient.SqlConnection.Open()
       at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)
       at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()
     Operator: NT AUTHORITY\SYSTEM
     Source Name: BETHESDA_401SERVER_Transfer Objects Task
     Source ID: {86F355AD-3B74-4D7B-8D2D-C743C790A269}
     Execution ID: {91B7C32C-C439-4EDB-8A0F-9F8BF207BC06}
     Start Time: 1/10/2006 1:34:15 PM
     End Time: 1/10/2006 1:34:15 PM
     Data Code: 0
    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
    Have you (or anyone else) successfully executed a Copy Databse task?
    Steve

Maybe you are looking for

  • BADI - ME_PROCESS_PO_CUST - To update Condition Types at time of creation

    Hi All I'm relatively new to Implementing BADIs. I'm using the BADI ME_PROCESS_PO_CUST. I have to update certain condition types with values determined from a custom table maintained for related Vendors. I have created a 'Z' implementation for ME_PRO

  • Can't send mail suddenly - help?

    i have had my computer set up with the same isp for a year and suddenly in the last week or so i can't send email. i thought it was a fluke as it would sometimes let me send but now i can't at all. i am getting this error message: Error This message

  • JMS adapter not picking the file

    Hello, I am working jms to jms scenario on PI7.0 Service Pack13. file is not able to pick up sendar JMS Channel. I am using WebSphereMQ Transport Protocol. JMS drivers are installed. I checked all parameters of JMS Adapter. no mistake in parameters.

  • Quark file will not open in InDesign

    I'm having trouble with one Quark file that will not open in InDesign. It came in a package with several other files that are working just fine. I'm getting this popup. It is not open in an application, the file format is exactly the same as the othe

  • Graph legend width change - Left aligned or right aligned

    Hello all, when I place an XY-Graph with Plot-Legend shown in LV2012, the text of the plot name is left aligned, wich is, what I want. With this behaviour the little pictures, representing the plot attributes, are fixed. After migrating to LV2014 I r