error 18456 when running job

sql2k sp3
Ive got a job that creates a folder both on the local box
and on the remote box. This job has run every nite
successfully for a few weeks now. Last nite it failed with
message: Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
I havent changed anything security or services related.
The sql services for both boxes run in the same domain
admin account.
Any ideas?
Thanks, Chris.Try making the job owner sa. I've seen this and it ideespeared when I did that.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"chris" <chrisr@.fingps.com> wrote in message news:034901c36693$a4ce8750$a501280a@.phx.gbl...
> sql2k sp3
> Ive got a job that creates a folder both on the local box
> and on the remote box. This job has run every nite
> successfully for a few weeks now. Last nite it failed with
> message: Login failed for user 'NT AUTHORITY\ANONYMOUS
> LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
> I havent changed anything security or services related.
> The sql services for both boxes run in the same domain
> admin account.
> Any ideas?
> Thanks, Chris.

Error 18452

Hi,
I am getting Login failed for user 'sa'. Reason: Not associated with a
trusted SQL Server connection. [SQLSTATE 28000] when try to run a RPC call
from one sql server 2000 to an other sql 2000. I have setup/configure the
remote server connection on both servers and they have the same sa password
and same domain ids for the sql server and sql agent accounts. I have no
problem to run the same RPC command in query analyzer. But I get this error
when I try to run the call within a sql job and the job is own by sa. Any
help would be great.
This error is thrown when you try to connect to a SQL Server using a
"standard" SQL login (such as the sa account) but your SQL server is
configured to only accept Windows logins. To allow standard logins you
would need to to set up Mixed Mode security:
In enterprise manager:
Expand a server group.
Right-click a server, and then click Properties.
Click the Security tab.
Under Authentication, click SQL Server and Windows.
References:
See Books Online topic: Authentication Modes
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx
|||Yes, I use mix mode on all our sql servers and they have the same sp3a. The
funny things is that I have no problem run this RPC on all remote servers
(within the same site) but having this problem when I try to run the RPC to
remote servers (out of state and out of USA). Also I don't have this problem
on SQL 7.0 environment, I can run RPC to any where (local site or remote
site). As I stated below, I can run the RPC call in Query Analyzer login as
SA but I having problem to run that call in the sql job.
Thanks,
"Fany Vargas [MSFT]" wrote:

> This error is thrown when you try to connect to a SQL Server using a
> "standard" SQL login (such as the sa account) but your SQL server is
> configured to only accept Windows logins. To allow standard logins you
> would need to to set up Mixed Mode security:
> In enterprise manager:
> Expand a server group.
> Right-click a server, and then click Properties.
> Click the Security tab.
> Under Authentication, click SQL Server and Windows.
> References:
> See Books Online topic: Authentication Modes
> Fany Vargas
> Microsoft Corporation
> This posting is provided "AS IS" with no warranties, and confers no rights.
> Are you secure? For information about the Strategic Technology Protection
> Program and to order your FREE Security Tool Kit, please visit
> http://www.microsoft.com/security.
> Microsoft highly recommends that users with Internet access update their
> Microsoft software to better protect against viruses and security
> vulnerabilities. The easiest way to do this is to visit the following
> websites:
> http://www.microsoft.com/protect
> http://www.microsoft.com/security/guidance/default.mspx
>
>
|||1. Recreate your linked server. Provide more details on how your linked
server is created as well. Is it using sa login or NT authentication?
2. In enterprise manager -> Management->SQL Agent ->Properties->Connection
tab, try specifying sa account and with nt authentication. Does it now
execute successfully?
3. If job is not owned by sa does it run successfully - (try changing job
owner to a different account)?
Fany Vargas
Microsoft Corporation
This posting is provided "AS IS" with no warranties, and confers no rights.
Are you secure? For information about the Strategic Technology Protection
Program and to order your FREE Security Tool Kit, please visit
http://www.microsoft.com/security.
Microsoft highly recommends that users with Internet access update their
Microsoft software to better protect against viruses and security
vulnerabilities. The easiest way to do this is to visit the following
websites:
http://www.microsoft.com/protect
http://www.microsoft.com/security/guidance/default.mspx

Error 18210 Backup up SQL Server 2005 Database to network drive

I have 2 different servers that run nightly backup jobs to a network drive using the UNC format. I am noticing the larger databases encountering the following errors on a regular basis

Error: 18210, Severity: 16, State: 1.

'\\fnfssql3\SQLBackups\MNSQL05\<database>.BAK'. Operating system error 64(The specified network name is no longer available.).

BACKUP failed to complete the command BACKUP DATABASE <database>. Check the backup application log for detailed messages.

There are 5 databases on this server all backed up by the same job and 3 of them wortk fine and 2 of them fail so it is not a permissions problem. Have there been any problems with backing up to a network drive in 2005?

Well, backing up to networks drives is not officially *supported*, thats why the browser only display the local drives.

The reason for that and the logical explanation why you shouldn′t do that is, because the network is less reliable than local drives. If you want to make sure the database is backuped to network, you will have to either make sure the windows where the backups are streamed to the network don′t interfer with each other or you use a local backup to a drive and copy the files later over. Thats the most reliable option beside using a NAS / SAN.

Jens K. Suessmeyer

http://www.sqlserver2005.de

|||

Network hic-up can do this. One can see such error without sql involved.

Try trapping the error and retry the operation. Also, try backing up locally as suggested by Jens.

|||

Backing up database to a UNC path is fully supported. You must be thinking of running the database from a network drive.

http://support.microsoft.com/kb/304261

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/sqlbackuprest.mspx

|||

Oj,

the reason why I put *supported* in stars is, that it is sure supported, but not reliable in terms of just having a network share associated on a UNC share. (I thought he explanation should made that clearer, sorry for the poor explanation :-) ) The reliablity descrease due to your mentioned outages on the network. Having big backup files for the transfer over the network is there not recommended undless you have a SAN or a NAS which ensures more reliablity for the transfer. I often used the UNC path backup too on customer sites but either tried to shape the task to copy the files to different time windows or used a local backup and copied the files over with a mechanism (like xcopy / robocopy) to restart in the case of a connection loss.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Error 17827 from SQL Server 2005 Express Edition

