How can we help you today? How can we help you today?
KatanaCS

Activity overview

Latest activity by KatanaCS

Here's the output from the file: 2/27/2008 11:00:01 AM : dbadmin:SIMPLE:4259848:4259848:0:0 2/27/2008 11:00:01 AM : distribution:SIMPLE:65544:65544:0:0 2/27/2008 11:00:01 AM : LogShip_Test:BULK_LOGGED:4259844:4259844:0:0 2/27/2008 11:00:01 AM : master:SIMPLE:65544:65544:0:0 2/27/2008 11:00:01 AM : model:SIMPLE:4259848:4259848:0:0 2/27/2008 11:00:01 AM : msdb:SIMPLE:65544:65544:0:0 2/27/2008 11:00:01 AM : tempdb:SIMPLE:8:8:0:0 2/27/2008 11:00:01 AM : ThrivaAdmin:BULK_LOGGED:20:20:0:0 2/27/2008 11:00:01 AM : ThrivaAdminMaster:BULK_LOGGED:4194324:4194324:0:0 2/27/2008 11:00:01 AM : ThrivaCore:BULK_LOGGED:20:20:0:0 2/27/2008 11:00:01 AM : ThrivaCoreMaster:BULK_LOGGED:20:20:0:0 2/27/2008 11:00:01 AM : ThrivaJournal:BULK_LOGGED:65540:65540:0:0 2/27/2008 11:00:01 AM : ThrivaManagement:BULK_LOGGED:20:20:0:0 2/27/2008 11:00:33 AM : dbadmin:SIMPLE:4259848:4259848:0:0 2/27/2008 11:00:33 AM : distribution:SIMPLE:65544:65544:0:0 2/27/2008 11:00:33 AM : LogShip_Test:BULK_LOGGED:4259844:4259844:0:0 2/27/2008 11:00:33 AM : master:SIMPLE:65544:65544:0:0 2/27/2008 11:00:33 AM : model:SIMPLE:4259848:4259848:0:0 2/27/2008 11:00:33 AM : msdb:SIMPLE:65544:65544:0:0 2/27/2008 11:00:33 AM : tempdb:SIMPLE:8:8:0:0 2/27/2008 11:00:33 AM : ThrivaAdmin:BULK_LOGGED:20:20:0:0 2/27/2008 11:00:33 AM : ThrivaAdminMaster:BULK_LOGGED:4194324:4194324:0:0 2/27/2008 11:00:33 AM : ThrivaCore:BULK_LOGGED:20:20:0:0 2/27/2008 11:00:33 AM : ThrivaCoreMaster:BULK_LOGGED:20:20:0:0 2/27/2008 11:00:33 AM : ThrivaJournal:BULK_LOGGED:65540:65540:0:0 2/27/2008 11:00:33 AM : ThrivaManagement:BULK_LOGGED:20:20:0:0 2/27/2008 11:15:01 AM : dbadmin:SIMPLE:4259848:4259848:0:0 2/27/2008 11:15:01 AM : distribution:SIMPLE:65544:65544:0:0 2/27/2008 11:15:01 AM : LogShip_Test:BULK_LOGGED:4259844:4259844:0:0 2/27/2008 11:15:01 AM : master:SIMPLE:65544:65544:0:0 2/27/2008 11:15:01 AM : model:SIMPLE:4259848:4259848:0:0 2/27/2008 11:15:01 AM : msdb:SIMPLE:65544:65544:0:0 2/27/2008 11:15:01 AM : tempdb:SIMPLE:8:8:0:0 2/27/2008 11:15:01 AM : ThrivaAdmin:BULK_LOGGED:20:20:0:0 2/27/2008 11:15:01 AM : ThrivaAdminMaster:BULK_LOGGED:4194324:4194324:0:0 2/27/2008 11:15:01 AM : ThrivaCore:BULK_LOGGED:20:20:0:0 2/27/2008 11:15:01 AM : ThrivaCoreMaster:BULK_LOGGED:20:20:0:0 2/27/2008 11:15:01 AM : ThrivaJournal:BULK_LOGGED:65540:65540:0:0 2/27/2008 11:15:01 AM : ThrivaManagement:BULK_LOGGED:20:20:0:0 2/27/2008 11:30:01 AM : dbadmin::4259848:-1:0: 2/27/2008 11:30:01 AM : distribution::65544:-1:0: 2/27/2008 11:30:01 AM : LogShip_Test:BULK_LOGGED:4259844:4259844:0:0 2/27/2008 11:30:01 AM : master:SIMPLE:65544:65544:0:0 2/27/2008 11:30:01 AM : model:SIMPLE:4259848:4259848:0:0 2/27/2008 11:30:01 AM : msdb:SIMPLE:65544:65544:0:0 2/27/2008 11:30:01 AM : tempdb:SIMPLE:8:8:0:0 2/27/2008 11:30:01 AM : ThrivaAdmin::20:-1:0: 2/27/2008 11:30:01 AM : ThrivaAdminMaster::4194324:-1:0: 2/27/2008 11:30:01 AM : ThrivaCore:BULK_LOGGED:20:20:0:0 2/27/2008 11:30:01 AM : ThrivaCoreMaster::20:-1:0: 2/27/2008 11:30:01 AM : ThrivaJournal::65540:-1:0: 2/27/2008 11:30:01 AM : ThrivaManagement::20:-1:0: / comments
Here's the output from the file: 2/27/2008 11:00:01 AM : dbadmin:SIMPLE:4259848:4259848:0:0 2/27/2008 11:00:01 AM : distribution:SIMPLE:65544:65544:0:0 2/27/2008 11:00:01 AM : LogShip_Test:BULK_LOG...
0 votes
Sure. The first database in the list alphabetically is [ABI], and I changed the database in the list to be [active2_repl]. The SQL login I used is "DBA". Of course, since there's no SQL instance installed with the name of the local node (the error being thrown), I can't run a trace on it to see where CA is trying to connect to that instance. Here's a capture of the profiler output (pipe-delimited): Event|TextData|login|spid Audit Login||DBA|150 SQL:BatchStarting|"SELECT OBJECT_ID('sqbtest') sqbtest, OBJECT_ID('sqbteststatus') sqbteststatus, OBJECT_ID('sqbtestcancel') sqbtestcancel"|DBA|150 SQL:StatementStarting|"SELECT OBJECT_ID('sqbtest') sqbtest, OBJECT_ID('sqbteststatus') sqbteststatus, OBJECT_ID('sqbtestcancel') sqbtestcancel"|DBA|150 SQL:StatementCompleted|"SELECT OBJECT_ID('sqbtest') sqbtest, OBJECT_ID('sqbteststatus') sqbteststatus, OBJECT_ID('sqbtestcancel') sqbtestcancel"|DBA|150 SQL:BatchCompleted|"SELECT OBJECT_ID('sqbtest') sqbtest, OBJECT_ID('sqbteststatus') sqbteststatus, OBJECT_ID('sqbtestcancel') sqbtestcancel"|DBA|150 RPC:Starting|exec sp_reset_connection|DBA|150 Audit Logout||DBA|150 RPC:Completed|exec sp_reset_connection|DBA|150 Audit Login||DBA|150 SQL:BatchStarting|SELECT name FROM master..sysdatabases WHERE status & 1568 = 0 ORDER BY name|DBA|150 SQL:StatementStarting|SELECT name FROM master..sysdatabases WHERE status & 1568 = 0 ORDER BY name|DBA|150 SQL:StatementCompleted|SELECT name FROM master..sysdatabases WHERE status & 1568 = 0 ORDER BY name|DBA|150 SQL:BatchCompleted|SELECT name FROM master..sysdatabases WHERE status & 1568 = 0 ORDER BY name|DBA|150 RPC:Starting|exec sp_reset_connection|DBA|150 Audit Logout||DBA|150 RPC:Completed|exec sp_reset_connection|DBA|150 Audit Login||DBA|150 SQL:BatchStarting|USE [ABI] SELECT SUM(CAST(size AS BIGINT) * 8192) size FROM sysfiles|DBA|150 SQL:StatementStarting|USE [ABI] |DBA|150 SQL:StatementCompleted|USE [ABI] |DBA|150 SQL:StatementStarting|SELECT SUM(CAST(size AS BIGINT) * 8192) size FROM sysfiles|DBA|150 SQL:StatementCompleted|SELECT SUM(CAST(size AS BIGINT) * 8192) size FROM sysfiles|DBA|150 SQL:BatchCompleted|USE [ABI] SELECT SUM(CAST(size AS BIGINT) * 8192) size FROM sysfiles|DBA|150 RPC:Starting|exec sp_reset_connection|DBA|150 Audit Logout||DBA|150 RPC:Completed|exec sp_reset_connection|DBA|150 Audit Login||DBA|150 SQL:BatchStarting|USE [active2_repl] SELECT SUM(CAST(size AS BIGINT) * 8192) size FROM sysfiles|DBA|150 SQL:StatementStarting|USE [active2_repl]|DBA|150 SQL:StatementCompleted|USE [active2_repl]|DBA|150 SQL:StatementStarting|SELECT SUM(CAST(size AS BIGINT) * 8192) size FROM sysfiles|DBA|150 SQL:StatementCompleted|SELECT SUM(CAST(size AS BIGINT) * 8192) size FROM sysfiles|DBA|150 SQL:BatchCompleted|USE [active2_repl] SELECT SUM(CAST(size AS BIGINT) * 8192) size FROM sysfiles|DBA|150 RPC:Starting|exec sp_reset_connection|DBA|150 Audit Logout||DBA|150 RPC:Completed|exec sp_reset_connection|DBA|150 Audit Login||DBA|150 SQL:BatchStarting|master..sqbtest N'active2_repl'|DBA|150 SQL:StatementStarting|master..sqbtest N'active2_repl'|DBA|150 Audit Login||DBA|153 SQL:BatchStarting|master..sqbteststatus|DBA|153 SQL:StatementStarting|master..sqbteststatus|DBA|153 SQL:StatementCompleted|master..sqbteststatus|DBA|153 SQL:BatchCompleted|master..sqbteststatus|DBA|153 | The above 4 lines are repeated 19 times | |153 SQL:StatementCompleted|master..sqbtest N'active2_repl'|DBA|150 SQL:BatchCompleted|master..sqbtest N'active2_repl'|DBA|150 this is where the error dialog pops up once the app is closed, the next two lines show up Audit Logout||DBA|150 Audit Logout||DBA|153 I also included errors in the trace, and only the warnings of changing database context and language setting were reported. Thanks! / comments
Sure. The first database in the list alphabetically is [ABI], and I changed the database in the list to be [active2_repl]. The SQL login I used is "DBA". Of course, since there's no SQL instance...
0 votes
Ok, I've put this into place. It's no trouble, it's obviously some odd hidden bug, such as "if it's Tuesday and it's raining, do something obscure ...". I'm just glad you guys are so responsive! 8) / comments
Ok, I've put this into place. It's no trouble, it's obviously some odd hidden bug, such as "if it's Tuesday and it's raining, do something obscure ...". I'm just glad you guys are so responsive!...
0 votes
Compression Analyzer - Authentication Bug
Hi, I'm not 100% sure if this post should be here or somewhere else, but I couldn't find a defined group for Compression Analyzer. I just tried to use the Compression Analyzer to estimate a databas...
2 followers 4 comments 0 votes
Just got an error, and here are the last two sessions worth of data from the log file: 2/21/2008 10:45:01 AM : dbadmin:SIMPLE:0:0 2/21/2008 10:45:01 AM : distribution:SIMPLE:0:0 2/21/2008 10:45:01 AM : LogShip_Test:BULK_LOGGED:0:0 2/21/2008 10:45:01 AM : master:SIMPLE:0:0 2/21/2008 10:45:01 AM : model:SIMPLE:0:0 2/21/2008 10:45:01 AM : msdb:SIMPLE:0:0 2/21/2008 10:45:01 AM : tempdb:SIMPLE:0:0 2/21/2008 10:45:01 AM : ThrivaAdmin:BULK_LOGGED:0:0 2/21/2008 10:45:01 AM : ThrivaAdminMaster:BULK_LOGGED:0:0 2/21/2008 10:45:01 AM : ThrivaCore:BULK_LOGGED:0:0 2/21/2008 10:45:01 AM : ThrivaCoreMaster:BULK_LOGGED:0:0 2/21/2008 10:45:01 AM : ThrivaJournal:BULK_LOGGED:0:0 2/21/2008 10:45:01 AM : ThrivaManagement:BULK_LOGGED:0:0 2/21/2008 11:00:01 AM : dbadmin::0: 2/21/2008 11:00:01 AM : distribution::0: 2/21/2008 11:00:01 AM : LogShip_Test:BULK_LOGGED:0:0 2/21/2008 11:00:01 AM : master:SIMPLE:0:0 2/21/2008 11:00:01 AM : model:SIMPLE:0:0 2/21/2008 11:00:01 AM : msdb:SIMPLE:0:0 2/21/2008 11:00:01 AM : tempdb:SIMPLE:0:0 2/21/2008 11:00:01 AM : ThrivaAdmin::0: 2/21/2008 11:00:01 AM : ThrivaAdminMaster::0: 2/21/2008 11:00:01 AM : ThrivaCore:BULK_LOGGED:0:0 2/21/2008 11:00:01 AM : ThrivaCoreMaster::0: 2/21/2008 11:00:01 AM : ThrivaJournal::0: 2/21/2008 11:00:01 AM : ThrivaManagement::0: It would seem the recovery model value wasn't captured on the run with the error. / comments
Just got an error, and here are the last two sessions worth of data from the log file: 2/21/2008 10:45:01 AM : dbadmin:SIMPLE:0:0 2/21/2008 10:45:01 AM : distribution:SIMPLE:0:0 2/21/2008 10:45:01 ...
0 votes