Try
running this from the command line on the build box while being logged in as the
same account under which draco.net service is running.
set ssdir=C:\Program Files\Microsoft Visual
Studio\VSS\
"C:\Program Files\Microsoft Visual
Studio\VSS\win32\ss.exe" history
"$/FocusClients/BrisbaneWater/Dev/WebApp/FocusCoordinators_V1.0.0" -R -I-N
-
The thing that
seems most like: Is your source safe
database really in "C:\Program Files\Microsoft Visual Studio\VSS\"
?
The SSDIR
should be the directory in which the srcsafe.ini file is found, seems like maybe
your ss database is somewhere else?
If the ss
database is on the network somewhere, make sure that the account under which
draco.net service is running has permissions over there (so if it is set to
system account, make it run under a network account)
Let us know if
you are still having problems or if this helps out.
-Michael
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of srikant charala
Sent: Wednesday, August 11, 2004 04:01
To: [EMAIL PROTECTED]
Subject: [Draconet-users] help on Warning: SS.EXE exit code: 100
hi! friends,
i'm new to draco.net. here i'm facing a problem with the VSS database. i'm
attaching the log and the config file for your perusal. please guide me through
it. --
LOG ---
8/11/2004 4:16:18 PM - Brisbane Water : Checking module for
changes
8/11/2004 4:16:18 PM - Detected path: C:\Program Files\Microsoft Visual Studio\VSS\win32
8/11/2004 4:16:18 PM - HISTORY arguments: history "$/FocusClients/BrisbaneWater/Dev/WebApp/FocusCoordinators_V1.0.0" -R -I-N -Vd"8/11/2004;4:16P~8/11/2004;12:08P" [EMAIL PROTECTED]:\WINDOWS\TEMP\tmpF5.tmp
8/11/2004 4:16:18 PM - Warning: SS.EXE exit code: 100
8/11/2004 4:16:18 PM - Brisbane Water : Detected no changes to module
8/11/2004 4:16:18 PM - Detected path: C:\Program Files\Microsoft Visual Studio\VSS\win32
8/11/2004 4:16:18 PM - HISTORY arguments: history "$/FocusClients/BrisbaneWater/Dev/WebApp/FocusCoordinators_V1.0.0" -R -I-N -Vd"8/11/2004;4:16P~8/11/2004;12:08P" [EMAIL PROTECTED]:\WINDOWS\TEMP\tmpF5.tmp
8/11/2004 4:16:18 PM - Warning: SS.EXE exit code: 100
8/11/2004 4:16:18 PM - Brisbane Water : Detected no changes to module
CONFIG FILE ---
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<configSections>
<!--
Register Draco's custom configuration section. The configuration parser
will delegate control to the ConfigurationSection class when it encounters
the <draco> element
-->
<section name="draco" type="Chive.Draco.Config.ConfigurationSection, Draco" />
</configSections>
<startup>
<supportedRuntime version="v1.1.4322"/>
<requiredRuntime version="v1.1.4322" safemode="true"/>
</startup>
<system.diagnostics>
<switches>
<!--
This switch controls general messages. In order to receive general
trace messages change the value to the appropriate level. "1" gives
error messages, "2" gives errors and warnings, "3" gives more
detailed error information, and "4" gives verbose trace information
-->
<add name="TraceLevelSwitch" value="4" />
</switches>
<trace autoflush="true" indentsize="4">
<listeners>
<!--
Logs all output to a file called draco.log that will be created in
the configuration directory (the directory containing modifications.xsl)
-->
<add name="Draco"
type="Chive.Draco.Util.FileTraceListener, Draco" />
<!--
We do not require require the default TraceListener which logs
output to the console. This is meaningless since Draco runs
as a Window Service
-->
<remove name="Default"/>
</listeners>
</trace>
</system.diagnostics>
<!-- Configures Draco remoting -->
<system.runtime.remoting>
<application>
<service>
<!--
The server-activated, singleton remote object
-->
<wellknown mode="Singleton"
objectUri="Draco"
type="Chive.Draco.DracoRemote, Draco" />
</service>
<!--
Register a tcp channel listening on port 8086
-->
<channels>
<channel ref="tcp" port="8086">
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full" />
</serverProviders>
<clientProviders>
<formatter ref="binary" />
</clientProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>
<draco xmlns="http://www.chive.com/draco">
<configuration>
<configSections>
<!--
Register Draco's custom configuration section. The configuration parser
will delegate control to the ConfigurationSection class when it encounters
the <draco> element
-->
<section name="draco" type="Chive.Draco.Config.ConfigurationSection, Draco" />
</configSections>
<startup>
<supportedRuntime version="v1.1.4322"/>
<requiredRuntime version="v1.1.4322" safemode="true"/>
</startup>
<system.diagnostics>
<switches>
<!--
This switch controls general messages. In order to receive general
trace messages change the value to the appropriate level. "1" gives
error messages, "2" gives errors and warnings, "3" gives more
detailed error information, and "4" gives verbose trace information
-->
<add name="TraceLevelSwitch" value="4" />
</switches>
<trace autoflush="true" indentsize="4">
<listeners>
<!--
Logs all output to a file called draco.log that will be created in
the configuration directory (the directory containing modifications.xsl)
-->
<add name="Draco"
type="Chive.Draco.Util.FileTraceListener, Draco" />
<!--
We do not require require the default TraceListener which logs
output to the console. This is meaningless since Draco runs
as a Window Service
-->
<remove name="Default"/>
</listeners>
</trace>
</system.diagnostics>
<!-- Configures Draco remoting -->
<system.runtime.remoting>
<application>
<service>
<!--
The server-activated, singleton remote object
-->
<wellknown mode="Singleton"
objectUri="Draco"
type="Chive.Draco.DracoRemote, Draco" />
</service>
<!--
Register a tcp channel listening on port 8086
-->
<channels>
<channel ref="tcp" port="8086">
<serverProviders>
<formatter ref="binary" typeFilterLevel="Full" />
</serverProviders>
<clientProviders>
<formatter ref="binary" />
</clientProviders>
</channel>
</channels>
</application>
</system.runtime.remoting>
<draco xmlns="http://www.chive.com/draco">
<!--
The number of seconds between polling a module for changes.
e.g. a value of 600 means that the module will be checked for
changes every 10 minutes.
-->
<pollperiod>6</pollperiod>
<!--
The number of seconds the repository must be idle for a build
to occur.
-->
<quietperiod>60</quietperiod>
<!--
The domain name or IP address of of your SMTP email server.
-->
<mailserver>tiger.india.surpac.com</mailserver>
The number of seconds between polling a module for changes.
e.g. a value of 600 means that the module will be checked for
changes every 10 minutes.
-->
<pollperiod>6</pollperiod>
<!--
The number of seconds the repository must be idle for a build
to occur.
-->
<quietperiod>60</quietperiod>
<!--
The domain name or IP address of of your SMTP email server.
-->
<mailserver>tiger.india.surpac.com</mailserver>
<!--
The email address that all email notifications are sent from.
-->
<fromaddress>[EMAIL PROTECTED]</fromaddress>
The email address that all email notifications are sent from.
-->
<fromaddress>[EMAIL PROTECTED]</fromaddress>
<!--
This element contains a build child element for each module that
is to be polled and rebuilt whenever a change is detected.
-->
<builds>
<!--
This is the first module that will be monitored and built whenever a change is detected.
-->
<build>
<!--
A unique name for the build (mandatory). Will appear in log output etc.
-->
<name>Brisbane Water</name>
<!--
Optionally override the pollperiod and quietperiod for this build only.
<pollperiod>10</pollperiod>
<quietperiod>30</quietperiod> -->
<notification>
<!--
A set of email addresses that will be sent notifications of modifcations
and build attempts.
-->
<email>
<recipient>[EMAIL PROTECTED]</recipient>
</email>
<!--
A directory to write the build results to after each build attempt.
-->
<file>
<dir>C:\Working\BuildOutput</dir>
</file>
</notification>
<!--
Configuration for the NAnt build tool.
-->
<nant>
<!--
The name and path to the NAnt build file to be executed. If a path
is given then it should be relative to the module's root directory.
-->
<buildfile>FocusCoordinators_V1.0.0/FocusCoordinators_V1.0.0.build</buildfile>
This element contains a build child element for each module that
is to be polled and rebuilt whenever a change is detected.
-->
<builds>
<!--
This is the first module that will be monitored and built whenever a change is detected.
-->
<build>
<!--
A unique name for the build (mandatory). Will appear in log output etc.
-->
<name>Brisbane Water</name>
<!--
Optionally override the pollperiod and quietperiod for this build only.
<pollperiod>10</pollperiod>
<quietperiod>30</quietperiod> -->
<notification>
<!--
A set of email addresses that will be sent notifications of modifcations
and build attempts.
-->
<email>
<recipient>[EMAIL PROTECTED]</recipient>
</email>
<!--
A directory to write the build results to after each build attempt.
-->
<file>
<dir>C:\Working\BuildOutput</dir>
</file>
</notification>
<!--
Configuration for the NAnt build tool.
-->
<nant>
<!--
The name and path to the NAnt build file to be executed. If a path
is given then it should be relative to the module's root directory.
-->
<buildfile>FocusCoordinators_V1.0.0/FocusCoordinators_V1.0.0.build</buildfile>
<!--
One or more explicit targets to execute, seperated by spaces.
If not specified, the default target will be executed.
-->
<targets>build</targets>
One or more explicit targets to execute, seperated by spaces.
If not specified, the default target will be executed.
-->
<targets>build</targets>
<!--
A set of properties that should be passed to the NAnt build file via
the -D:name=value command line option.
-->
<!-- <properties>
<property name="property1" value="value1" />
<property name="property2" value="value2" />
</properties> -->
</nant>
<!--
Configuration for Visual SourceSafe.
-->
<vss>
<!--
The full path the the project in SourceSafe.
-->
<project>$/FocusClients/BrisbaneWater/Dev/WebApp/FocusCoordinators_V1.0.0</project>
<!--
The optional username and password.
-->
<username>Admin</username>
<password></password>
<!--
The path to the directory containing SRCSAFE.INI. In most cases SS.EXE is in
the VSS\WIN32 directory and by default will find a SRCSAFE.INI file in the VSS
directory. If you want SS.EXE to use a different SRCSAFE.INI, use this element.
-->
<!-- Local -->
<ssdir>C:\Program Files\Microsoft Visual Studio\VSS\</ssdir>
A set of properties that should be passed to the NAnt build file via
the -D:name=value command line option.
-->
<!-- <properties>
<property name="property1" value="value1" />
<property name="property2" value="value2" />
</properties> -->
</nant>
<!--
Configuration for Visual SourceSafe.
-->
<vss>
<!--
The full path the the project in SourceSafe.
-->
<project>$/FocusClients/BrisbaneWater/Dev/WebApp/FocusCoordinators_V1.0.0</project>
<!--
The optional username and password.
-->
<username>Admin</username>
<password></password>
<!--
The path to the directory containing SRCSAFE.INI. In most cases SS.EXE is in
the VSS\WIN32 directory and by default will find a SRCSAFE.INI file in the VSS
directory. If you want SS.EXE to use a different SRCSAFE.INI, use this element.
-->
<!-- Local -->
<ssdir>C:\Program Files\Microsoft Visual Studio\VSS\</ssdir>
<!--
Server
-->
<!-- <ssdir>\\server02\vss</ssdir> -->
</vss>
</build>
<!--
Add additional modules here.
-->
</builds>
<!-- <ssdir>\\server02\vss</ssdir> -->
</vss>
</build>
<!--
Add additional modules here.
-->
</builds>
</draco>
</configuration>
</configuration>
cheers,
shrikant :)
Yahoo! India Matrimony: Find your life partner online.