Hi,
I'm using SQL server 2005 Express Edition in my solution and I've run into a
problem that I can't find any information about.
The application was running OK (for several days) until this happend just
out of the blue.
The application is written in C++ and we are using ADO to access the
database.
The authentication used with sql server user names and passwords.
I have not changed the password for any user
In the SQL server error log I found the following lines.
2007-03-15 01:34:01.13 Server Server resumed execution after being idle
209 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2007-03-15 02:34:01.61 Server Server resumed execution after being idle
213 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2007-03-15 03:11:00.78 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:00.78 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:00.80 Server Error: 17054, Severity: 16, State: 1.
2007-03-15 03:11:00.80 Server The current event was not reported to the
Windows Events log. Operating system error = 5(error not found). You may nee
d
to clear the Windows Events log if it is full.
2007-03-15 03:11:02.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:02.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:05.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:05.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:11.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:11.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:23.45 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:23.45 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:11:48.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:48.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:12:38.31 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:12:38.31 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:14:16.67 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:14:16.67 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:15:55.91 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:15:55.91 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
2007-03-15 03:17:35.19 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:17:35.19 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local mach
ine>]
Does anyone have any ideas why i get this behavior from SQL?
After we rebooted the system everything worked OK again.
Voja TadicVoja,
How many connections are being made to your SQL Express instance? Although
there is no hard limit to connections, there are resource limits on memory
and once those are used up, you will have problems.
Might you have many connections that should have closed during the several
successful days, but have not? If so, you many have many unused connections
still consuming resources.
The reason I ask is because the only instance of 17827 I see in technet is
SQL Server 2000 extended stored procedure related and means: The maximum
number of '%1!ld!' remote connections is currently in use.
Although that is not directly your error, it may be a hint as to the
underlying problem.
RLF
"vojat" <vojat@.discussions.microsoft.com> wrote in message
news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@.microsoft.com...
> Hi,
> I'm using SQL server 2005 Express Edition in my solution and I've run into
> a
> problem that I can't find any information about.
> The application was running OK (for several days) until this happend just
> out of the blue.
> The application is written in C++ and we are using ADO to access the
> database.
> The authentication used with sql server user names and passwords.
> I have not changed the password for any user
>
> In the SQL server error log I found the following lines.
>
> 2007-03-15 01:34:01.13 Server Server resumed execution after being
> idle
> 209 seconds: user activity awakened the server. This is an informational
> message only. No user action is required.
> 2007-03-15 02:34:01.61 Server Server resumed execution after being
> idle
> 213 seconds: user activity awakened the server. This is an informational
> message only. No user action is required.
> 2007-03-15 03:11:00.78 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:00.78 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:00.80 Server Error: 17054, Severity: 16, State: 1.
> 2007-03-15 03:11:00.80 Server The current event was not reported to
> the
> Windows Events log. Operating system error = 5(error not found). You may
> need
> to clear the Windows Events log if it is full.
> 2007-03-15 03:11:02.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:02.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:05.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:05.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:11.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:11.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:23.45 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:23.45 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:48.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:48.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:12:38.31 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:12:38.31 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:14:16.67 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:14:16.67 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:15:55.91 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:15:55.91 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:17:35.19 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:17:35.19 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
>
> Does anyone have any ideas why i get this behavior from SQL?
>
> After we rebooted the system everything worked OK again.
> Voja Tadic|||Hi,
I only use one connection for this application and I'm closing the
connection after each action to the database. I'm also using the connection
pooling functionality in ADO. This application uses the database alot.
I do have one additional application that uses ADO.DET and connects,
retrives data and dissconects and then terminats. This is done ~20-30 times
each day.
"Russell Fields" wrote:

> Voja,
> How many connections are being made to your SQL Express instance? Althoug
h
> there is no hard limit to connections, there are resource limits on memory
> and once those are used up, you will have problems.
> Might you have many connections that should have closed during the several
> successful days, but have not? If so, you many have many unused connectio
ns
> still consuming resources.
> The reason I ask is because the only instance of 17827 I see in technet i
s
> SQL Server 2000 extended stored procedure related and means: The maximum
> number of '%1!ld!' remote connections is currently in use.
> Although that is not directly your error, it may be a hint as to the
> underlying problem.
> RLF
> "vojat" <vojat@.discussions.microsoft.com> wrote in message
> news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@.microsoft.com...
>
>|||Voja,
I don't have any real good insight for you. You might look here for the
answer or someone to talk with:
http://blogs.msdn.com/sql_protocols.../23/558651.aspx
RLF
"vojat" <vojat@.discussions.microsoft.com> wrote in message
news:0ACE3553-246E-46EC-936D-5A57E1181A02@.microsoft.com...[vbcol=seagreen]
> Hi,
> I only use one connection for this application and I'm closing the
> connection after each action to the database. I'm also using the
> connection
> pooling functionality in ADO. This application uses the database alot.
> I do have one additional application that uses ADO.DET and connects,
> retrives data and dissconects and then terminats. This is done ~20-30
> times
> each day.
>
> "Russell Fields" wrote:
>

Error 17827 from SQL Server 2005 Express Edition

Hi,
I'm using SQL server 2005 Express Edition in my solution and I've run into a
problem that I can't find any information about.
The application was running OK (for several days) until this happend just
out of the blue.
The application is written in C++ and we are using ADO to access the
database.
The authentication used with sql server user names and passwords.
I have not changed the password for any user
In the SQL server error log I found the following lines.
2007-03-15 01:34:01.13 Server Server resumed execution after being idle
209 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2007-03-15 02:34:01.61 Server Server resumed execution after being idle
213 seconds: user activity awakened the server. This is an informational
message only. No user action is required.
2007-03-15 03:11:00.78 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:00.78 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:11:00.80 Server Error: 17054, Severity: 16, State: 1.
2007-03-15 03:11:00.80 Server The current event was not reported to the
Windows Events log. Operating system error = 5(error not found). You may need
to clear the Windows Events log if it is full.
2007-03-15 03:11:02.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:02.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:11:05.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:05.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:11:11.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:11.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:11:23.45 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:23.45 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:11:48.42 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:11:48.42 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:12:38.31 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:12:38.31 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:14:16.67 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:14:16.67 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:15:55.91 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:15:55.91 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
2007-03-15 03:17:35.19 Logon Error: 17827, Severity: 20, State: 1.
2007-03-15 03:17:35.19 Logon There was a failure while attempting to
encrypt a password. The connection has been closed. [CLIENT: <local machine>]
Does anyone have any ideas why i get this behavior from SQL?
After we rebooted the system everything worked OK again.
Voja Tadic
Voja,
How many connections are being made to your SQL Express instance? Although
there is no hard limit to connections, there are resource limits on memory
and once those are used up, you will have problems.
Might you have many connections that should have closed during the several
successful days, but have not? If so, you many have many unused connections
still consuming resources.
The reason I ask is because the only instance of 17827 I see in Technet is
SQL Server 2000 extended stored procedure related and means: The maximum
number of '%1!ld!' remote connections is currently in use.
Although that is not directly your error, it may be a hint as to the
underlying problem.
RLF
"vojat" <vojat@.discussions.microsoft.com> wrote in message
news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@.microsoft.com...
> Hi,
> I'm using SQL server 2005 Express Edition in my solution and I've run into
> a
> problem that I can't find any information about.
> The application was running OK (for several days) until this happend just
> out of the blue.
> The application is written in C++ and we are using ADO to access the
> database.
> The authentication used with sql server user names and passwords.
> I have not changed the password for any user
>
> In the SQL server error log I found the following lines.
>
> 2007-03-15 01:34:01.13 Server Server resumed execution after being
> idle
> 209 seconds: user activity awakened the server. This is an informational
> message only. No user action is required.
> 2007-03-15 02:34:01.61 Server Server resumed execution after being
> idle
> 213 seconds: user activity awakened the server. This is an informational
> message only. No user action is required.
> 2007-03-15 03:11:00.78 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:00.78 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:00.80 Server Error: 17054, Severity: 16, State: 1.
> 2007-03-15 03:11:00.80 Server The current event was not reported to
> the
> Windows Events log. Operating system error = 5(error not found). You may
> need
> to clear the Windows Events log if it is full.
> 2007-03-15 03:11:02.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:02.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:05.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:05.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:11.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:11.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:23.45 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:23.45 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:11:48.42 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:11:48.42 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:12:38.31 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:12:38.31 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:14:16.67 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:14:16.67 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:15:55.91 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:15:55.91 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
> 2007-03-15 03:17:35.19 Logon Error: 17827, Severity: 20, State: 1.
> 2007-03-15 03:17:35.19 Logon There was a failure while attempting to
> encrypt a password. The connection has been closed. [CLIENT: <local
> machine>]
>
> Does anyone have any ideas why i get this behavior from SQL?
>
> After we rebooted the system everything worked OK again.
> Voja Tadic
|||Hi,
I only use one connection for this application and I'm closing the
connection after each action to the database. I'm also using the connection
pooling functionality in ADO. This application uses the database alot.
I do have one additional application that uses ADO.DET and connects,
retrives data and dissconects and then terminats. This is done ~20-30 times
each day.
"Russell Fields" wrote:

> Voja,
> How many connections are being made to your SQL Express instance? Although
> there is no hard limit to connections, there are resource limits on memory
> and once those are used up, you will have problems.
> Might you have many connections that should have closed during the several
> successful days, but have not? If so, you many have many unused connections
> still consuming resources.
> The reason I ask is because the only instance of 17827 I see in Technet is
> SQL Server 2000 extended stored procedure related and means: The maximum
> number of '%1!ld!' remote connections is currently in use.
> Although that is not directly your error, it may be a hint as to the
> underlying problem.
> RLF
> "vojat" <vojat@.discussions.microsoft.com> wrote in message
> news:0AD8C694-B1B5-462A-9425-B8C791BE63E6@.microsoft.com...
>
>
|||Voja,
I don't have any real good insight for you. You might look here for the
answer or someone to talk with:
http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
RLF
"vojat" <vojat@.discussions.microsoft.com> wrote in message
news:0ACE3553-246E-46EC-936D-5A57E1181A02@.microsoft.com...[vbcol=seagreen]
> Hi,
> I only use one connection for this application and I'm closing the
> connection after each action to the database. I'm also using the
> connection
> pooling functionality in ADO. This application uses the database alot.
> I do have one additional application that uses ADO.DET and connects,
> retrives data and dissconects and then terminats. This is done ~20-30
> times
> each day.
>
> "Russell Fields" wrote:

Error 17052

I've got the following event in the event viewer of my server that run
SQL Server 2000, and it's getting stopped every 5 minutes, I don't kno
if this event and the crash have relation, if anyone know, please hel
me...
17052:
This SQL Server has been optimized for 8 concurrent queries. This limi
has been exceedec by 5 queries and performance may be adversel
affected.
Diego Modolo Ribeir
Harsmake
----
Posted via http://www.mcse.m
----
View this thread: http://www.mcse.ms/message389771.htmWhat version of SQL do you have and how many CPUs do U have configured for SQL
if more than 4 what is your MAXDOP(sp_configure 'Degree') run_value?|||You are running either MSDE or Personal Edition, and these 2 versions are
optimised for a maximum of 8 concurrent queries. When you have more, the
performance of your server will drop, and you might get time outs etc. You
will have to upgrade to SQL Server Standard Edition if you want to have more
concurrent queries.
--
Jacco Schalkwijk
SQL Server MVP
"Harsmaken" <Harsmaken.11kjeo@.mail.mcse.ms> wrote in message
news:Harsmaken.11kjeo@.mail.mcse.ms...
> I've got the following event in the event viewer of my server that runs
> SQL Server 2000, and it's getting stopped every 5 minutes, I don't know
> if this event and the crash have relation, if anyone know, please help
> me...
> 17052:
> This SQL Server has been optimized for 8 concurrent queries. This limit
> has been exceedec by 5 queries and performance may be adversely
> affected.
>
> Diego Modolo Ribeiro
>
> Harsmaken
> ---
> Posted via http://www.mcse.ms
> ---
> View this thread: http://www.mcse.ms/message389771.html
>|||Thanks for clearing this up Jacco..never encountered this before

Error 1612 - can't get Express installed

I have done all I can to resolve this on my own and would really appreciate any help anyone can give me. I have run uninstall utilities, followed a few MSDN reinstall methods, but all roads lead back to this vicious cycle:

The install hangs trying to install the prereq Microsoft SQL Server 2005 Setup Support Files with Error 1612. So I try to uninstall the Support files using Add/Remove..but the Windows Installer looks for "Microsoft SQL Server Native Client" disk, which of course I don't have because I install from downloads from Microsoft.

That's the very short version. I've got a ton of hours reading help groups, MSDN, trying everything.

I have posted the error log file below. Thanks in advance.

