Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
Author |
Topic |
aki123
Starting Member
20 Posts |
Posted - 2007-08-21 : 04:17:05
|
hion server 2000 sp4 i have crm work on 2005 expresserp on prevasivebackup exec on sql 2000in event viewer i see events 3409 and 8313i expireance slow performance almost every morningtry to restart some services, but most of the timeonly restart to the server help.then the server work normaly.all those issues start after upgrade backupexec from 9 to 9.1then it seems that my application db moved from named instanceto the defualt one. yet the application workes fine.any info will be finethanks |
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-08-21 : 22:34:11
|
They are not sql error. Did you check cpu and memory usage? What kind of server you have? How about server load? |
|
|
aki123
Starting Member
20 Posts |
Posted - 2007-08-22 : 01:50:29
|
hi rmiaoho how come they are no sql error?event id: 3409 source: mssqlserverPerformance counter shared memory setup failed with error -1. Reinstall sqlctr.ini for this instance, and ensure that the instance login account has correct registry permissions. right this morning, i came and saw they cpu work harder then usual.i stop backup exec services and it work as usual.by work harder i mean jumping from 20% to 80% and sometime stock on 100%. usual is 10% to 60% no 100 is showing.its ibm xserver 225 2.5g mega ram os is 2000 sp4yet think its backup exec issue.i can re-install backup exec, but i just wonderbackup exec use sql, those it matter to me, as admin?thanks |
|
|
aki123
Starting Member
20 Posts |
Posted - 2007-08-22 : 02:28:06
|
one thing to mentionedthis event logs every reebot of the server.tahnks |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-08-22 : 15:13:11
|
It's OS can't read .ini file properly, and 3409 will not affect sql performance. High cpu usage is caused by backup exec in your case, check with vendor. |
|
|
|
|
|