getting "Error 1314 from CreateProcessAsUser" when using xp_cmdshe

Hi All,
After setting the proxy account, I'm getting this error msg. I've read
articles to set the "Increase Quotas" setting but can't find it in the list.
We're running on Windows 2003. Also, if and when I do find it, what do I se
t
it to?
Thanks,
BNBasically, SQL cannot spawn a new process using the existing credentials. OS
error 1314 translates to "A required privilege is not held by the client."
Make sure that the proxy and SQL start-up accounts have the "Act as part of
the operating system" privilege.
Adrian
"OutlookNewbieDev" <OutlookNewbieDev@.discussions.microsoft.com> wrote in
message news:E440EF6B-6080-4BAF-A2B5-1A56C6067A45@.microsoft.com...
> Hi All,
> After setting the proxy account, I'm getting this error msg. I've read
> articles to set the "Increase Quotas" setting but can't find it in the
> list.
> We're running on Windows 2003. Also, if and when I do find it, what do I
> set
> it to?
> Thanks,
> BN
>

getting "Error 1314 from CreateProcessAsUser" when using xp_cmdshe

Hi All,
After setting the proxy account, I'm getting this error msg. I've read
articles to set the "Increase Quotas" setting but can't find it in the list.
We're running on Windows 2003. Also, if and when I do find it, what do I set
it to?
Thanks,
BN
Basically, SQL cannot spawn a new process using the existing credentials. OS
error 1314 translates to "A required privilege is not held by the client."
Make sure that the proxy and SQL start-up accounts have the "Act as part of
the operating system" privilege.
Adrian
"OutlookNewbieDev" <OutlookNewbieDev@.discussions.microsoft.com> wrote in
message news:E440EF6B-6080-4BAF-A2B5-1A56C6067A45@.microsoft.com...
> Hi All,
> After setting the proxy account, I'm getting this error msg. I've read
> articles to set the "Increase Quotas" setting but can't find it in the
> list.
> We're running on Windows 2003. Also, if and when I do find it, what do I
> set
> it to?
> Thanks,
> BN
>

getting "Error 1314 from CreateProcessAsUser" when using xp_cmdshe

Hi All,
After setting the proxy account, I'm getting this error msg. I've read
articles to set the "Increase Quotas" setting but can't find it in the list.
We're running on Windows 2003. Also, if and when I do find it, what do I set
it to?
Thanks,
BNBasically, SQL cannot spawn a new process using the existing credentials. OS
error 1314 translates to "A required privilege is not held by the client."
Make sure that the proxy and SQL start-up accounts have the "Act as part of
the operating system" privilege.
Adrian
"OutlookNewbieDev" <OutlookNewbieDev@.discussions.microsoft.com> wrote in
message news:E440EF6B-6080-4BAF-A2B5-1A56C6067A45@.microsoft.com...
> Hi All,
> After setting the proxy account, I'm getting this error msg. I've read
> articles to set the "Increase Quotas" setting but can't find it in the
> list.
> We're running on Windows 2003. Also, if and when I do find it, what do I
> set
> it to?
> Thanks,
> BN
>sql

Getting - Setting Environment Variables

Hi,

1st. Issue

I have written a package that uses an environmet variable which contains certain information that the user must enter. A sql script task will then get the information from the environment variable and manipulate it.

I don't have a problem programmatically getting information from the environment variable. However, when I manually edit the contents of the environment variable, the changes won't take place unless the box is rebooted. Is there a way to refresh environment variables without rebooting?

2nd. Issue

I have written another package that also reads data from an environment variable but it must also manipulate the data and save the changes to the environment variable.

I have accomplished this programmatically by using GetEnvironmentVariable() and SetEnvironmentVariable(), but unfortunately the changes live during program execution only. Afte the program executes, the changes are wiped out.

How can I make changes stick to environment variables (programmatically)?

-- I found a solution to this:

When programmatically getting and/or setting an environment variable the 'target' parameter must be specified in the method call. By 'target' I mean the location in the registry where your environment variable is stored.

GetEnvironmentVariable( var, target )

SetEnvironmentVariable( OldValue, NewValue, target )

Please visit this link for more info:

http://msdn2.microsoft.com/en-us/library/96xafkes.aspx

GetDate() in Constraint using user's system time, Stored Proc using Server's.

All,

I have a table that has a Default Constraint for setting a DateTime field. I have a stored procedure that calls data from the table where the date field is <= GetDate().

I performed the following test:

1. Called insert stored proc and checked date field for recently added entry by query window ( 2007-03-01 11:09:44.000 ). This matches my (user) system date and time.

2. Immediately call GetDate() from the query window (2007-03-01 11:07:47.727). I assume this is the Server system date and time.

*note: These servers are on separate domains and therefore could have different system times.

This causes my select stored procedure to NOT return the values I just entered.

Any ideas on why this might occur? Does GetDate() run within the context of it's call (ie Called from application, uses web server system time, but called from query window uses server)?

If more that one server is involved I would check the system time delta between them and compare that to what you see in your test. In my experience two servers in the same domain getting time from the same server can be off by minutes...depending on how often they poll.|||

Todd:

Are you saying that you are trying to have the trigger update a datetime field and then use the getdate() function to try match the inserted record? If so, that is not a very good idea; this procedure will not be "tight" enough.

Also, if you are trying to use getdate() as method of "water-marking" records so that you can dynamically process records according to whether or not they are greater than or equal to the getdate() watermark, that kind of process will also "leak" records from time to time. This is a problem that I have battled a number of times. I can put together a mock-up to demonstrate that leakage problem if you would like.

sql