May 12, 2011 at 8:19 am
Hi Guys, I have an issue where my scheduled job just seems to fail sometimes for no reason. Here is the scenario: If I right click on start job on step and run the job like that it runs fine for the most part without failing, when I schedule it and let it run as scheduled it runs fine for the most part, the problem is that sometimes when I do what I just said the job fails for no reason and I don't know why...Can this be some memory allocation issue or something else? Just wondering if anyone has dealt with this kind of issue before. Thanks in advance
May 12, 2011 at 8:24 am
Have you looked in the job history for the error message?
John
May 12, 2011 at 8:37 am
owner of the job ?
job history error ?
Regards,
Syed Jahanzaib Bin Hassan
BSCS | MCTS | MCITP | OCA | OCP | OCE | SCJP | IBMCDBA
My Blog
www.aureus-salah.com
May 12, 2011 at 8:44 am
Owner of the job is my username, the job history error is one that I was getting before but I finally fixed that yesterday by adding my username to the server as part of the "Log on as user" list in the local policy settings section. But now today I can run the job through the agent and its successful, but when it does fail from time to time for no reason at all, the same error messages show up, its not the connections or anything like that, but if you guys want below is the error message. I've been testing the job all morning to run every 30 mins to see if there is a trend, the job failed at 10:07am for no reason at all, and now at 10:37am the job went through successfully.
Executed as user: CORE\<username>. ...sion 10.50.1600.1 for 64-bit Copyright (C) Microsoft Corporation 2010. All rights reserved. Started: 10:07:00 AM Error: 2011-05-12 10:09:10.16 Code: 0xC001401E Source: IGIVE Connection manager "Archive" Description: The file name "\\pulse\Image_Storage\ToProcess\" specified in the connection was not valid. End Error Error: 2011-05-12 10:09:10.16 Code: 0xC001401D Source: IGIVE Description: Connection "Archive" failed validation. End Error Error: 2011-05-12 10:09:10.16 Code: 0xC001401E Source: IGIVE Connection manager "ArchiveXML" Description: The file name "\\pulse\Image_Storage\Temp\.xml" specified in the connection was not valid. End Error Error: 2011-05-12 10:09:10.16 Code: 0xC001401D Source: IGIVE Description: Connection "ArchiveXML" failed validation. End Error Error: 2011-05-12 10:09:10.16 Code: 0xC001401E Source: IGIVE Connection manager "DeleteBADXML Files" Description: The file name "\\pulse\Image_Storage\ToProcess\Error\BADXML.txt" specified in the connection was not valid. End Error Error: 2011-05-12 10:09:10.16 Code: 0xC001401D Source: IGIVE Description: Connection "DeleteBADXML Files" failed validation. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401E Source: IGIVE Connection manager "DELTXT" Description: The file name "\\pulse\Image_Storage\Temp\.txt" specified in the connection was not valid. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401D Source: IGIVE Description: Connection "DELTXT" failed validation. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401E Source: IGIVE Connection manager "Error File" Description: The file name "\\pulse\Image_Storage\ToProcess\Error\05122011.csv" specified in the connection was not valid. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401D Source: IGIVE Description: Connection "Error File" failed validation. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401E Source: IGIVE Connection manager "IGCTXT" Description: The file name "\\pulse\Image_Storage\Temp\.txt" specified in the connection was not valid. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401D Source: IGIVE Description: Connection "IGCTXT" failed validation. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401E Source: IGIVE Connection manager "IGCXML" Description: The file name "\\pulse\Image_Storage\Temp\.xml" specified in the connection was not valid. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401D Source: IGIVE Description: Connection "IGCXML" failed validation. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401E Source: IGIVE Connection manager "IGCXSL" Description: The file name "\\pulse\Image_Storage\Temp\DONOTDELETE\igc.xsl" specified in the connection was not valid. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401D Source: IGIVE Description: Connection "IGCXSL" failed validation. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401E Source: IGIVE Connection manager "PDF" Description: The file name "\\pulse\Image_Storage\PDF\" specified in the connection was not valid. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401D Source: IGIVE Description: Connection "PDF" failed validation. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401E Source: IGIVE Connection manager "Valid File" Description: The file name "\\pulse\Image_Storage\Inkjet\IGC_INKJET.csv" specified in the connection was not valid. End Error Error: 2011-05-12 10:09:10.18 Code: 0xC001401D Source: IGIVE Description: Conne... The package execution fa... The step failed.
May 12, 2011 at 8:53 am
Looks like occasional network problems are preventing your PULSE server from being reached - either that or something is wrong with the server itself.
John
May 12, 2011 at 9:06 am
I was afraid of that, but from what I have deduced from what people have told me here, there are never any issues with it, but taking advice from people that aren't network admins is like taking advice from a monkey on how to end world hunger. I think that might be a possibility, I don't put anything out of the realm of possibilities, SSIS is known to be very particular. If you guys have any other possible suggestions to what I should be double checking it would be greatly appreciated.
May 12, 2011 at 10:03 am
"The file name "\\pulse\Image_Storage\ToProcess\" specified in the connection was not valid."
It looks like it's looking for a file name but it's given a Directory path.
"IGIVE Connection manager "IGCXML" Description: The file name "\\pulse\Image_Storage\Temp\.xml" specified in the connection was not valid."
Note the UNC path "\\pulse\Image_Storage\Temp\.xml", it only has a file extension and not a complete filename with extension.
"The file name "\\pulse\Image_Storage\PDF\" specified in the connection was not valid."
It looks like it's looking for a file name but it's given a Directory path.
IS this file "igc.xsl" valid?
I ask because most Excel spreadsheets are .xls or the new .xlsx
I could be wrong and that might be a valid file unique to your application.
From looking at the UNC directory paths not having a file name, it might be possible that a variable may be populating the filename and that var might be empty? Just a hunch.
Network guys always say everything is working fine. For the most part their correct. Crap just seems to go wrong when their not looking.
I would recomend using the IP address instead of the NetBios name or the FQDN of your "PULSE" server/machine. That eliminates your DNS server(s) from the equation. If you have only one DNS server and it reboots the same time you're running your package, then name resolution is dead till it gets back online.
May 12, 2011 at 10:42 am
I see why you would say that the paths are wrong, but the paths without files are variables that just hold the bulk of the connection string as I'm using expressions to build the paths dynamically, also that is why you see the entire path with only a .xml at the end because the for each loop container builds the name and adds it to the .xml, I definitely can see why you would think that. With the trending analysis that I have done as far as running the job every 30 mins, I am noticing that the job runs fine in one run and will fail for no reason the next run, run fine the next run and then fail the next, etc... any suggestions why this might be happening?
May 12, 2011 at 10:49 am
For kicks, grant "sa" as the job owner and see if it keeps happening.
😀
May 12, 2011 at 11:00 am
HAHA, I will try that to see what happens. damn sa gets everything, even though my account is an SA account, I'll try it anyway you never know
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply