home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.databases.ms-sqlserver      Notorious Rube Goldberg contraption      19,505 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 17,728 of 19,505   
   Matthew Wells to JAW   
   Re: SSIS Connection...   
   29 Dec 09 10:33:41   
   
   From: matthew.wells@firstbyte.net   
      
   All services were running under LocalSystem.  I created a new user with   
   Domain Admin rights and have changed all services to use this account.  I   
   know remote connections are allowed because I've created a .udl file and   
   connected under sa and my windows login.  I'm still getting the same   
   message.  I also didn't see anything in the configuration manager that would   
   help.  I connected the SSIS service to SSMS and there's nothing there   
   either.  Do you have any other suggestions?   
      
   "JAW"  wrote in message   
   news:6ZWdnSt25eDZuaTWnZ2dnUVZ_qWdnZ2d@earthlink.com...   
   > In 2008 the account (SQL Server or Windows) if it has been granted   
   > DBACCESS it should have what it needs.   
   >   
   > Also, I think the access drivers come from MDAC. You should make sure that   
   > is on your computer as well.   
   >   
   > I have not experienced this issue in 2008.   
   >   
   >   
   > "Matthew Wells"  wrote in message   
   > news:7K8_m.126539$Wf2.67624@newsfe23.iad...   
   >> I'm using 2008 and did a little research and found that SACM is not   
   >> available anymore.  I found some info on configuring other SQL engines,   
   >> but nothing for Access mdb files.  Do you know where to look?   
   >>   
   >> Thanks.   
   >>   
   >> "JAW"  wrote in message   
   >> news:e98379ea-a278-476b-b78a-58b8778aaedd@u37g2000vbc.googlegroups.com...   
   >>> Assume you are running 2005 you can check the Surface Area   
   >>> Configuration Manager and make sure remote connections are being   
   >>> allowed. That is the first thing I would look at.   
   >>>   
   >>> On Dec 28, 12:50 pm, "Matthew Wells"    
   >>> wrote:   
   >>>> Hello   
   >>>>   
   >>>>     I'm building an SSIS package from home to be deployed at an office.   
   >>>> The   
   >>>> package is a simple Access to SQL Server migration.  I was building the   
   >>>> SSIS   
   >>>> package on a local machine which also housed the Access file.  I   
   >>>> decided to   
   >>>> open the SSIS package from my laptop.  Both the laptop and the   
   >>>> workstation I   
   >>>> was using use the same mapped share - F:\.  The Access connection is   
   >>>> OLE DB   
   >>>> / Office 12.  The SQL Server is an SQL Server Destination object.  Now   
   >>>> when   
   >>>> I open the SQL Destination, I get this warning at the bottom and I   
   >>>> can't map   
   >>>> columns:   
   >>>>   
   >>>> "The selected data source is on a remote computer.  The bulk insert   
   >>>> operation can be executed only on the local computer."   
   >>>>   
   >>>> When I run this package at the office, the Access file will not - and   
   >>>> can   
   >>>> not - be on the local machine.  Is there a way around this?   
   >>>>   
   >>>> Thanks.   
   >>>>   
   >>>> Matthew Wells   
   >>>> matthew.we...@firstbyte.net   
   >>>   
   >   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca