|
|
You're in the
sql server dts
group:SSIS - can SSIS pkg recognize a drive letter within SMS job?
sql server dts:
Is there some way that SSIS projects can recognize a drive mapping when the package(s) are executed from within a SMS job ? The SMS job agent runs within it's own shell and I've tried using " EXECUTE xp_cmdshell 'SUBST W: \\network_server\shared\database\sql_server\workarea\dba\server_name\instance_name\db_name\subsystem\' " in an [ Execute SQL Task ] prior to running a series of [ Execute Package Tasks ] ... and other variations with no luck. I understand the I'd have a better chance using UNC's directly however our SSIS scripts are stored on different netowork server and the path is longer than 128 characters. Thus the need for a mapped drive letter. I also understand that I could move all of the target packages into the Sql Server SSIS 'store' ... however ... this particular project is unloads every table in our enterprise database to a delimited text file as an alternative backup. There is a package for each table requiring a HUGE number of packages to be imported into the DB SSIS store. At this point I'm simply trying to place the MAIN packages in the db SSIS 'store' rather than dealing with the madness of importing hundreds of packages into the 'store'. If anyone knows how to get SSIS to recognize a mapped drive please provide a pointer to one or more examples. Thanks in advance !!! Barry in Oregon
Hi Barry,
To let me better understand your issue, could you please describe your process more detailed so that I can reproduce your issue? I performed a test at my side, however I could not reproduce your issue. My test process was as following: 1. Create a mapped drive Y: which mapped to drive D: on another machine. 2. Create a Execute SQL Task with the following SQL statement: INSERT INTO item VALUES('A7',4,20) 3. Save the package to the mapped drive path Y:\Share\test.dtsx 4. Connect to SQL Server Integration Services from SSMS 5. Expand Stored Packages, right click File System, select Import package; 6. Select Pckage location as File System, select package path as Y:\Share\test.dtsx and input Pakcage name as test; 7. Connect to SQL Server instance from SSMS, expand SQL Server Agent, right click Jobs, click New Job...., input the job name, select Steps, click New..., input Step name, select Type as SQL Server Integration Services package, select Package source as SSIS Package Store, select Server, select Package as Test and click OK. 8. Start the job and it worked fine. The SQL Server Agent service account is a domain user which has full control on the remote share folder. Please check my steps and compare with yours to see if there are some hints. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Community Support ===================================================== Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
Charles,
Thanks for the quick response! Its very much appreciated. Unfortunately, I've been fighting fires all day and as a result I haven't had a chance to retest this issue. I'll let you know as soon as possible! Thanks in advance !! Barry in Oregon [quoted text, click to view] "Charles Wang[MSFT]" <changliw@online.microsoft.com> wrote in message news:K8G$QD3wHHA.4484@TK2MSFTNGHUB02.phx.gbl... > Hi Barry, > To let me better understand your issue, could you please describe your > process more detailed so that I can reproduce your issue? > > I performed a test at my side, however I could not reproduce your issue. > My > test process was as following: > 1. Create a mapped drive Y: which mapped to drive D: on another machine. > 2. Create a Execute SQL Task with the following SQL statement: > INSERT INTO item VALUES('A7',4,20) > 3. Save the package to the mapped drive path Y:\Share\test.dtsx > 4. Connect to SQL Server Integration Services from SSMS > 5. Expand Stored Packages, right click File System, select Import package; > 6. Select Pckage location as File System, select package path as > Y:\Share\test.dtsx and input Pakcage name as test; > 7. Connect to SQL Server instance from SSMS, expand SQL Server Agent, > right > click Jobs, click New Job...., input the job name, select Steps, click > New..., input Step name, select Type as SQL Server Integration Services > package, select Package source as SSIS Package Store, select Server, > select > Package as Test and click OK. > 8. Start the job and it worked fine. > The SQL Server Agent service account is a domain user which has full > control on the remote share folder. > > Please check my steps and compare with yours to see if there are some > hints. If you have any other questions or concerns, please feel free to > let > me know. > > Best regards, > Charles Wang > Microsoft Online Community Support > ===================================================== > Get notification to my posts through email? Please refer to: > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications > > If you are using Outlook Express, please make sure you clear the check box > "Tools/Options/Read: Get 300 headers at a time" to see your reply > promptly. > > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscriptions/support/default.aspx. > ====================================================== > When responding to posts, please "Reply to Group" via > your newsreader so that others may learn and benefit > from this issue. > ====================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. > ====================================================== > > > > >
Hi Barry,
No problem. Just feel free to post back if you encounter any problems when you retest this issue. Have a nice day! Best regards, Charles Wang Microsoft Online Community Support ===================================================== Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
Charles,
I reproduced the problem with a much smaller ssis project on our test Sql Server against the AdventureWorks sample database. The best approach would probably be to send or ftp you a zipped copy of the SSIS project along with a couple of screen shots. Can we coordinate something like that ?? Thanks in advance. Barry in Oregon [quoted text, click to view] "Charles Wang[MSFT]" <changliw@online.microsoft.com> wrote in message news:E5XK0ZFxHHA.4484@TK2MSFTNGHUB02.phx.gbl... > Hi Barry, > No problem. Just feel free to post back if you encounter any problems when > you retest this issue. > > Have a nice day! > > Best regards, > Charles Wang > Microsoft Online Community Support > ===================================================== > Get notification to my posts through email? Please refer to: > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications > > If you are using Outlook Express, please make sure you clear the check box > "Tools/Options/Read: Get 300 headers at a time" to see your reply > promptly. > > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscriptions/support/default.aspx. > ====================================================== > When responding to posts, please "Reply to Group" via > your newsreader so that others may learn and benefit > from this issue. > ====================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. > ====================================================== > > >
Hi Barry,
Thanks for your response. You can directly send the package to me (changliw_at_microsoft_dot_com). Best regards, Charles Wang Microsoft Online Community Support ===================================================== Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
Hi Barry,
Thanks for your response. What is the result if you modify the FullPath value? Also, I find that your SQL Server 2005 version is 9.0.0.1399 which indicates that your SQL Server 2005 has no service packs installed. I recommend that you install SQL Server 2005 SP2 first and then recreate your SSIS package to see if this issue persists. You can download the SP2 from: http://www.microsoft.com/downloads/details.aspx?familyid=d07219b2-1e23-49c8- 8f0c-63fa18f26d3a&displaylang=en http://support.microsoft.com/kb/933508 Please feel free to let me know if you have any other questions or concerns. Best regards, Charles Wang Microsoft Online Community Support [quoted text, click to view] >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> this observation may be worth mentioning.>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> > Charles, > I don't know if this has any relevance to this issue or not. However ... [quoted text, click to view] > I was fighting with trying to rename one of my SSIS projects and had a all the projects to a new correctly named project. Durning this > process terrible time getting the renaming to 'take', finally ended > up deleting the .database, .dtproj, etc files totally and simpy readded I noticed that the package descriptions within the .dtproj file have a <FullPath> xml tag. But in my SSIS projects the [quoted text, click to view] > <FullPath> value contains only the package name and no path information SMS job to fail to find the package ??at all. Implying that, to run, the directory containing the > package must be selected ... could this be the issue that is causing the [quoted text, click to view] > Probably a 'red herring' but one never knows ... [quoted text, click to view] > <DtsPackage>
> <Name>aim_employee_responsible_to_delimited_txt.dtsx</Name> > <FullPath>aim_employee_responsible_to_delimited_txt.dtsx</FullPath> > <References /> > </DtsPackage> > <DtsPackage> > <Name>aim_hardware_attributes_to_delimited_txt.dtsx</Name> > <FullPath>aim_hardware_attributes_to_delimited_txt.dtsx</FullPath> > <References /> > </DtsPackage> > <DtsPackage> > <Name>aim_inventory_item_to_delimited_txt.dtsx</Name> > <FullPath>aim_inventory_item_to_delimited_txt.dtsx</FullPath> > <References /> > </DtsPackage> > Barry > in Oregon
Charles,
1st thanks for all your advice and patience while helping me work this problem. Your help is very much appreciated. With respect to your suggestions ... I tried changing the mapped drive values to UNC's for both the path to the delimited text file directory and also the path to the .dtsx files. The process still fails. Very frustrating. I also tried adding the UNC path to the <FullPath> value in the .dtproj ..dtsx definitions as well. Still with no success. It's interesting to note that the job runs fine when executed directly from within the SMS - Integration Services connection package store using both the mapped drives and the UNC paths. With respect to engine version, we're still running the 1st release version. From your note it looks like I should re-consider installing SP2. Unfortunately, from what I've read about 'breaking' problems with SP1 & SP2, I'm very wary of upgrading our instance since our engine is running GREAT right now except for this particular problem. The one alternative I've been wondering about is setting the default package path in the 'Controller' SSIS package that calls all the individual table [Execute Package] tasks. Unfortunately, I haven't figured out a way to set a starting path from within an SSIS package script. Is there a way to set a 'defualt starting path' at the beginning of an SSIS package ? By the way, changing the file path on 150+ individual packages with the SSIS designer would be VERY tedious ... is there some place that package object paths can be updated with a text editor outside of the SSIS designer ? I had hopes when updating the .dtproj <FullPath> value but it setting the path there doesn't seem to make a difference. Thanks in advance. Barry in Oregon [quoted text, click to view] "Charles Wang[MSFT]" <changliw@online.microsoft.com> wrote in message news:%23$toY%23SzHHA.5848@TK2MSFTNGHUB02.phx.gbl... > Hi Barry, > Thanks for your response. > > What is the result if you modify the FullPath value? > Also, I find that your SQL Server 2005 version is 9.0.0.1399 which > indicates that your SQL Server 2005 has no service packs installed. I > recommend that you install SQL Server 2005 SP2 first and then recreate > your > SSIS package to see if this issue persists. > > You can download the SP2 from: > http://www.microsoft.com/downloads/details.aspx?familyid=d07219b2-1e23-49c8- > 8f0c-63fa18f26d3a&displaylang=en > http://support.microsoft.com/kb/933508 > > Please feel free to let me know if you have any other questions or > concerns. > > Best regards, > Charles Wang > Microsoft Online Community Support > >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>> >> Charles, > >> I don't know if this has any relevance to this issue or not. However ... > this observation may be worth mentioning. > >> I was fighting with trying to rename one of my SSIS projects and had a > terrible time getting the renaming to 'take', finally ended >> up deleting the .database, .dtproj, etc files totally and simpy readded > all the projects to a new correctly named project. Durning this > process > I noticed that the package descriptions within the .dtproj file have a > <FullPath> xml tag. But in my SSIS projects the >> <FullPath> value contains only the package name and no path information > at all. Implying that, to run, the directory containing the >> package must be selected ... could this be the issue that is causing the > SMS job to fail to find the package ?? > >> Probably a 'red herring' but one never knows ... > > >> <DtsPackage> >> <Name>aim_employee_responsible_to_delimited_txt.dtsx</Name> >> > <FullPath>aim_employee_responsible_to_delimited_txt.dtsx</FullPath> >> <References /> >> </DtsPackage> >> <DtsPackage> >> <Name>aim_hardware_attributes_to_delimited_txt.dtsx</Name> >> > <FullPath>aim_hardware_attributes_to_delimited_txt.dtsx</FullPath> >> <References /> >> </DtsPackage> >> <DtsPackage> >> <Name>aim_inventory_item_to_delimited_txt.dtsx</Name> >> <FullPath>aim_inventory_item_to_delimited_txt.dtsx</FullPath> >> <References /> >> </DtsPackage> > >> Barry >> in Oregon >
Hi Barry,
Sorry for delaying my response. I noticed that you might have a long time to perform a test with SP2, so I decided to request our Lab to help me establish a fresh test environment with SQL Server 2005 without SP2 yesterday. However the environment was just finished this afternoon. To my surprise, after my test I found that my former solution could also work on the SQL Server 2005 without SP2. So I think that we should put SP2 aside now, this issue is caused by other reasons. I would like to summarize my steps here and you may check to see if there was any step ommitted at your side: 1. Created a shared folder on the remote machine (Server B) and assign fully control permission to the my local SQL Server Agent Services (on Server A) startup account which is a domain user; 2. On my local computer (Server A), created a mapped drive to the UNC folder where you upload the SSIS package; 3. Uploaded the SSIS package which was simple and just contained one "Execute SQL Task" to the shared folder; 4. On Server A, connected to SQL Server Integration Services from SSMS, right clicked File System, clicked Import Package, selected Package location as File System, selected Pckage path as W:\rptest.dtsx (W represents '\\charles-test\server_name\shared\database\sql_server\workarea\dba\server_n ame\instance_name\db_name') , input package name as rptest, and clicked OK; 5. Tried running the package in SSMS to check if it could work. It finished successfully on my machine. 6. On Server A, connected to Database Engine from SSMS, expanded SQL Server Agent and created a job; under job properties window, input job name, selected Steps, clicked New..., input Step name, selected Type as "SQL Server Integration Services Package", selected "Run as" as "SQL Agent Service Account", selected "Package source" as "SSIS Package Store", selected Server as my local server name "CharlesXP", selected "Log on to the server" as "Use Windows Authentication", selected Package as "\File System\rptest" and clicked OK. 7. Right clicked the job and clicked "Start job at step...". It worked without any error message thrown. I began to doubt that if this was a permission issue at your side. For now, I recommend that you let me know the following questions: 1. What is your SQL Server Agent service account? 2. What are the permissions that your SQL Server Agent service account has on your remote shared folder? 3. If this issue persists, what is the result if you use a simple SSIS test package? For your question, I have not found any documentation talking about it, however I think it is essentially same as deploying all the SSIS packages into the File System folder of SQL Server Integration Services package storage, which is actually my above method. If you have any other questions or concerns, please feel free to let me know. Best regards, Charles Wang Microsoft Online Partner Support PLEASE NOTE: The partner managed newsgroups are provided to assist with break/fix issues and simple how to questions. We also love to hear your product feedback! Let us know what you think by posting - from the web interface: Partner Feedback - from your newsreader: microsoft.private.directaccess.partnerfeedback. We look forward to hearing from you! ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
Charles,
Boy do I feel stupid !!! Realized from your process description that you were running SSMS from your workstation. As dba, I normally run SSMS on our Sql Server using a remote (terminal services) connection from my workstation to our Sql Server box. So I tried the running the job from SSMS installed on and running from my workstation. (even though I couldn't see the step in the job property page). It worked !! Arrrgggggg. Next test, I walked down to the machine room and ran the job directly on the Sql Server console. It ran there successfully as well !! So I set up a scheduled run for 12:45pm ... the job ran fine !!!! Arrrrrggggggggg !!!! So the issue seems to have something to do with executing the SSMS job via the remote (terminal services) connection. All other jobs I've set up using the remote terminal session to the server have worked fine until now. Terminal services has been solid up to now ... never really considered it as a possible problem source. I think I'll go throw myself out the window now. Barry in Oregon [quoted text, click to view] "Charles Wang[MSFT]" <changliw@online.microsoft.com> wrote in message news:dalYTME0HHA.6140@TK2MSFTNGHUB02.phx.gbl... > Hi Barry, > Sorry for delaying my response. I noticed that you might have a long time > to perform a test with SP2, so I decided to request our Lab to help me > establish a fresh test environment with SQL Server 2005 without SP2 > yesterday. However the environment was just finished this afternoon. > > To my surprise, after my test I found that my former solution could also > work on the SQL Server 2005 without SP2. So I think that we should put SP2 > aside now, this issue is caused by other reasons. > > I would like to summarize my steps here and you may check to see if there > was any step ommitted at your side: > 1. Created a shared folder on the remote machine (Server B) and assign > fully control permission to the my local SQL Server Agent Services (on > Server A) startup account which is a domain user; > 2. On my local computer (Server A), created a mapped drive to the UNC > folder where you upload the SSIS package; > 3. Uploaded the SSIS package which was simple and just contained one > "Execute SQL Task" to the shared folder; > 4. On Server A, connected to SQL Server Integration Services from SSMS, > right clicked File System, clicked Import Package, selected Package > location as File System, selected Pckage path as W:\rptest.dtsx (W > represents > '\\charles-test\server_name\shared\database\sql_server\workarea\dba\server_n > ame\instance_name\db_name') , input package name as rptest, and clicked > OK; > 5. Tried running the package in SSMS to check if it could work. It > finished > successfully on my machine. > 6. On Server A, connected to Database Engine from SSMS, expanded SQL > Server > Agent and created a job; under job properties window, input job name, > selected Steps, clicked New..., input Step name, selected Type as "SQL > Server Integration Services Package", selected "Run as" as "SQL Agent > Service Account", selected "Package source" as "SSIS Package Store", > selected Server as my local server name "CharlesXP", selected "Log on to > the server" as "Use Windows Authentication", selected Package as "\File > System\rptest" and clicked OK. > 7. Right clicked the job and clicked "Start job at step...". > It worked without any error message thrown. > > I began to doubt that if this was a permission issue at your side. For > now, > I recommend that you let me know the following questions: > 1. What is your SQL Server Agent service account? > 2. What are the permissions that your SQL Server Agent service account has > on your remote shared folder? > 3. If this issue persists, what is the result if you use a simple SSIS > test > package? > > For your question, I have not found any documentation talking about it, > however I think it is essentially same as deploying all the SSIS packages > into the File System folder of SQL Server Integration Services package > storage, which is actually my above method. > > If you have any other questions or concerns, please feel free to let me > know. > > Best regards, > Charles Wang > Microsoft Online Partner Support > > PLEASE NOTE: The partner managed newsgroups are provided > to assist with break/fix issues and simple how to questions. > We also love to hear your product feedback! > > Let us know what you think by posting > - from the web interface: Partner Feedback > - from your newsreader: > microsoft.private.directaccess.partnerfeedback. > We look forward to hearing from you! > ====================================================== > When responding to posts, please "Reply to Group" via > your newsreader so that others may learn and benefit > from this issue. > ====================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. > ====================================================== > > > > > > > > > > > > > >
Hi Barry,
Congratulations! I am glad to hear that this issue has been fixed. The cause is indeed hard to be found. Based on your description, I performed a little more research and I found that there was indeed a known issue of running SQL jobs with Terminal Services. For your information, please refer to: FIX: Error message when you schedule some SQL Server 2005 Integration Services packages to run as jobs: "Package <PackageName> has been cancelled" http://support.microsoft.com/kb/922527 From the KB article, it seems that installing SP2 will fix this issue, however since you do not want to install SP2, I recommend that you contact CSS for just acquiring this hotfix to see if it helps. You can get CSS telephone numbers from http://support.microsoft.com/contactus/?ws=support. If you have any other questions or concerns, please feel free to let me know. Have a nice day! Best regards, Charles Wang Microsoft Online Community Support ===================================================== Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
Charles,
Again, thanks very much for your help and patience while we worked this issue. It's very much appreciated. I hope MSFT appreciates you as much as I do. I'm simply glad that we've resolved, or at least identified, the bug. I was certain I was losing my mind. The original goal has been met since scheduled SMSS jobs will actually run the SSIS batch packages. I'll simply conduct my normal testing of SSIS based jobs outside of my normal Terminal Services connection. Unless other issues arise that make going to SP2 necessary, I just as soon wait for SP3. My hope is that SP3 will have solved most of the common 'breaking' behaviors and since we aren't really doing anything out of the ordinary I expect that waiting for SP3 may be our best strategy. Best regards & many thanks! Barry in Oregon [quoted text, click to view] "Charles Wang[MSFT]" <changliw@online.microsoft.com> wrote in message news:$DfQ5w00HHA.360@TK2MSFTNGHUB02.phx.gbl... > Hi Barry, > Congratulations! I am glad to hear that this issue has been fixed. The > cause is indeed hard to be found. > > Based on your description, I performed a little more research and I found > that there was indeed a known issue of running SQL jobs with Terminal > Services. > For your information, please refer to: > FIX: Error message when you schedule some SQL Server 2005 Integration > Services packages to run as jobs: "Package <PackageName> has been > cancelled" > http://support.microsoft.com/kb/922527 > > From the KB article, it seems that installing SP2 will fix this issue, > however since you do not want to install SP2, I recommend that you contact > CSS for just acquiring this hotfix to see if it helps. > You can get CSS telephone numbers from > http://support.microsoft.com/contactus/?ws=support. > > If you have any other questions or concerns, please feel free to let me > know. > Have a nice day! > > Best regards, > Charles Wang > Microsoft Online Community Support > ===================================================== > Get notification to my posts through email? Please refer to: > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications > > If you are using Outlook Express, please make sure you clear the check box > "Tools/Options/Read: Get 300 headers at a time" to see your reply > promptly. > > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscriptions/support/default.aspx. > ====================================================== > When responding to posts, please "Reply to Group" via > your newsreader so that others may learn and benefit > from this issue. > ====================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. > ====================================================== > >
Hi Barry,
I appreicate your updating and feedback. If you have any other questions or concerns in future, please feel free to post back. It is always our pleasure to be of assistance. Have a great day! Best regards, Charles Wang Microsoft Online Community Support ===================================================== Get notification to my posts through email? Please refer to: http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications If you are using Outlook Express, please make sure you clear the check box "Tools/Options/Read: Get 300 headers at a time" to see your reply promptly. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ====================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from this issue. ====================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ======================================================
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |