From: esquel@sommarskog.se   
      
   Gene Wirchenko (genew@ocis.net) writes:   
   >      I tried and ran into some trouble.  The tests for   
   > Win32::SqlServer failed.  I got:   
   >   
   > SQL Server message 2, Severity 16, State 1   
   > Named Pipes Provider: Could not open a connection to SQL Server [2].   
   > Message 08001 from 'Microsoft SQL Server Native Client 10.0',   
   > Severity: 16   
   > 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.   
      
   Which means that you were not able to contact SQL Server.   
      
   >      My guess is that it is trying to use the wrong instance name. How   
   > do I specify the instance?   
   >   
   >      Or is it something else?   
      
   If you were running the test suite for Win32::SqlServer, you need to set up   
   connection details with OLLEDBTEST as described in Tests.html. If you are   
   trying to use an AbaPerls tool, use the -S switch to specify a server.   
      
      
   --   
   Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se   
      
   Books Online for SQL Server 2005 at   
   http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx   
   Books Online for SQL Server 2000 at   
   http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)