Korean wording appear as ? in PDF

Can anyone help me ?
My question is :
My report contains some Korean wording. When I export to PDF, the Korean
word appear as ?. Then I export the report in Excel format, there is no
problem in the Korean wording. But when I try to print it, the default page
orientation is 'Landscape' and there is default left and right margin no
matter how I adjust the report size in reporting services.Make sure the font you're using exists on both the server and the client
viewing the PDF.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"May Liu" <MayLiu@.discussions.microsoft.com> wrote in message
news:17D5F204-6D94-4ECA-93A1-E287442C8C5D@.microsoft.com...
> Can anyone help me ?
> My question is :
> My report contains some Korean wording. When I export to PDF, the Korean
> word appear as ?. Then I export the report in Excel format, there is no
> problem in the Korean wording. But when I try to print it, the default
> page
> orientation is 'Landscape' and there is default left and right margin no
> matter how I adjust the report size in reporting services.
>

Kill Process

Hello again,
I have one process that appear runing (OMNIBACK), i've yet
kill the process (The command(s) completed
successfully)... but the process still running.
Can i do a SUPERKILL ;o)
i dont know what to do.
Best Regards> I have one process that appear runing (OMNIBACK), i've yet
> kill the process (The command(s) completed
> successfully)... but the process still running.
> Can i do a SUPERKILL ;o)
They are likely in the middle of a rollback. If you say KILL <spid> again
you should be able to see what percentage of rollback has completed.
To be safe, I would just let the process finish what it's doing to clean
itself up. Many people are tempted to just power down the box or force the
SQL Server service to restart, but I promise you this isn't the way to go...
can lead to suspect database, or a database that has to start the same
recovery/rollback process all over again before you will be able to use it.
While you're waiting, I would find out what they did, why you had to kill
the user, and take steps to prevent this from happening again.
--
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||KILL is limited in its power.
The closest thing to SUPERKILL is the hefty: ALTER DATABASE mydb SET
SINGLE_USER. Then you can make it multi-user again. This will chase
_everybody_ (not one user) out of a database.
Russell Fields
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:ec0601c43cfd$7e94f420$a301280a@.phx.gbl...
> Hello again,
> I have one process that appear runing (OMNIBACK), i've yet
> kill the process (The command(s) completed
> successfully)... but the process still running.
> Can i do a SUPERKILL ;o)
> i dont know what to do.
> Best Regards
>|||you can add the status_only clause to Kill.
One question - if it's rolled back 100% but still not ending, is it running something outside of SQL? I.e. something like sp_OaCreate to run a COM component or xp_cmdshell or xp_sendmail?
If that's the case then SQL can lose sight of whether the process is active or not - normally because the dll (or whatever) hasn't reported status back.
Alici
http://www.sqlporn.co.uk|||Maybe it's executing a WSH script, and the server is waiting for someone to
walk by and click "OK" on a MsgBox. :-)
"Alicia" <anonymous@.discussions.microsoft.com> wrote in message
news:ABA285E4-A89A-45BE-BBB0-B2A6DCCEC86F@.microsoft.com...
> you can add the status_only clause to Kill.
> One question - if it's rolled back 100% but still not ending, is it
running something outside of SQL? I.e. something like sp_OaCreate to run a
COM component or xp_cmdshell or xp_sendmail?
> If that's the case then SQL can lose sight of whether the process is
active or not - normally because the dll (or whatever) hasn't reported
status back.
> Alicia
> http://www.sqlporn.co.uk|||Yeah - I've seen that in a job running DTS ActiveX script with debug code in
it...
xp_cmdshell 'notepad' will do it as well :-)
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:OS8lU6QPEHA.2636@.TK2MSFTNGP10.phx.gbl...
> Maybe it's executing a WSH script, and the server is waiting for someone
to
> walk by and click "OK" on a MsgBox. :-)
>
>
> "Alicia" <anonymous@.discussions.microsoft.com> wrote in message
> news:ABA285E4-A89A-45BE-BBB0-B2A6DCCEC86F@.microsoft.com...
> > you can add the status_only clause to Kill.
> > One question - if it's rolled back 100% but still not ending, is it
> running something outside of SQL? I.e. something like sp_OaCreate to run a
> COM component or xp_cmdshell or xp_sendmail?
> > If that's the case then SQL can lose sight of whether the process is
> active or not - normally because the dll (or whatever) hasn't reported
> status back.
> >
> > Alicia
> >
> > http://www.sqlporn.co.uk
>sql

Kill Process

