Foreign characters in email

Hi,

My applications sends email using the smtp service.

When the service sends the mail, the content has some foreign characters in it.

These generally occur when I give forward the mail to someone or when the content has a fullstop.

I have given the subscriber's locale as en-us.

Below given is the first instance which i am facing.

Note: This is an auto-generated mail..Do not reply to this mail..

Above you can see, there are two dots instead of one.

Another instance is when I forward the mail:

?噉?扮灳??噉?剂???慬杮攽?獵挠慬獳伽瑵潬歯敍獳条?慥敤?污杩?氢晥??剉∽呌≒￣??慴楢摮硥∽???但呎?捡?吢?楓敺∽?￣????匠???????￣?剂￣?吾??圠????匾??匠?????乏???????噉??噉Hi,

These are the characters i had mentioned above.

Are you setting the BodyEncoding element in the DeliveryChannel of the ICF? Something like:

<Argument>
<Name>BodyEncoding</Name>
<Value>utf-16</Value>
</Argument>

HTH...

Joe

|||yes it is utf-16

Regards,
navbhan|||Generally speaking, I've seen a number of programs that do not natively support UTF-16. Try UTF-8 and see what happens. If your application requires UTF-16, that may not be a long term solutions, but at least it may help to clarify the issues a bit.

HTH...

Joe

Foreign characters in email

Hi,

My applications sends email using the smtp service.

When the service sends the mail, the content has some foreign characters in it.

These generally occur when I give forward the mail to someone or when the content has a fullstop.

I have given the subscriber's locale as en-us.

Below given is the first instance which i am facing.

Note: This is an auto-generated mail..Do not reply to this mail..

Above you can see, there are two dots instead of one.

Another instance is when I forward the mail:

?噉?扮灳??噉?剂???慬杮攽?獵挠慬獳伽瑵潬歯敍獳条?慥敤?污杩?氢晥??剉∽呌≒￣??慴楢摮硥∽???但呎?捡?吢?楓敺∽?￣????匠???????￣?剂￣?吾??圠????匾??匠?????乏???????噉??噉Hi,

These are the characters i had mentioned above.

Are you setting the BodyEncoding element in the DeliveryChannel of the ICF? Something like:

<Argument>
<Name>BodyEncoding</Name>
<Value>utf-16</Value>
</Argument>

HTH...

Joe

|||yes it is utf-16

Regards,
navbhan|||Generally speaking, I've seen a number of programs that do not natively support UTF-16. Try UTF-8 and see what happens. If your application requires UTF-16, that may not be a long term solutions, but at least it may help to clarify the issues a bit.

HTH...

Joe

Force Protocol Encryption Enabled & SQL Server Cannot Start

I'm running SQL 2000 Server with Windows service account with a normal user
privileges.
However, whenever I turn on Force Protocol Encryption (the cert is already
installed), the server does not start.
I suspect that it's to do with the service account which does not have
rights to the cert. How do I grant the service account with sufficient
privilege to read the cert so that Force Protocol Encryption can be enabled?
Thanks.How SQL Server uses a certificate when the Force Protocol Encryption option
is set on http://support.microsoft.com/default.aspx?scid=kb;en-us;318605
How SQL Server verifies that a certificate is valid
â?¢ The certificate's Enhanced Key Usage property has to be turned on for
Server Authentication. To verify that the certificate is used for server
authentication, use the Microsoft Management Console (MMC) Certificate
snap-in. Double-click the certificate name, and then select Details. Click
the Enhanced Key Usage property, and then verify that the value is: Server
Authentication(1.3.6.1.5.5.7.3.1).
â?¢ Make sure that the certificate name is the same as the SQL Server FQDN or
the value configured in the registry (as described earlier).
â?¢ You must install the certificate to the Certificates\Current User Personal
Certificates folder while you are logged on as the SQL Server startup
account. This will make sure that the certificate will be put in the Personal
Certificates folder of the SQL Server startup account. If you have logged on
with a user account that is different from the SQL Server startup account,
put the certificate in the Certificates\Local Computer Personal Certificates
folder. This action solves the problem of having certificates stored under
the wrong user account.
To view the Current User folder, follow these steps:1. Logon as the SQL
Server startup account.
2. Use the MMC Certificates snap-in to verify the location of the
certificate.
FIX: Cannot Use Non-Administrator Account to Start SQL Server and Force
Encryption http://support.microsoft.com/default.aspx?scid=kb;en-us;314636
"James" wrote:
> I'm running SQL 2000 Server with Windows service account with a normal user
> privileges.
> However, whenever I turn on Force Protocol Encryption (the cert is already
> installed), the server does not start.
> I suspect that it's to do with the service account which does not have
> rights to the cert. How do I grant the service account with sufficient
> privilege to read the cert so that Force Protocol Encryption can be enabled?
> Thanks.

