alimack's questions

I'm using a proxy to run several SQL Server agent jobs.
Essentially the jobs copy data from Excel spreadsheets into a dbs via a network shared drive. The jobs have been failing for several weeks with the following error:

"Unable to start execution of step 1 (reason: Error authenticating proxy SERVERNAME\sharename, system error: ConnGetProxyPassword). The step failed."

when I run it under the proxy account, if I run it under the SQL Server Agent then I don't have permission errors.

I've recreated the proxy accounts but this has made no difference. The password for the proxy is correct.

Banging my head against this - any suggestions? It's not password length which I've seen suggested online.

Basically, I'm trying to make SOAP calls from a Tomcat server via a corporate proxy/ firewall (which I have no direct control over), I've tried to add info to the catalina.properties file as shown:

http.proxyPort=80
http.proxyHost=www-proxy.company.com

I'm still getting timeouts in the stdout logs. Do I need to do anything else and if not is there another way to test the SOAP calls?

Essentially I have a job which runs in BIDS and as as a stand lone package and while it runs under the SQL Server Agent it doesn't complete properly (no error messages though).

The job steps are:

1) Delete all rows from table;

2) Use For each loop to fill up table from Excel spreasheets;

3) Clean up table.

I've tried this MS page (steps 1 & 2), didn't see any need to start changing from Server side security.

Also SQLServerCentral.com for this page, no resolution.

How can I get error logging or a fix?

I have logged in as the proxy account I'm running this under, and the job runs stand alone but complains that the Excel tables are empty?

Basically I'm trying to run a functioning SSIS job (created in BIDS) under the SQL Server Agent - it reads a set of Excel spreadsheets and dumps the results into a table. The problem I'm having is getting the SSA to read the file path, the relevant part of the error is:

"0x80004005 Description: "'N:\Assets Property & Facilities Management\Monthly Absence.xls' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides."

I've tried using UNC paths (\servername\ share) but the BIDS rewrites the paths to standard file paths (c:\directory\filename), I've also tried a proxy which runs this step under an Admin account. I've also tried changing the path to UNC on the SSIS job on the server. Also I'm forcing it to use the 32 bit DTEXEC, so it's not that either

Always get the same error, do I need to re-create the job from scratch?

I'm trying to use SSIS to traverse a directory of Excel files and put them into a table in SQL Server. I seem to have a basic choice - either I get the same spreadsheet dumped in the table 10 times or I get an error message. I'm using the instructions here:

http://www.sqlis.com/post/Looping-over-files-with-the-Foreach-Loop.aspx

Error message:

TITLE: Package Validation Error

Package Validation Error

ADDITIONAL INFORMATION:

Error at Data Flow Task [Destination - HR_Data [200]]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DestinationConnectionOLEDB" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.

Error at Data Flow Task [DTS.Pipeline]: component "Destination - HR_Data" (200) failed validation and returned error code 0xC020801C.

Error at Data Flow Task [DTS.Pipeline]: One or more component failed validation.

Error at Data Flow Task: There were errors during task validation.

Error at HR Full Data Load [Connection manager "DestinationConnectionOLEDB"]: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft OLE DB Provider for ODBC Drivers" Hresult: 0x80004005 Description: "[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified".

(Microsoft.DataTransformationServices.VsIntegration)

BUTTONS:

OK

One day instead of connecting to the database my SQL Server Management gave me the following error: "Data Source name not found & no default driver found"

Note it had been working for several years before this, all that had changed was an upgrade to Office (97 ->2000) and the monthly Windows patches.

I tried rebooting, re-installing both the SQL Server 2000 and 2005 clients on the machine but no joy. I can access the database(s) from other machines.

Basically seeing problems accessing external drives, SuperDuper backup slow and prone to crashing causing kernel panics, Virusbarrier ditto. See my answer seems to be a known firewire driver fault in Snow Leopard which persists in 10.6.1.

With a 4Gb RAM server and Windows 2003, I've determined by trial and error that setting a virtual RAM limit of 1.6 seems to kill the runaway processes without causing the normal processes to restart unnecessarily.

Support suggested a formula of 1.9 - all running processes = virtual memory limit, is there any theory behind this?

Obviously you can detach the whole dbs and reattach using sp_attach and sp_detach. Is there an online way to do this, have had a quick google but can't see anything.

I've got an extensive selection of these to add to a spreadsheet and don't want to go through by hand. What it the T-SQL command(s) to generate a list of SQL Server Agent Jobs?

This caused flame war in my Mac users group, but the recent advisory that Apple released and then pulled suggesting using anti-virus products. My take is that it's worth being safe rather than sorry, what's the general feeling on serverfault?

And if yes what do you recommend?

What is it and how can it stop it cancelling my updates from Enterprise Manager?