Hello again,
I have one process that appear runing (OMNIBACK), i've yet
kill the process (The command(s) completed
successfully)... but the process still running.
Can i do a SUPERKILL ;o)
i dont know what to do.
Best Regards
> I have one process that appear runing (OMNIBACK), i've yet
> kill the process (The command(s) completed
> successfully)... but the process still running.
> Can i do a SUPERKILL ;o)
They are likely in the middle of a rollback. If you say KILL <spid> again
you should be able to see what percentage of rollback has completed.
To be safe, I would just let the process finish what it's doing to clean
itself up. Many people are tempted to just power down the box or force the
SQL Server service to restart, but I promise you this isn't the way to go...
can lead to suspect database, or a database that has to start the same
recovery/rollback process all over again before you will be able to use it.
While you're waiting, I would find out what they did, why you had to kill
the user, and take steps to prevent this from happening again.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||KILL is limited in its power.
The closest thing to SUPERKILL is the hefty: ALTER DATABASE mydb SET
SINGLE_USER. Then you can make it multi-user again. This will chase
_everybody_ (not one user) out of a database.
Russell Fields
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:ec0601c43cfd$7e94f420$a301280a@.phx.gbl...
> Hello again,
> I have one process that appear runing (OMNIBACK), i've yet
> kill the process (The command(s) completed
> successfully)... but the process still running.
> Can i do a SUPERKILL ;o)
> i dont know what to do.
> Best Regards
>
|||you can add the status_only clause to Kill.
One question - if it's rolled back 100% but still not ending, is it running something outside of SQL? I.e. something like sp_OaCreate to run a COM component or xp_cmdshell or xp_sendmail?
If that's the case then SQL can lose sight of whether the process is active or not - normally because the dll (or whatever) hasn't reported status back.
Alicia
http://www.sqlporn.co.uk
|||Maybe it's executing a WSH script, and the server is waiting for someone to
walk by and click "OK" on a MsgBox. :-)
"Alicia" <anonymous@.discussions.microsoft.com> wrote in message
news:ABA285E4-A89A-45BE-BBB0-B2A6DCCEC86F@.microsoft.com...
> you can add the status_only clause to Kill.
> One question - if it's rolled back 100% but still not ending, is it
running something outside of SQL? I.e. something like sp_OaCreate to run a
COM component or xp_cmdshell or xp_sendmail?
> If that's the case then SQL can lose sight of whether the process is
active or not - normally because the dll (or whatever) hasn't reported
status back.
> Alicia
> http://www.sqlporn.co.uk
|||Yeah - I've seen that in a job running DTS ActiveX script with debug code in
it...
xp_cmdshell 'notepad' will do it as well :-)
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:OS8lU6QPEHA.2636@.TK2MSFTNGP10.phx.gbl...
> Maybe it's executing a WSH script, and the server is waiting for someone
to
> walk by and click "OK" on a MsgBox. :-)
>
>
> "Alicia" <anonymous@.discussions.microsoft.com> wrote in message
> news:ABA285E4-A89A-45BE-BBB0-B2A6DCCEC86F@.microsoft.com...
> running something outside of SQL? I.e. something like sp_OaCreate to run a
> COM component or xp_cmdshell or xp_sendmail?
> active or not - normally because the dll (or whatever) hasn't reported
> status back.
>

Kill Process

Hello again,
I have one process that appear runing (OMNIBACK), i've yet
kill the process (The command(s) completed
successfully)... but the process still running.
Can i do a SUPERKILL ;o)
i dont know what to do.
Best Regards> I have one process that appear runing (OMNIBACK), i've yet
> kill the process (The command(s) completed
> successfully)... but the process still running.
> Can i do a SUPERKILL ;o)
They are likely in the middle of a rollback. If you say KILL <spid> again
you should be able to see what percentage of rollback has completed.
To be safe, I would just let the process finish what it's doing to clean
itself up. Many people are tempted to just power down the box or force the
SQL Server service to restart, but I promise you this isn't the way to go...
can lead to suspect database, or a database that has to start the same
recovery/rollback process all over again before you will be able to use it.
While you're waiting, I would find out what they did, why you had to kill
the user, and take steps to prevent this from happening again.
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/|||KILL is limited in its power.
The closest thing to SUPERKILL is the hefty: ALTER DATABASE mydb SET
SINGLE_USER. Then you can make it multi-user again. This will chase
_everybody_ (not one user) out of a database.
Russell Fields
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:ec0601c43cfd$7e94f420$a301280a@.phx.gbl...
> Hello again,
> I have one process that appear runing (OMNIBACK), i've yet
> kill the process (The command(s) completed
> successfully)... but the process still running.
> Can i do a SUPERKILL ;o)
> i dont know what to do.
> Best Regards
>|||you can add the status_only clause to Kill.
One question - if it's rolled back 100% but still not ending, is it running
something outside of SQL? I.e. something like sp_OaCreate to run a COM compo
nent or xp_cmdshell or xp_sendmail?
If that's the case then SQL can lose sight of whether the process is active
or not - normally because the dll (or whatever) hasn't reported status back.
Alicia
http://www.sqlporn.co.uk|||Maybe it's executing a WSH script, and the server is waiting for someone to
walk by and click "OK" on a MsgBox. :-)
"Alicia" <anonymous@.discussions.microsoft.com> wrote in message
news:ABA285E4-A89A-45BE-BBB0-B2A6DCCEC86F@.microsoft.com...
> you can add the status_only clause to Kill.
> One question - if it's rolled back 100% but still not ending, is it
running something outside of SQL? I.e. something like sp_OaCreate to run a
COM component or xp_cmdshell or xp_sendmail?
> If that's the case then SQL can lose sight of whether the process is
active or not - normally because the dll (or whatever) hasn't reported
status back.
> Alicia
> http://www.sqlporn.co.uk|||Yeah - I've seen that in a job running DTS ActiveX script with debug code in
it...
xp_cmdshell 'notepad' will do it as well :-)
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:OS8lU6QPEHA.2636@.TK2MSFTNGP10.phx.gbl...
> Maybe it's executing a WSH script, and the server is waiting for someone
to
> walk by and click "OK" on a MsgBox. :-)
>
>
> "Alicia" <anonymous@.discussions.microsoft.com> wrote in message
> news:ABA285E4-A89A-45BE-BBB0-B2A6DCCEC86F@.microsoft.com...
> running something outside of SQL? I.e. something like sp_OaCreate to run a
> COM component or xp_cmdshell or xp_sendmail?
> active or not - normally because the dll (or whatever) hasn't reported
> status back.
>