Force Protocol Encryption Enabled & SQL Server Cannot Start

I'm running SQL 2000 Server with Windows service account with a normal user
privileges.
However, whenever I turn on Force Protocol Encryption (the cert is already
installed), the server does not start.
I suspect that it's to do with the service account which does not have
rights to the cert. How do I grant the service account with sufficient
privilege to read the cert so that Force Protocol Encryption can be enabled?
Thanks.
How SQL Server uses a certificate when the Force Protocol Encryption option
is set on http://support.microsoft.com/default...b;en-us;318605
How SQL Server verifies that a certificate is valid
? The certificate's Enhanced Key Usage property has to be turned on for
Server Authentication. To verify that the certificate is used for server
authentication, use the Microsoft Management Console (MMC) Certificate
snap-in. Double-click the certificate name, and then select Details. Click
the Enhanced Key Usage property, and then verify that the value is: Server
Authentication(1.3.6.1.5.5.7.3.1).
? Make sure that the certificate name is the same as the SQL Server FQDN or
the value configured in the registry (as described earlier).
? You must install the certificate to the Certificates\Current User Personal
Certificates folder while you are logged on as the SQL Server startup
account. This will make sure that the certificate will be put in the Personal
Certificates folder of the SQL Server startup account. If you have logged on
with a user account that is different from the SQL Server startup account,
put the certificate in the Certificates\Local Computer Personal Certificates
folder. This action solves the problem of having certificates stored under
the wrong user account.
To view the Current User folder, follow these steps:1. Logon as the SQL
Server startup account.
2. Use the MMC Certificates snap-in to verify the location of the
certificate.
FIX: Cannot Use Non-Administrator Account to Start SQL Server and Force
Encryption http://support.microsoft.com/default...b;en-us;314636
"James" wrote:

> I'm running SQL 2000 Server with Windows service account with a normal user
> privileges.
> However, whenever I turn on Force Protocol Encryption (the cert is already
> installed), the server does not start.
> I suspect that it's to do with the service account which does not have
> rights to the cert. How do I grant the service account with sufficient
> privilege to read the cert so that Force Protocol Encryption can be enabled?
> Thanks.

Force Protocol Encryption Enabled & SQL Server Cannot Start

