Deployment Solution

 View Only

  • 1.  DSWEB 6.9 sp5 - can't schedule jobs in future

    Posted Oct 05, 2011 04:03 PM

    We've installed a new DS (6.9 sp5) directly on the sql server (server 2008r2 sp1, w/ sql 2008r2). This was a clean install, not an upgrade. Most everything seems to be working with one glaring exception:  i cannot schedule a job to occur in the future using the web console.  Before you say anything, I did follow the KB article detailing how to instal on server2008r2 with regards to the IIS6 compatibility items.

    for example:  let's say it's 10am right now, and i want to run a PCT capture at 9pm tonight after the user has gone home.  i can schedule this job to run using the 32bit console just fine, but if i try to schedule it using the web console, i get a big ugly error.  If i schedule it to run immediately from the web console, it works fine.  it doesn't matter what the job does or whose credentials you use - all of them error if you try to schedule them for anything other than "immediately" in the web console.

    i called symantec support and they say that DSWEB is EOL and we're SOL (ok, they didn't say SOL, but might as well have).  That's kinda strange since DS 6.9sp5 just came out earlier this year and it isn't EOL any time soon (or so they say).  We don't plan to use DS 7.1 (it's not feature-complete for us yet) so now we have no product we can use in this scenario.  

    right now our workaround is for the techs (who don't have access to the 32bit console) to email me with a machine name, job, and desired time, and i schedule the job for them.  this is ok when there's only a few per week but things are about to ramp up and it's going to be multiples per HOUR.  i have better things to do than sit there and schedule jobs for people.  

    other than giving our techs access to the 32bit console (which is something we don't want to do), how else are people working around this?  is it possible to maybe write some vb/vbs that will work with axsched.exe or even directly with sql to make it work again? 

    (Or are we the only company still using dsweb?)



  • 2.  RE: DSWEB 6.9 sp5 - can't schedule jobs in future

    Posted Oct 05, 2011 04:41 PM

    Hi Gibson,

    Can you post a screen shot of the error that you are seeing?  It might help us determine what is going on and where to assist you in finding the cause and/or resolution.



  • 3.  RE: DSWEB 6.9 sp5 - can't schedule jobs in future

    Posted Oct 05, 2011 04:55 PM

     

    I attempted to schedule a job to happen at 15:59 (it's currently 15:52).  after confirming that this was the schedule that i wanted, below is the error i got.  
     
    Deployment Web Console error
      The following error has occurred processing the last request:
    • Exception of type 'System.Web.HttpUnhandledException' was thrown.
    Details:  
      System.Web
     
      System.ArgumentOutOfRangeException: Ticks must be between DateTime.MinValue.Ticks and DateTime.MaxValue.Ticks. Parameter name: ticks Server stack trace: at System.DateTime..ctor(Int64 ticks) at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadDateTime() at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadValue(InternalPrimitiveTypeE code) at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.ReadMemberPrimitiveUnTyped() at System.Runtime.Serialization.Formatters.Binary.__BinaryParser.Run() at System.Runtime.Serialization.Formatters.Binary.ObjectReader.Deserialize(HeaderHandler handler, __BinaryParser serParser, Boolean fCheck, IMethodCallMessage methodCallMessage) at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Deserialize(Stream serializationStream, HeaderHandler handler, Boolean fCheck, IMethodCallMessage methodCallMessage) at System.Runtime.Remoting.Channels.CoreChannel.DeserializeBinaryRequestMessage(String objectUri, Stream inputStream, Boolean bStrictBinding, TypeFilterLevel securityLevel) at System.Runtime.Remoting.Channels.BinaryServerFormatterSink.ProcessMessage(IServerChannelSinkStack sinkStack, IMessage requestMsg, ITransportHeaders requestHeaders, Stream requestStream, IMessage& responseMsg, ITransportHeaders& responseHeaders, Stream& responseStream) Exception rethrown at [0]: at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg) at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type) at Altiris.DSSDK.Schedule.SetStartTime(DateTime time, TimeZone zone) at DSWeb.scheduleJob.Button_ApplySchedule_Click(Object sender, EventArgs e) at System.Web.UI.WebControls.Button.OnClick(EventArgs e) at System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) at System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) at System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
     
      at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequestWithNoAssert(HttpContext context) at System.Web.UI.Page.ProcessRequest(HttpContext context) at ASP.schedulejob_aspx.ProcessRequest(HttpContext context) at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

     



  • 4.  RE: DSWEB 6.9 sp5 - can't schedule jobs in future

    Posted Oct 11, 2011 12:44 PM

    Hey jason

     

     

    I dabbled with SP5 for a bit when testing out some Win7 deployment stuiff. My issues were Jobs not completing and erroring out often(The long numeric errors), DS remote worked sporatically. I never even got to the DS web before I abandoned SP5 and went to SP4. Which has a whole set of problems on it's own including the console not being compatible with the rest of our SP2 environment.

    The onyl solution I see is for Altiris to resolve all the issues with 7.1 and everyone migrate over to version 7x.

     



  • 5.  RE: DSWEB 6.9 sp5 - can't schedule jobs in future

    Posted Nov 25, 2011 03:57 PM

    Hi!

    We have the same issues with DSWeb 6.9 on a server  2008r2 sp1, w/SQL eXpress 2008...  Any news?



  • 6.  RE: DSWEB 6.9 sp5 - can't schedule jobs in future

    Posted Nov 28, 2011 04:54 PM

    no news yet.  this isn't at the top of my list but it's looking like i will have to write a custom app myself since we really don't want the techs in the 32bit console.



  • 7.  RE: DSWEB 6.9 sp5 - can't schedule jobs in future

    Posted Nov 29, 2011 03:50 AM

    Gibson, 

    Sorry to hear that ... but unfortunately yes, web console got the last update with 6.9SP1 i believe and there's no changes to it after. Thus some functionality is indeed broken. 

    You are saying that you don't want to let techs to 32bit console. But are you aware that you can specify exactly how much they can do there? If you would install them remote console and specify the rights (scheduling a job for example but denying the modification/delete for all the jobs) then this should do the trick for you?

     



  • 8.  RE: DSWEB 6.9 sp5 - can't schedule jobs in future

    Posted Nov 29, 2011 02:53 PM

    at my last job the help desk used dsweb and was able to schedule tasks in the future without issue, running DS 6.9 sp2.  perhaps the only difference there was that the servers were running 2003, not 2008, and i think sql was 2005.

    if it is an issue with the OS and/or SQL, then symantec needs to review/revise their product compatibility matrix.  as a customer, i would assume that 100% of the product works if symantec says that the OS/DB solution i have is compatible.  

    yes i'm familiar with DS permissions - we use them now to keep the techs from breaking things in the web console, since it's possible to do so there.  the main problem with giving the techs the 32bit console is training and support.  The sad part is that everyone in my department honestly believes that it will be easier for us to write a web app that holds your hand through the entire process than it would be to train and support the techs on a new (to them) console.  Plus we don't want that many concurrent connections to SQL from them leaving their consoles open all the time (because they never close anything).