Difference between revisions of "Talk:Invalid Binary Header on Replication"
From EHS Help
(→Compare configuration of live and test servers: new section) |
(→Provide additional debug coding to help narrow down the problem area: new section) |
||
| Line 7: | Line 7: | ||
**Minimum requirement is 2005 | **Minimum requirement is 2005 | ||
*Compare database schemas for table ILOG_REPL between live and test servers | *Compare database schemas for table ILOG_REPL between live and test servers | ||
| + | |||
| + | == Provide additional debug coding to help narrow down the problem area == | ||
| + | |||
| + | *Attempt to open another datatable (any) to establish channel comms are working okay | ||
| + | **Write some output to console window for confirmation | ||
| + | *Attempt to open another datatable from a different service to isolate problems with specific service implementations | ||
| + | **write datatable output to console for confirmation | ||
| + | *Call method on server to isolate specific problems with datastreamer | ||
| + | **output results to console. | ||
Latest revision as of 14:49, 13 October 2012
Discuss potential solutions and methods of narrowing down the problem. Evidence is contradictory at the moment & we need a clearer picture.
Compare configuration of live and test servers
- Compare IIS versions on live and test servers
- Compare SQL Server versions on live and test servers
- Minimum requirement is 2005
- Compare database schemas for table ILOG_REPL between live and test servers
Provide additional debug coding to help narrow down the problem area
- Attempt to open another datatable (any) to establish channel comms are working okay
- Write some output to console window for confirmation
- Attempt to open another datatable from a different service to isolate problems with specific service implementations
- write datatable output to console for confirmation
- Call method on server to isolate specific problems with datastreamer
- output results to console.
