Need Project Tracking software

SourceGear's Dragnet is cheap and it ties in really well with their most
awesome source control provider (vault)
http://sourcegear.com/
FogBugz is popular and also cheap
[url]http://www.fogcr.com/FogBugz/[/url]
There's the Issue Tracker Starter Kit which is free:
http://www.asp.net/starterkits/down...index=0&tabid=1
Karl
--
MY ASP.Net tutorials
http://www.openmymind.net/
http://openmymind.net/redirector.aspx?documentId=51 - Learn about AJAX!
"Antonio" <blarfoc@.yahoo.com> wrote in message
news:1135094223.837753.13100@.z14g2000cwz.googlegroups.com...
> Hi, sorry for the OT question but the readers opinions will matter more
> to me.
> I team lead a small development team of .net and sql programmers.
> There is another team in our group like ours. We are tracking our
> project requests and statuses in Excel as it is shared with people
> ourside our teams who also need update abilities.
> We're looking for a good project tracking software for teams like ours.
> It can be web based preferrably.
> PLEASE PLEASE do not tell me to have us write it ourselves. :-) We
> can but need to focus on our dev projects.
> can you readers suggest some of the 3rd party project tracking and
> request applications that you use today that you would recommend?
> Thanks!
>"Karl Seguin" <karl REMOVE @. REMOVE openmymind REMOVEMETOO . ANDME net>
wrote in news:enNTu$XBGHA.3408@.TK2MSFTNGP12.phx.gbl:

> SourceGear's Dragnet is cheap and it ties in really well with their most
> awesome source control provider (vault)
> http://sourcegear.com/
We use Vault + Dragnet. Vault works wonderfully... but I find that DragNet
needs additional refinement.
Stan Kee (spamhoneypot@.rogers.com)

Need help with xp_cmdshell and proxy accout

I am tracking down a problem using xp_cmdshell on SQLServer 2000 (MSDE). Th
e
DB user is not a sysadmin, but does have exec rights for xp_cmdshell. I als
o
have an agent proxy account (Win2K account) set which is a member of “User
s”
group. This scheme has been working fine until I made some changes recently.
The changes I made are: Applied Win2K SP4, applied a host of hotfixes, and
made several changes in user rights and other security-related settings.
I’ve been testing this from OSQL logged in as the same user that my
application uses when it attaches to SQLServer. I get this error:
“xpsql.cpp: Error 1385 from LogonUserW on line 488”. Another issue whic
h I
think is related is that if I run xp_sqlagent_proxy_account to set the proxy
account, I get this error: “Specified user can not login”. Interestingl
y, if
I make the proxy account a member of the Administrators group, then I can se
t
the proxy account and I can execute xp_cmdshell.
Does anyone know what rights (Win2K rights) are required for SQLServer to
run xp_cmdshell, and what rights are required for the proxy account? By
rights I mean things like: Impersonate another user, logon as a batch job,
logon locally, logon as a service, and so on. This almost certainly has
something to do with rights, but I haven’t been able to isolate it yet. C
an
anyone suggest anything else to try that might help identify the problem?
Thanks,
CraigFor anyone interested, I have found the answer. The proxy account must have
the logon right "Log on as a batch job".
"Craig Daniel" wrote:

> I am tracking down a problem using xp_cmdshell on SQLServer 2000 (MSDE).
The
> DB user is not a sysadmin, but does have exec rights for xp_cmdshell. I a
lso
> have an agent proxy account (Win2K account) set which is a member of “Us
ers”
> group. This scheme has been working fine until I made some changes recentl
y.
> The changes I made are: Applied Win2K SP4, applied a host of hotfixes, and
> made several changes in user rights and other security-related settings.
> I’ve been testing this from OSQL logged in as the same user that my
> application uses when it attaches to SQLServer. I get this error:
> “xpsql.cpp: Error 1385 from LogonUserW on line 488”. Another issue wh
ich I
> think is related is that if I run xp_sqlagent_proxy_account to set the pro
xy
> account, I get this error: “Specified user can not login”. Interestin
gly, if
> I make the proxy account a member of the Administrators group, then I can
set
> the proxy account and I can execute xp_cmdshell.
> Does anyone know what rights (Win2K rights) are required for SQLServer to
> run xp_cmdshell, and what rights are required for the proxy account? By
> rights I mean things like: Impersonate another user, logon as a batch job,
> logon locally, logon as a service, and so on. This almost certainly has
> something to do with rights, but I haven’t been able to isolate it yet.
Can
> anyone suggest anything else to try that might help identify the problem?
> Thanks,
> Craig
>