VBScript builds an Project but hangs on proj start date

[mgirdner]

I have a VBScript that gets called from a web server. It creates an MS Project project. In my development environment it works as designed. In production environment, when the script executes, I get ~20 dialog boxes that appear on the web server console that say:
The start of task [n] [task name] Task of "Project 1" is before the project starts.

As far as I can tell, all the config params are the same between my working Dev instance of MSProj and my production instance.
Does this ring any bells?

As a work around, I thought that I could merely set the Project Start Date to some early date in the VBscript but have also failed at getting that to take.

I've tried:
Set objProject = WScript.CreateObject("MsProject.Application")
objProject.FileNew()
objProject.ProjectSummaryInfo "Start", "1/1/2002"

...but I get an "argument value is not valid" error.

Any help would be appreciated

 

[PDQBach]

Since your code works in Dev but not in Prod, I doubt the issue is with your code.

Use your VB script to create a project file in Prod with no tasks, no resources. Then compare system settings and Project settings between the Dev and Prod environments.

Consider, too, looking at things like the default system date format.

I dunno ... I'm really stretching here.

When you do find out, please post back here so we can all learn from your experience. Thanks.

 

[mgirdner]

Thanks PDQBach for the suggestion. I'll give that a shot tomorrow.
Here's another quirky data point:
When I manually log into the prod web server console and manually execute the vbscript, it executes flawlessly. It's almost as if the "default" configuration of MSProject -- i.e. the one instance of MSP that gets called from the web app server -- has different config parameters set than the instance on my user session. And if so, I don't know how to override the default behavior of that instance.
I've spent several days pulling out my hair on this and that's what's lead me to try the alternative approach and try to override the default Project Start Date of [today] to some early date -- to keep MS Project from stalling with the dialog boxes. Any insight on what I might be doing wrong syntactically or otherwise?

 

[PDQBach]

I have nothing else! (You're working way outside the area where I have any experience ... sure sounds like fun, though ... you guys hiring? <"jest" kidding>)