=== Verbose logging started: 1/25/2007 21:01:41 Build type: SHIP UNICODE 3.01.4000.2435 Calling process: c:\6b4bf5519a6c349936f69599\setup.exe ===
MSI (c) (2C:64) [21:01:41:265]: Resetting cached policy values
MSI (c) (2C:64) [21:01:41:265]: Machine policy value 'Debug' is 0
MSI (c) (2C:64) [21:01:41:265]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (c) (2C:64) [21:01:41:265]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (2C:64) [21:01:41:265]: Grabbed execution mutex.
MSI (c) (2C:64) [21:01:41:281]: Cloaking enabled.
MSI (c) (2C:64) [21:01:41:281]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (2C:64) [21:01:41:281]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (98:90) [21:01:41:296]: Grabbed execution mutex.
MSI (s) (98:E4) [21:01:41:296]: Resetting cached policy values
MSI (s) (98:E4) [21:01:41:296]: Machine policy value 'Debug' is 0
MSI (s) (98:E4) [21:01:41:296]: ******* RunEngine:
******* Product: {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
******* Action:
******* CommandLine: **********
MSI (s) (98:E4) [21:01:41:296]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (98:E4) [21:01:41:296]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (98:E4) [21:01:41:296]: User policy value 'DisableMedia' is 0
MSI (s) (98:E4) [21:01:41:296]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Looking for sourcelist for product {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Adding {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Now checking product {53F5C3EE-05ED-4830-994B-50B2F0D50FCE}
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Media is enabled for product.
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Source with value name '1' is blank
MSI (s) (98:E4) [21:01:41:296]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msi
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Processing net source list.
MSI (s) (98:E4) [21:01:41:296]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msi
MSI (s) (98:E4) [21:01:41:296]: SOURCEMGMT: Processing media source list.
MSI (s) (98:E4) [21:01:41:312]: Note: 1: 2203 2: 3: -2147287037
MSI (s) (98:E4) [21:01:41:312]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (98:E4) [21:01:41:312]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msi
MSI (s) (98:E4) [21:01:41:312]: SOURCEMGMT: Processing URL source list.
MSI (s) (98:E4) [21:01:41:312]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
MSI (s) (98:E4) [21:01:41:312]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msi
MSI (s) (98:E4) [21:01:41:312]: Note: 1: 1706 2: 3: SqlSupport.msi
MSI (s) (98:E4) [21:01:41:312]: SOURCEMGMT: Failed to resolve source
MSI (s) (98:E4) [21:01:41:312]: MainEngineThread is returning 1612
MSI (c) (2C:64) [21:01:41:312]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (2C:64) [21:01:41:312]: MainEngineThread is returning 1612
=== Verbose logging stopped: 1/25/2007 21:01:41 ===

hi,

jklegseth wrote:

I have done all I can to resolve this on my own and would really appreciate any help anyone can give me. I have run uninstall utilities, followed a few MSDN reinstall methods, but all roads lead back to this vicious cycle:

The install hangs trying to install the prereq Microsoft SQL Server 2005 Setup Support Files with Error 1612. So I try to uninstall the Support files using Add/Remove..but the Windows Installer looks for "Microsoft SQL Server Native Client" disk, which of course I don't have because I install from downloads from Microsoft.

try manually installing SQL Native Client before the SQLExpress installation by running the relative package (half the page down)

regards

|||

Hi Andrea,

I tried what you suggested. Here is what happens.

- I get a warning that "A lower version of this product has been detected on your stystem. Would you like to upgrade your existing installation?"

- I click Yes

- Install seems to go fine -- it shows me what will be installed, etc., until I get a window saying, "Insert the 'Microsoft SQL Native Client' disk and click OK.

|||

Update: Using Windows Install Cleanup I was able to get past the Native error. I think there was a registry entry for Native install that was no longer valid. I got through the SQL install only to have a new problem. Now, during the installation System Configuration Check I pass 14 of 15 tests. I get a warning for Com Plus Catalog Requirement.

The warning message is: "Com Plus Catalog Requirement (Warning), Messages: If SQL Server Setup fails, Setup will roll back....For more information, see How to: Work Around Com+ Check Failure in SQL Server Setup."

I followed the steps in that KB article but when I add Component Services in the Console and click on Com+ Applications, I get an error: "ERror Code 8004E00F - COM+ was unable to talk to the Microsoft Distributed Transaction Coordinator.

So I looked that up and found various articles but none that seemed to apply directly to my problem.

If I continue the SQL Server setup and ignore the warning, I get a successful install of Setup Support Files, VSS WRiter, Backwards Compatability, but get failed warnings on all the of the SQL Express 2005 components. I'm once again stumped. Any ideas?

Thanks for your help.

|||

Update #2

I was to get past the above issue by following the steps at http://www.pcreview.co.uk/forums/thread-1596796.php. MSXML6 then failed during SQL Server install, so I removed it and reinstalled it. I am very close now. The error I now get is: "An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name" I have followed the steps at http://blogs.msdn.com/astebner/archive/2005/12/08/501885.aspx but this has not resolved the. I can't believe how much time I've spent on this, but maybe this error is one you have encountered? I will keep searching and posting here so others with this issue can find help. If you have any ideas I would appreciate it.

Error 14266 - Is 11:59:59 PM not a valid time?

Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,
It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:

>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,
|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work.
The scheduling wizard assumes that the end time is 11:59:59 PM. This is
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it.
Then right click on the associated job. Select "All Tasks > Generate
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into a
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:[vbcol=seagreen]
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
> PM. I
> (valid
> saved."
bdatch
bdatch's Profile: http://www.msusenet.com/member.php?userid=675
View this thread: http://www.msusenet.com/t-3298150

Error 14266 - Is 11:59:59 PM not a valid time?

Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:

>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work.
The scheduling wizard assumes that the end time is 11:59:59 PM. This is
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it.
Then right click on the associated job. Select "All Tasks > Generate
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into a
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:[vbcol=seagreen]
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
>
> PM. I
> (valid
> saved."
bdatch
---
bdatch's Profile: http://www.msmcse.ms/member.php?userid=675
View this thread: http://www.msmcse.ms/t-3298150

Error 14266 - Is 11:59:59 PM not a valid time?

Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:
>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work
The scheduling wizard assumes that the end time is 11:59:59 PM. This i
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it
Then right click on the associated job. Select "All Tasks > Generat
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >I created a DTS package and wanted to schedule it to run at 11:59:5
> PM. I
> >could not save the schedule.
> >
> >An error "Error 14266: The specified '@.active_end_time' is invali
> (valid
> >values are: before or after @.active_start_time). The job was no
> saved."
> >
> >I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
> >11:59:59 PM not ?
> >
> >Please help
--
bdatc
----
bdatch's Profile: http://www.msusenet.com/member.php?userid=67
View this thread: http://www.msusenet.com/t-329815sql

Error 14262: specified @job_id... does not exist

Got a client who is getting this error when trying "Start synchronizing" on
a subscription in Enterprise Manager. When the subscription is run using the
Administrator account which originally created it, it runs OK. But when a
different account is being used, this error is thrown. Do subscriptions have
to be synchronized by the account which created them?
--
Mark
Is this a push or pull subscription? How is the subscription run?
The account should be in the PAL and the job owner should be the sa account.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
> Got a client who is getting this error when trying "Start synchronizing"
> on a subscription in Enterprise Manager. When the subscription is run
> using the Administrator account which originally created it, it runs OK.
> But when a different account is being used, this error is thrown. Do
> subscriptions have to be synchronized by the account which created them?
> --
> --
> Mark
>
|||It's a pull subscription to a merge replication.
--
Mark
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
> Is this a push or pull subscription? How is the subscription run?
> The account should be in the PAL and the job owner should be the sa
> account.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
> news:OKJGoHeFGHA.516@.TK2MSFTNGP15.phx.gbl...
>
|||I've seen this error when the subscription has been running, was deleted,
and then recreated. EM has cached the old job's information. Can you try a
refresh before trying to run the job again?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Mark Rendle" <markdotrendleatcomputersoftwaredotcom> wrote in message
news:%23mzaXIpFGHA.2012@.TK2MSFTNGP14.phx.gbl...
> It's a pull subscription to a merge replication.
> --
> --
> Mark
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:ukMaDdeFGHA.3056@.TK2MSFTNGP09.phx.gbl...
>

Error 14258: ... SQL ServerAgent is starting

Whenever I attempt to edit/run/... a scheduled job, I get the error message:
"Error 14258: Cannot perform this operation while SQL ServerAgent is
starting. Try again later."
I also notice that all scheduled jobs have "Date/time not available" in
"Next Run Date".
Of course Agent is not starting now, it has already started (Alerts and
Operators can be edited without a problem). The server is SQL2000, SP4.
Check the status of the service from Administrative Tools -
is the service Running or Starting?
Alerts and operators can be edited without Agent running.
Also check your Agent.out file.
-Sue
On Thu, 16 Feb 2006 03:55:29 -0800, "vsiat"
<vsiat@.discussions.microsoft.com> wrote:

>Whenever I attempt to edit/run/... a scheduled job, I get the error message:
>"Error 14258: Cannot perform this operation while SQL ServerAgent is
>starting. Try again later."
>I also notice that all scheduled jobs have "Date/time not available" in
>"Next Run Date".
>Of course Agent is not starting now, it has already started (Alerts and
>Operators can be edited without a problem). The server is SQL2000, SP4.
|||The service IS running. I restarted it to make sure though, as I also did
with the server and the machine; nothing worked. The service is reported to
be running in both enterprise manager and windows services but no scheduled
jobs can be edited/run/...etc.
Also, when I stop the service I can edit jobs or create new ones, but there
is no way to run them.
There is no Agent.out file.
"Sue Hoegemeier" wrote:

> Check the status of the service from Administrative Tools -
> is the service Running or Starting?
> Alerts and operators can be edited without Agent running.
> Also check your Agent.out file.
> -Sue
|||ok, I checked SQLAgent.out file. It has one entry:
"... ? [393] Waiting for SQL Server to recover databases..."
but I don't understand which databases it is recovering as there is no such
indication in SQL server logs or Current activity.
"Sue Hoegemeier" wrote:

> Check the status of the service from Administrative Tools -
> is the service Running or Starting?
> Alerts and operators can be edited without Agent running.
> Also check your Agent.out file.
> -Sue
|||If you tried stopping and then restarting just the Agent
service and it won't start, reporting the same error then my
guess would be that you are running SQL Server in
lightweight pooling mode. Set it back to the default of
thread mode.
sp_configure 'allow updates', 1
go
reconfigure with override
go
sp_configure 'lightweight pooling', 0
go
reconfigure with override
go
-Sue
On Fri, 17 Feb 2006 00:41:28 -0800, "vsiat"
<vsiat@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>ok, I checked SQLAgent.out file. It has one entry:
>"... ? [393] Waiting for SQL Server to recover databases..."
>but I don't understand which databases it is recovering as there is no such
>indication in SQL server logs or Current activity.
>
>"Sue Hoegemeier" wrote:

Error 14113 while trying to setup replication on SQL Server 2000 S

Hi,
I'm trying to run the wizard to setup replication on a SQL Server 2000 SP3.
Entering the parameters goes without a problem but when executing the script
I'm getting an error 14113:
SQL Server Enterprise MAnager could not configure 'XYZ' as the distributor
for 'XYZ'.
Error 14113: Could not execute c:\... \instdist.sql
I have all the necessary rights on the DB server and on Win 2003.
I also noticed that XP_CMDSHELL doesn't work on this server (probably needed
to execute the previous line) so I executed the instdist.sql manually in
query analyzer.
This clearly isn't enough to get replication working.
The problem with XP_CMDSHELL:
Msg 50001, Level 1, State 50001
xpsql.cpp: Error 1260 from CreateProcess on line 675
I already dropped XP_CMDSHELL:
exec sp_dropextendedproc 'xp_cmdshell'
then replaced the dll with one from another server (just in case) and
re-installed it:
exec sp_addextendedproc 'xp_cmdshell', 'xplog70.dll'
all with the same result.
IMHO both problems are related. Any suggestions?
Tanks in advance,
Gaston.
Can you try to run command shell from within query analyzer? Can you create
subfolders within your snapshot location?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Gaston" <Gaston@.discussions.microsoft.com> wrote in message
news:ADC431B8-38B5-477D-BE35-AFBF9D6903EC@.microsoft.com...
> Hi,
> I'm trying to run the wizard to setup replication on a SQL Server 2000
> SP3.
> Entering the parameters goes without a problem but when executing the
> script
> I'm getting an error 14113:
> SQL Server Enterprise MAnager could not configure 'XYZ' as the distributor
> for 'XYZ'.
> Error 14113: Could not execute c:\... \instdist.sql
> I have all the necessary rights on the DB server and on Win 2003.
> I also noticed that XP_CMDSHELL doesn't work on this server (probably
> needed
> to execute the previous line) so I executed the instdist.sql manually in
> query analyzer.
> This clearly isn't enough to get replication working.
> The problem with XP_CMDSHELL:
> Msg 50001, Level 1, State 50001
> xpsql.cpp: Error 1260 from CreateProcess on line 675
> I already dropped XP_CMDSHELL:
> exec sp_dropextendedproc 'xp_cmdshell'
> then replaced the dll with one from another server (just in case) and
> re-installed it:
> exec sp_addextendedproc 'xp_cmdshell', 'xplog70.dll'
> all with the same result.
> IMHO both problems are related. Any suggestions?
> Tanks in advance,
> Gaston.
>
|||If you mean if I can run "xp_cmdshell" fromwithin query analyzer: No, this
doesn't work.
The problem with XP_CMDSHELL:
> Msg 50001, Level 1, State 50001
> xpsql.cpp: Error 1260 from CreateProcess on line 675
And it seems that the OSQL command wouldn't even be executed, so the
distribution server can't be setup.
I can create subfolders on the snapshot location, np.
Thanks already,
Gaston.
"Hilary Cotter" wrote:

> Can you try to run command shell from within query analyzer? Can you create
> subfolders within your snapshot location?
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:ADC431B8-38B5-477D-BE35-AFBF9D6903EC@.microsoft.com...
>
>
|||I suspect this is your problem.
Can you reapply SP3, or better yet SP4 and try again?
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Gaston" <Gaston@.discussions.microsoft.com> wrote in message
news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...[vbcol=seagreen]
> If you mean if I can run "xp_cmdshell" fromwithin query analyzer: No, this
> doesn't work.
> The problem with XP_CMDSHELL:
> And it seems that the OSQL command wouldn't even be executed, so the
> distribution server can't be setup.
> I can create subfolders on the snapshot location, np.
> Thanks already,
> Gaston.
>
> "Hilary Cotter" wrote:
|||Hi Hilary,
The xp_cmdshell works after we applied SP4. So now we're on to the
replication problem. I suppose that this will work now as well!
Thanks for your efforts so far!
/Gaston Verelst
"Hilary Cotter" wrote:

> I suspect this is your problem.
> Can you reapply SP3, or better yet SP4 and try again?
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...
>
>
|||Hi Hilary,
The replication is up and running, thanks for your support!
Kind regards,
Gaston Verelst (Belgium)
"Hilary Cotter" wrote:

> I suspect this is your problem.
> Can you reapply SP3, or better yet SP4 and try again?
> --
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
> "Gaston" <Gaston@.discussions.microsoft.com> wrote in message
> news:667B866F-107F-47AB-9355-AC6C9CDF9CE5@.microsoft.com...
>
>

Error 13

I got an error 13 "Cannot resolve collation conflict for
equal to operation"
when trying to run some tasksThat means, you are trying to compare two character columns in your query,
but those columns are of different collations and hence the error.
Unless there's a good reason, all columns in the database should be of the
same collation. If you do need to have a different collation, then you need
to take care of that situation using the COLLATE keyword, in your queries.
if you run sp_help on the tables in question, you will see what collations
are being used by the table columns.
Look up SQL Server Books Online for more informaiton on collations and
COLLATE.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"krasi" <krkrastev@.tbicredit.bg> wrote in message
news:01f901c3de73$64587570$a001280a@.phx.gbl...
I got an error 13 "Cannot resolve collation conflict for
equal to operation"
when trying to run some tasks

Error 13

I got an error 13 "Cannot resolve collation conflict for
equal to operation"
when trying to run some tasksThat means, you are trying to compare two character columns in your query,
but those columns are of different collations and hence the error.
Unless there's a good reason, all columns in the database should be of the
same collation. If you do need to have a different collation, then you need
to take care of that situation using the COLLATE keyword, in your queries.
if you run sp_help on the tables in question, you will see what collations
are being used by the table columns.
Look up SQL Server Books Online for more informaiton on collations and
COLLATE.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm
"krasi" <krkrastev@.tbicredit.bg> wrote in message
news:01f901c3de73$64587570$a001280a@.phx.gbl...
I got an error 13 "Cannot resolve collation conflict for
equal to operation"
when trying to run some tasks

Error 120

Hello.
I'm trying to run the following statement:
insert into [destination table]
([fields])
select [fields] from [source table]
When I try to run it, I get the following error messages:
Server: Msg 120, Level 15, State 1, Line 8
The select list for the INSERT statement contains fewer
items than the insert list. The number of SELECT values
must match the number of INSERT columns.
Server: Msg 8180, Level 16, State 1, Line 8
Statement(s) could not be prepared.
The select list matches the insert list exactly.
The source and destination tables are located on two
different (linked) servers.
Both servers are running MSSQL 2000 SP3a.
What am I doing wrong?
Thank you.Without seeing the actual insert statement we can only guess. My guess
would be you have a space in one of the column names.
Andrew J. Kelly
SQL Server MVP
"Vlad Soare" <vsoare@.hotmail.com> wrote in message
news:12a5601c4432a$dcaeb0e0$a301280a@.phx
.gbl...
> Hello.
> I'm trying to run the following statement:
> insert into [destination table]
> ([fields])
> select [fields] from [source table]
> When I try to run it, I get the following error messages:
> Server: Msg 120, Level 15, State 1, Line 8
> The select list for the INSERT statement contains fewer
> items than the insert list. The number of SELECT values
> must match the number of INSERT columns.
> Server: Msg 8180, Level 16, State 1, Line 8
> Statement(s) could not be prepared.
> The select list matches the insert list exactly.
> The source and destination tables are located on two
> different (linked) servers.
> Both servers are running MSSQL 2000 SP3a.
> What am I doing wrong?
> Thank you.
>|||No, the statement is definitely OK, it works on other
servers, there's only one server it doesn't work on. And
it works if I run it locally, but it doesn't work when I
run it from another server.
Here are the statements:
declare @.IdSpatiu int,
@.IdTran int
set @.IdSpatiu = 15
set @.IdTran = 20
insert into [ts-331].Ploiesti.dbo.Factura
(IdSpatiu, IdTran, Numar)
select @.IdSpatiu, @.IdTran, Numar
from [ts-331].Deva.dbo.Factura
where IdTran = 11 and IdSpatiu = 9
If I replace "select @.IdSpatiu, @.IdTran, Numar"
with "select 15, 20, Numar", it works. It doesn't like
the variables in the select list.
If I'm connected to the server [ts-331], it works. But if
I'm connected to another server (to which ts-331 is
linked), it doesn't work.
It must be something about the ts-331 server. At first I
thought it must be the service pack, because it had no
service pack installed, but then I installed SP3a and the
problem persisted.
Thank you.

>--Original Message--
>Without seeing the actual insert statement we can only
guess. My guess
>would be you have a space in one of the column names.
>--|||It looks fine to me as well. Maybe there is something strange with the way
the Linked server is set up on that machine. Why do you want to do an
insert like that remotely anyway? It would be much cleaner if you had a
stored proc on the linked server that you call and pass in the 2 parameters.
That way the sp does not have to make any linked server calls at all when
actually doing the Insert.
Andrew J. Kelly
SQL Server MVP
"Vlad Soare" <vsoare@.hotmail.com> wrote in message
news:1318b01c443b8$d05fa8b0$a401280a@.phx
.gbl...
> No, the statement is definitely OK, it works on other
> servers, there's only one server it doesn't work on. And
> it works if I run it locally, but it doesn't work when I
> run it from another server.
> Here are the statements:
> declare @.IdSpatiu int,
> @.IdTran int
> set @.IdSpatiu = 15
> set @.IdTran = 20
> insert into [ts-331].Ploiesti.dbo.Factura
> (IdSpatiu, IdTran, Numar)
> select @.IdSpatiu, @.IdTran, Numar
> from [ts-331].Deva.dbo.Factura
> where IdTran = 11 and IdSpatiu = 9
> If I replace "select @.IdSpatiu, @.IdTran, Numar"
> with "select 15, 20, Numar", it works. It doesn't like
> the variables in the select list.
> If I'm connected to the server [ts-331], it works. But if
> I'm connected to another server (to which ts-331 is
> linked), it doesn't work.
> It must be something about the ts-331 server. At first I
> thought it must be the service pack, because it had no
> service pack installed, but then I installed SP3a and the
> problem persisted.
> Thank you.
>
> guess. My guess
>|||I had the same problem. Try this. I don't know why it works but it
does.
insert into [ts-331].Ploiesti.dbo.Factura
(IdSpatiu, IdTran, Numar)
select (select @.IdSpatiu), (select @.IdTran), Numar
from [ts-331].Deva.dbo.Factura
where IdTran = 11 and IdSpatiu = 9

Error 120

Hello.
I'm trying to run the following statement:
insert into [destination table]
([fields])
select [fields] from [source table]
When I try to run it, I get the following error messages:
Server: Msg 120, Level 15, State 1, Line 8
The select list for the INSERT statement contains fewer
items than the insert list. The number of SELECT values
must match the number of INSERT columns.
Server: Msg 8180, Level 16, State 1, Line 8
Statement(s) could not be prepared.
The select list matches the insert list exactly.
The source and destination tables are located on two
different (linked) servers.
Both servers are running MSSQL 2000 SP3a.
What am I doing wrong?
Thank you.
Without seeing the actual insert statement we can only guess. My guess
would be you have a space in one of the column names.
Andrew J. Kelly
SQL Server MVP
"Vlad Soare" <vsoare@.hotmail.com> wrote in message
news:12a5601c4432a$dcaeb0e0$a301280a@.phx.gbl...
> Hello.
> I'm trying to run the following statement:
> insert into [destination table]
> ([fields])
> select [fields] from [source table]
> When I try to run it, I get the following error messages:
> Server: Msg 120, Level 15, State 1, Line 8
> The select list for the INSERT statement contains fewer
> items than the insert list. The number of SELECT values
> must match the number of INSERT columns.
> Server: Msg 8180, Level 16, State 1, Line 8
> Statement(s) could not be prepared.
> The select list matches the insert list exactly.
> The source and destination tables are located on two
> different (linked) servers.
> Both servers are running MSSQL 2000 SP3a.
> What am I doing wrong?
> Thank you.
>
|||No, the statement is definitely OK, it works on other
servers, there's only one server it doesn't work on. And
it works if I run it locally, but it doesn't work when I
run it from another server.
Here are the statements:
declare @.IdSpatiu int,
@.IdTran int
set @.IdSpatiu = 15
set @.IdTran = 20
insert into [ts-331].Ploiesti.dbo.Factura
(IdSpatiu, IdTran, Numar)
select @.IdSpatiu, @.IdTran, Numar
from [ts-331].Deva.dbo.Factura
where IdTran = 11 and IdSpatiu = 9
If I replace "select @.IdSpatiu, @.IdTran, Numar"
with "select 15, 20, Numar", it works. It doesn't like
the variables in the select list.
If I'm connected to the server [ts-331], it works. But if
I'm connected to another server (to which ts-331 is
linked), it doesn't work.
It must be something about the ts-331 server. At first I
thought it must be the service pack, because it had no
service pack installed, but then I installed SP3a and the
problem persisted.
Thank you.