I'm running SQL 2000 Server with Windows service account with a normal user
privileges.
However, whenever I turn on Force Protocol Encryption (the cert is already
installed), the server does not start.
I suspect that it's to do with the service account which does not have
rights to the cert. How do I grant the service account with sufficient
privilege to read the cert so that Force Protocol Encryption can be enabled?
Thanks.How SQL Server uses a certificate when the Force Protocol Encryption option
is set on http://support.microsoft.com/defaul...kb;en-us;318605
How SQL Server verifies that a certificate is valid
? The certificate's Enhanced Key Usage property has to be turned on for
Server Authentication. To verify that the certificate is used for server
authentication, use the Microsoft Management Console (MMC) Certificate
snap-in. Double-click the certificate name, and then select Details. Click
the Enhanced Key Usage property, and then verify that the value is: Serve
r
Authentication(1.3.6.1.5.5.7.3.1).
? Make sure that the certificate name is the same as the SQL Server FQDN o
r
the value configured in the registry (as described earlier).
? You must install the certificate to the Certificates\Current User Person
al
Certificates folder while you are logged on as the SQL Server startup
account. This will make sure that the certificate will be put in the Persona
l
Certificates folder of the SQL Server startup account. If you have logged on
with a user account that is different from the SQL Server startup account,
put the certificate in the Certificates\Local Computer Personal Certificates
folder. This action solves the problem of having certificates stored under
the wrong user account.
To view the Current User folder, follow these steps:1. Logon as the SQL
Server startup account.
2. Use the MMC Certificates snap-in to verify the location of the
certificate.
FIX: Cannot Use Non-Administrator Account to Start SQL Server and Force
Encryption http://support.microsoft.com/defaul...kb;en-us;314636
"James" wrote:

> I'm running SQL 2000 Server with Windows service account with a normal use
r
> privileges.
> However, whenever I turn on Force Protocol Encryption (the cert is already
> installed), the server does not start.
> I suspect that it's to do with the service account which does not have
> rights to the cert. How do I grant the service account with sufficient
> privilege to read the cert so that Force Protocol Encryption can be enable
d?
> Thanks.

For security reasons DTD is prohibited in this XML document.

When we develop with the Microsoft SQL Server 2005 Reporting Service.
We got the exception on some reports.

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on
XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Ther report renders well first time, but if we click the title to sort the report, it will throw the exception.

And It occurred that we use IE6 and IE7 to view the report at same time, but if we use the same version brower, there are no exception.
Can somebody help me?

My development’s environment :
Windows XP English Professional + SP2
Microsoft SQL Server 2005 Development version + SP 1 + SP 2
Microsoft Visual Studio 2005 Professional Version 8.0.50727.51 (QFE.050727-5100) + SP1
Microsoft .NET Framework Version 2.0.50727

Hi Kevin,

We found an issue like this in a recent version of pre-release SQL 2005 Reporting Services SP2. If you are running versions of Reporting Services prior to SP2, please let me know. Otherwise, this will be fixed in the the final release of SP2.

|||

I'm seeing this occur in both SP1, and the CTP release of SP2.

Please advise. Reports render some of the time, but the vast majority I revceive the same error.

|||

We just installed SP2 in our organization. I am running a very large dataset which brings out about 4 million rows. When I run this report I am getting this error.

For security reasons DTD is prohibited in this XML document......

Please help...

For security reasons DTD is prohibited in this XML document.

When we develop with the Microsoft SQL Server 2005 Reporting Service.
We got the exception on some reports.

For security reasons DTD is prohibited in this XML document. To enable DTD processing set the ProhibitDtd property on
XmlReaderSettings to false and pass the settings into XmlReader.Create method.

Ther report renders well first time, but if we click the title to sort the report, it will throw the exception.

And It occurred that we use IE6 and IE7 to view the report at same time, but if we use the same version brower, there are no exception.
Can somebody help me?

My development’s environment :
Windows XP English Professional + SP2
Microsoft SQL Server 2005 Development version + SP 1 + SP 2
Microsoft Visual Studio 2005 Professional Version 8.0.50727.51 (QFE.050727-5100) + SP1
Microsoft .NET Framework Version 2.0.50727

Hi Kevin,

We found an issue like this in a recent version of pre-release SQL 2005 Reporting Services SP2. If you are running versions of Reporting Services prior to SP2, please let me know. Otherwise, this will be fixed in the the final release of SP2.

|||

I'm seeing this occur in both SP1, and the CTP release of SP2.

Please advise. Reports render some of the time, but the vast majority I revceive the same error.

|||

We just installed SP2 in our organization. I am running a very large dataset which brings out about 4 million rows. When I run this report I am getting this error.

For security reasons DTD is prohibited in this XML document......

Please help...