Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Source Safe / May 2004

Tip: Looking for answers? Try searching our database.

SSDIR Error

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
alangham - 08 Apr 2004 16:51 GMT
I've got a batch file that I use to run a nightly compile of the latest version of code in SourceSafe. When I run it from the command line it works fine, however when I run it as a scheduled task (NT Server) I get the following error

No VSS database (srcsafe.ini) found.  Use the SSDIR environment variable or run netsetup

In the batch file I manually set this variable, e.g., set SSDIR=\\<some server>\<vss share>, and I've also tried set SSDIR=E:

Additionally, the scheduled task is set to run as me (and I already have the SSDIR set) in the correct startup directory

I've searched for a solution and haven't been able to find anything

Any help will be greatly appreciated! Thanks

Arthur
Richard J - 09 Apr 2004 13:31 GMT
Alan,

If possible, set up the SSDIR as a System environment variable.  The VSS database information should never change (or at least not daily).  Then when the scheduled task runs, it will read the environment variables and find it.  I believe, not sure so someone correct me if I am mistaken, but it sounds like the NT Server scheduler is not recognizing user environment variables

Give it a try; can't hurt.  Hopefully it will help out
Richar
   
    ----- alangham wrote: ----
   
    I've got a batch file that I use to run a nightly compile of the latest version of code in SourceSafe. When I run it from the command line it works fine, however when I run it as a scheduled task (NT Server) I get the following error
   
    No VSS database (srcsafe.ini) found.  Use the SSDIR environment variable or run netsetup
   
    In the batch file I manually set this variable, e.g., set SSDIR=\\<some server>\<vss share>, and I've also tried set SSDIR=E:
   
    Additionally, the scheduled task is set to run as me (and I already have the SSDIR set) in the correct startup directory
   
    I've searched for a solution and haven't been able to find anything
   
    Any help will be greatly appreciated! Thanks
   
    Arthur
alangham@yahoo.com - 15 Apr 2004 16:26 GMT
Richard,

That variable already exists as well.

Arthur

>-----Original Message-----
>Alan,
>
>If possible, set up the SSDIR as a System environment variable.  The VSS database information should never
change (or at least not daily).  Then when the scheduled
task runs, it will read the environment variables and find
it.  I believe, not sure so someone correct me if I am
mistaken, but it sounds like the NT Server scheduler is
not recognizing user environment variables.

>Give it a try; can't hurt.  Hopefully it will help out.
>Richard
>    
>     ----- alangham wrote: -----
>    
>     I've got a batch file that I use to run a nightly compile of the latest version of code in SourceSafe. When
I run it from the command line it works fine, however when
I run it as a scheduled task (NT Server) I get the
following error:
>    
>     No VSS database (srcsafe.ini) found.  Use the SSDIR environment variable or run netsetup.
>    
>     In the batch file I manually set this variable, e.g., set SSDIR=\\<some server>\<vss share>, and I've also
tried set SSDIR=E:.
>    
>     Additionally, the scheduled task is set to run as me (and I already have the SSDIR set) in the correct startup
directory.
>    
>     I've searched for a solution and haven't been able to find anything.
[quoted text clipped - 3 lines]
>     Arthur
>.
Joe Masters - 21 Apr 2004 06:18 GMT
Try verifying all the things you think you're setting. Run a batch file with
all those same settings, but instead of running VSS, write things out to a
file, like the user name, the ssdir and ssuser environment variables, the
current path, and anything else you can think of.

Joe

> Richard,
>
[quoted text clipped - 42 lines]
> >     Arthur
> >.
Jim Atwood - 06 May 2004 22:23 GMT
What user do you have your scheduled task running as?  If this user
(ususally System) does not have access to the network or the server in
question, then you get this sort of error.

Hope that helps,
Jim Atwood

> Richard,
>
[quoted text clipped - 53 lines]
>>    Arthur
>>.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.