>--Original Message--
>Without seeing the actual insert statement we can only
guess. My guess
>would be you have a space in one of the column names.
>--
|||It looks fine to me as well. Maybe there is something strange with the way
the Linked server is set up on that machine. Why do you want to do an
insert like that remotely anyway? It would be much cleaner if you had a
stored proc on the linked server that you call and pass in the 2 parameters.
That way the sp does not have to make any linked server calls at all when
actually doing the Insert.
Andrew J. Kelly
SQL Server MVP
"Vlad Soare" <vsoare@.hotmail.com> wrote in message
news:1318b01c443b8$d05fa8b0$a401280a@.phx.gbl...
> No, the statement is definitely OK, it works on other
> servers, there's only one server it doesn't work on. And
> it works if I run it locally, but it doesn't work when I
> run it from another server.
> Here are the statements:
> declare @.IdSpatiu int,
> @.IdTran int
> set @.IdSpatiu = 15
> set @.IdTran = 20
> insert into [ts-331].Ploiesti.dbo.Factura
> (IdSpatiu, IdTran, Numar)
> select @.IdSpatiu, @.IdTran, Numar
> from [ts-331].Deva.dbo.Factura
> where IdTran = 11 and IdSpatiu = 9
> If I replace "select @.IdSpatiu, @.IdTran, Numar"
> with "select 15, 20, Numar", it works. It doesn't like
> the variables in the select list.
> If I'm connected to the server [ts-331], it works. But if
> I'm connected to another server (to which ts-331 is
> linked), it doesn't work.
> It must be something about the ts-331 server. At first I
> thought it must be the service pack, because it had no
> service pack installed, but then I installed SP3a and the
> problem persisted.
> Thank you.
> guess. My guess
>
|||I had the same problem. Try this. I don't know why it works but it
does.
insert into [ts-331].Ploiesti.dbo.Factura
(IdSpatiu, IdTran, Numar)
select (select @.IdSpatiu), (select @.IdTran), Numar
from [ts-331].Deva.dbo.Factura
where IdTran = 11 and IdSpatiu = 9

