Showing posts with label migrating. Show all posts
Showing posts with label migrating. Show all posts

Wednesday, March 28, 2012

PDF rendering extension not working on SQL RS 2K sp2

I am in the process of migrating apps from SSRS 2K sp1 to SP2 and one of the
application renders to PDF and it is not working.
I thought pdf rendering was missed out from rsserver.config file and added
the line below
<Extension Name="PDF"
type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"/>
...thinking it might help, but still not.
THis is the error msg we are getting whenever we run the report from the
application.
An attempt has been made to use a rendering extension that is not registered
for this report server. --> An attempt has been made to use a rendering
extension that is not registered for this report server. --> An attempt has
been made to use a rendering extension that is not registered for this report
server
When we run the report from reporting service it works...
Can some one help me or point me in how to fix ...
Env: Win2k3 - SQL 2k - SSRS Sp2.
Thanks
- SaravanaAnyone can you reply about this, as I am in a time crunch
regards
- Saravana
"SK" wrote:
> I am in the process of migrating apps from SSRS 2K sp1 to SP2 and one of the
> application renders to PDF and it is not working.
> I thought pdf rendering was missed out from rsserver.config file and added
> the line below
> <Extension Name="PDF"
> type="Microsoft.ReportingServices.Rendering.ImageRenderer.PdfReport,Microsoft.ReportingServices.ImageRendering"/>
> ...thinking it might help, but still not.
> THis is the error msg we are getting whenever we run the report from the
> application.
> An attempt has been made to use a rendering extension that is not registered
> for this report server. --> An attempt has been made to use a rendering
> extension that is not registered for this report server. --> An attempt has
> been made to use a rendering extension that is not registered for this report
> server
> When we run the report from reporting service it works...
> Can some one help me or point me in how to fix ...
> Env: Win2k3 - SQL 2k - SSRS Sp2.
> Thanks
> - Saravana

Friday, March 23, 2012

Pbm Migrating Access 2003 Database to Sql 2005Express Edition

I tried various ways to migrate an access 2003 database with 1 table to

sql Express 2005 Edition without success, I can only find the resulted

sql database in Sql Server Express Edition 2005 without data.

Please advise if any help.

This article might help:

http://support.microsoft.com/kb/237980

Buck Woody

|||Check that you don't have any replication field in the table. This will cause it to fail in migration.sql

Pbm Migrating Access 2003 Database to Sql 2005Express Edition

I tried various ways to migrate an access 2003 database with 1 table to

sql Express 2005 Edition without success, I can only find the resulted

sql database in Sql Server Express Edition 2005 without data.

Please advise if any help.

This article might help:

http://support.microsoft.com/kb/237980

Buck Woody

|||Check that you don't have any replication field in the table. This will cause it to fail in migration.

Friday, March 9, 2012

Password protection

Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Password protection

Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".
Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>
|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.

Password protection

Basic, I know.....
I am migrating an application from Jet to SQL (MSDE). The
database stores user ID and passords for the application.
When designing a table in SQL, ho do I st the password
field to be not viewable as in Jet it is called "password".Hi,
Why dont you use the SQL Server Login and Users. The password column is
encryted and can not be decrypted (Highly secured).
See the topic "Managing security" in SQL server books online.
Thanks
Hari
MCDBA
"Keith Emery" <anonymous@.discussions.microsoft.com> wrote in message
news:79b501c4843f$e8a6d430$a601280a@.phx.gbl...
> Basic, I know.....
> I am migrating an application from Jet to SQL (MSDE). The
> database stores user ID and passords for the application.
> When designing a table in SQL, ho do I st the password
> field to be not viewable as in Jet it is called "password".
>|||Hari's suggestion is valid. Let SQL Server (MSDE) manage security for you.
It gives you one less thing to worry about.
Rand
This posting is provided "as is" with no warranties and confers no rights.