You have to be a sysadmin to start it up, according to this page:

http://dbforums.com/arch/71/2003/6/832887

also, this KB article says something about the Certificate Authority name...

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q302/4/09.ASP&NoWebContent=1&NoWebContent=1

any help?

Don't know if it's exactly the same error message, but I've found you have to be logged in locally to start the Agent service; ie, you can't start up EM...

Please don't crosspost. This is the other forum post:

http://www.sqlservercentral.com/forum/topic.asp?TOPIC_ID=14456&FORUM_ID=23&CAT_ID=2&Topic_Title=procedure&Forum_Title=General

No problem. I guess I have a bit of a prejudice against cursors in stored procedures...

When you are stuck in a situation like that, choose to do the simplest stored procedure you can, returning the data to ASP, then using procedural code to format it....

You would need to do LEFT JOINs to your lookup tables, otherwsie you will end up showing only those records that have records in both lookup tables. Plus, not...

To get a list of the columns in a specific table:

declare @TableName varchar(150)

--

select sc.*  

from syscolumns sc 

inner join sysobjects so on so.id = sc.id

inner...

select si.name, count(*) 

from syscolumns sc 

inner join sysobjects so on so.id = sc.id

inner join sysindexes si on si.id = so.id

where si.indid < 2

and so.type =...

Investigate removing permissions from any public user, then using the Access Workgroup file to control permissions. Just a warning, it can get very complicated.

What data is going into the dropdown and the listbox? Please post either the script you have already, or a table schema with an explanation as to what data...

We've seen this happen a couple times on joins to derived tables, but never seen it happen from two permanent tables with an inner join. This code looks like...

Are you sure it wasn't Quest software's Spotlight on SQL? Maybe an eval version was installed?

There is absolutely no shame in asking a valid question. The only poor question is the one not asked. Please keep forum posts respectful of other's abilities and...

And before anyone points it out, I'd like to state that I deliberately LEFT OUT transactions from the procedure I posted to give some weight to the fact that the...

paras_98:

first, don't prefix your procedures with "sp_". SQL Server looks in system tables first when it is asked to execute a proc starting with sp_; this will only slow...