Error 120

Hello.
I'm trying to run the following statement:
insert into [destination table]
([fields])
select [fields] from [source table]
When I try to run it, I get the following error messages:
Server: Msg 120, Level 15, State 1, Line 8
The select list for the INSERT statement contains fewer
items than the insert list. The number of SELECT values
must match the number of INSERT columns.
Server: Msg 8180, Level 16, State 1, Line 8
Statement(s) could not be prepared.
The select list matches the insert list exactly.
The source and destination tables are located on two
different (linked) servers.
Both servers are running MSSQL 2000 SP3a.
What am I doing wrong?
Thank you.Without seeing the actual insert statement we can only guess. My guess
would be you have a space in one of the column names.
--
Andrew J. Kelly
SQL Server MVP
"Vlad Soare" <vsoare@.hotmail.com> wrote in message
news:12a5601c4432a$dcaeb0e0$a301280a@.phx.gbl...
> Hello.
> I'm trying to run the following statement:
> insert into [destination table]
> ([fields])
> select [fields] from [source table]
> When I try to run it, I get the following error messages:
> Server: Msg 120, Level 15, State 1, Line 8
> The select list for the INSERT statement contains fewer
> items than the insert list. The number of SELECT values
> must match the number of INSERT columns.
> Server: Msg 8180, Level 16, State 1, Line 8
> Statement(s) could not be prepared.
> The select list matches the insert list exactly.
> The source and destination tables are located on two
> different (linked) servers.
> Both servers are running MSSQL 2000 SP3a.
> What am I doing wrong?
> Thank you.
>|||No, the statement is definitely OK, it works on other
servers, there's only one server it doesn't work on. And
it works if I run it locally, but it doesn't work when I
run it from another server.
Here are the statements:
declare @.IdSpatiu int,
@.IdTran int
set @.IdSpatiu = 15
set @.IdTran = 20
insert into [ts-331].Ploiesti.dbo.Factura
(IdSpatiu, IdTran, Numar)
select @.IdSpatiu, @.IdTran, Numar
from [ts-331].Deva.dbo.Factura
where IdTran = 11 and IdSpatiu = 9
If I replace "select @.IdSpatiu, @.IdTran, Numar"
with "select 15, 20, Numar", it works. It doesn't like
the variables in the select list.
If I'm connected to the server [ts-331], it works. But if
I'm connected to another server (to which ts-331 is
linked), it doesn't work.
It must be something about the ts-331 server. At first I
thought it must be the service pack, because it had no
service pack installed, but then I installed SP3a and the
problem persisted.
Thank you.
>--Original Message--
>Without seeing the actual insert statement we can only
guess. My guess
>would be you have a space in one of the column names.
>--|||It looks fine to me as well. Maybe there is something strange with the way
the Linked server is set up on that machine. Why do you want to do an
insert like that remotely anyway? It would be much cleaner if you had a
stored proc on the linked server that you call and pass in the 2 parameters.
That way the sp does not have to make any linked server calls at all when
actually doing the Insert.
--
Andrew J. Kelly
SQL Server MVP
"Vlad Soare" <vsoare@.hotmail.com> wrote in message
news:1318b01c443b8$d05fa8b0$a401280a@.phx.gbl...
> No, the statement is definitely OK, it works on other
> servers, there's only one server it doesn't work on. And
> it works if I run it locally, but it doesn't work when I
> run it from another server.
> Here are the statements:
> declare @.IdSpatiu int,
> @.IdTran int
> set @.IdSpatiu = 15
> set @.IdTran = 20
> insert into [ts-331].Ploiesti.dbo.Factura
> (IdSpatiu, IdTran, Numar)
> select @.IdSpatiu, @.IdTran, Numar
> from [ts-331].Deva.dbo.Factura
> where IdTran = 11 and IdSpatiu = 9
> If I replace "select @.IdSpatiu, @.IdTran, Numar"
> with "select 15, 20, Numar", it works. It doesn't like
> the variables in the select list.
> If I'm connected to the server [ts-331], it works. But if
> I'm connected to another server (to which ts-331 is
> linked), it doesn't work.
> It must be something about the ts-331 server. At first I
> thought it must be the service pack, because it had no
> service pack installed, but then I installed SP3a and the
> problem persisted.
> Thank you.
> >--Original Message--
> >Without seeing the actual insert statement we can only
> guess. My guess
> >would be you have a space in one of the column names.
> >
> >--
>|||I had the same problem. Try this. I don't know why it works but it
does.
insert into [ts-331].Ploiesti.dbo.Factura
(IdSpatiu, IdTran, Numar)
select (select @.IdSpatiu), (select @.IdTran), Numar
from [ts-331].Deva.dbo.Factura
where IdTran = 11 and IdSpatiu = 9

