|
|
 Cluster
DOS
IBM - AS400
MOM
Performance Counters
Service Broker
 SQL Server
Temporary Database
Views
Backup
SQL Mail
DTS - Data Transformation Services
Memory
Security
Excel
Jobs SQL Agent
MSDE
Install
DBCC
User Management
System Databases
BCV
Deadlocks
Temp Tables
 Find the physical se...
Enable xp_cmdshell
Intermittent Connect...
Connection String Pr...
Login Error ( State)...
Turn Default Tracing...
Re-index fails when ...
SMO AND DMO
Tracing of Errors
Extra carriage Retur...
Query to find Object...
Named Instance Port ...
Adding Domain Login ...
Rename Logical File ...
Error 3624 Delete st...
SQL DMO Error 21776
NetworkConnections
SQL Server Service m...
Trace Flags for Dead...
Change Server Name
Alternate to Count(*...
Windows OS
Will be added as a sub-category of, SQL Server
|
|
Extra carriage Return
|
|
Char(13) + char(10) just worked like a charm …
Thank you.
--------------------------------------------------------------------------------
From: Horkay, Robert
Sent: Tuesday, September 26, 2006 4:13 PM
To: Gupta, Vishal
Subject: RE: NON LEAP FPC Status on Sep 26 2006 1:00PM
Vishal,
You can make a code adjustment to avoid this, below is the actual root cause and the solution, it’s a bit verbose.
XPSMTP uses a maximum line length of 1000 characters, minus two for storing a carriage return linefeed (\r\n) to terminate the line. When you are sending a message which contains a line or lines that are longer then the maximum line length, XPSMTP automatically inserts a carriage return linefeed (\r\n) before it sends the line to the SMTP server. If you have embedded carriage return linefeeds inside your message which occur before the maximum line length of 1000 characters, the string is terminate at that point and send to the server, in which case no extra carriage return linefeed is added. The problem occurs when you are using only using line feeds (\n) without the carriage return (\r) inside your message. So the workaround is to use carriage return linefeeds (\r\n) instead of linefeeds (\n). In T-SQL a carriage return linefeed can be represented using char(13) + char(10). In a future release XPSMTP will automatically be able to use both \n as a \r\n to terminate lines before exceeding the maximum line length of a 1000 characters.
Bob
--------------------------------------------------------------------------------
From: Gupta, Vishal
Sent: Tuesday, September 26, 2006 3:33 PM
To: Horkay, Robert
Subject: RE: NON LEAP FPC Status on Sep 26 2006 1:00PM
No hurry … whenever you find some time
--------------------------------------------------------------------------------
From: Horkay, Robert
Sent: Tuesday, September 26, 2006 3:24 PM
To: Gupta, Vishal
Subject: RE: NON LEAP FPC Status on Sep 26 2006 1:00PM
Vishal,
I remember something on this, very similar a long time ago, I’ll need some time to research and refresh my memory….
Bob
--------------------------------------------------------------------------------
From: Gupta, Vishal
Sent: Tuesday, September 26, 2006 1:16 PM
To: Horkay, Robert
Subject: FW: NON LEAP FPC Status on Sep 26 2006 1:00PM
We get these alert emails from TIB48 on an hourly basis. Would you know why it would add a ‘return’ character in the line in red? We are getting some other emails also and we see the same in those also. It seems like for every 1024 chrs it is putting in an extra ‘return’ character. I was just curious to know why it would happen, and if you know the reason for that.
Thanks,
Vishal
-----Original Message-----
From: NONLEAP_FPC [mailto:SQLADM@hrblock.com]
Sent: Tuesday, September 26, 2006 1:01 PM
To: Gupta, Vishal; Nachimuthu, Balamani; Glen, George; Seema, Dilip; Venugopal, Pramod; Mehta, Sangeet; Branstetter, Christopher
Subject: NON LEAP FPC Status on Sep 26 2006 1:00PM
NON LEAP FPC Status on Sep 26 2006 1:00PM showing when the last file was received today and minutes since last received.
AST (AM INBOUND) : Files Processed Today: 901 Last Processed at: 12:59 (1 mins)
PC (AM OUTBOUND) : Files Processed Today: 10530 Last Processed at: 12:59 (1 mins)
CCF (OIB CCF) : Files Processed Today: 77 Last Processed at: 13:00 (0 mins)
CPN (COUPON INBOUND) : Files Processed Today: 3472 Last Processed at: 12:59 (1 mins)
PCCP_IN (PCCP INBOUND) : Files Processed Today: 35 Last Processed at: 12:56 (4 mins)
PCCP_OUT (PCCP OUTBOUND) : Files Processed Today: 33 Last Processed at: 12:59 (1 mins)
POS (POS) : Files Processed Today: 36 Last Processed at: 12:59 (1 mins)
SET (POS SETTLEMENT) : Files Processed Today: 3 Last Processed at: 09:53 (187 mins) *** ALERT ***
PERU (FILE SERVER) : Files Pr
ocessed Today: 1436 Last Processed at: 12:59 (1 mins)
BOLIVIA (FILE SERVER) : Files Processed Today: 1507 Last Processed at: 12:59 (1 mins)
SWEDEN (FILE SERVER) : Files Processed Today: 1504 Last Processed at: 12:59 (1 mins)
PHRX (POS HEALTH REPORT) : *** No Files Processed Today ***
EFILE (EFILE NOTIFICATION) : *** No Files Processed Today ***
BO (BAILOUT) : *** No Files Processed Today ***
PRICE (PRICING INBOUND) : *** No Files Processed Today ***
IMAL (IMAL) : *** No Files Processed Today ***
CIMS (CIMS) : *** No Files Processed Today ***
SPBILL (SETTLEMENT PRICING) : *** No Files Processed Today ***
*****Service from SQL Server: NONLEAP_FPC:WHQEAITIB48******
|
|
|
|
|