Error 1105: 'PRIMARY' filegroup is full

I get the following error when attempting to run the
Database Maintenance Plan Optimization job for a database:
Rebuilding indexes for table 'WebLog'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1105:
[Microsoft][ODBC SQL Server Driver][SQL Server]Could not
allocate space for object '(SYSTEM table id: -933813458)'
in database 'svc2000WebLog' because the 'PRIMARY'
filegroup is full.
I am running SQL Server 2000 (SP3) on a Windows 2000 (SP4)
machine. There is plenty of disk space on the server. Do
I need to expand the database before running this job?SQL Server need working space in the db for DBCC DBREINDEX. Also, autogrow
doesn't catch up in some situations. See below. Consider pre-allocating
storage or using DBCC INDEXDEFRAG instead.
http://support.microsoft.com/default.aspx?scid=kb;en-us;305635
--
Tibor Karaszi
"Tom Griffin" <griffin@.co.santa-barbara.ca.us> wrote in message
news:042601c3a23d$5e190a70$a301280a@.phx.gbl...
> I get the following error when attempting to run the
> Database Maintenance Plan Optimization job for a database:
> Rebuilding indexes for table 'WebLog'
> [Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 1105:
> [Microsoft][ODBC SQL Server Driver][SQL Server]Could not
> allocate space for object '(SYSTEM table id: -933813458)'
> in database 'svc2000WebLog' because the 'PRIMARY'
> filegroup is full.
> I am running SQL Server 2000 (SP3) on a Windows 2000 (SP4)
> machine. There is plenty of disk space on the server. Do
> I need to expand the database before running this job?
>

Error 1105 When Using SQLMaint To Reindex Tables

I have a standard reorganise/reindex job running against a 32GB database on SQl Srever 2000. When trying to run the job it fails and returns Error 1105 <'PRIMARY' filegroup is full>. What's confusing me is that I have 53GB free on the drive on which my Primary file group sits.

Has anyone else come accross this problem when trying to set up a regular reindex job?

(more detail) the maintenance plan only includes the reorganisation/reindex job, no other jobs - including backing up the DB - are included. The DB in question is the only DB on the server: it's a test server.Sounds like you've restricted the file growth size...go to the database properties and tell us what it's set to...|||Brett,

You were right, log size was being restricted. Funny how you miss the obvious stuff.....

Many Thanks

Matthew