Monday, March 26, 2012
report data with different char-set other than english
Russian language. The report object and the text box object have a very
promising property
called: language but setting this property to the required language is not
helping.
How can i make my report to display this data. We changed the language
seeting and IE encoding settging to view the data in the report to the
correct format but its not working. So far what we found is either the report
or reporting services is escaping the high (over 128) characters in the HTML
page.
Any input is appreciated.
--
TIA
-PSHello PS,
I would like to know this issue clearly.
Did you mean that you want to show the text which is in Russian and stored
in SQL Server database?
If so, I don't think you need to do any configuration in the reporting
service and the textbox will show what you stored in the SQL server
database.
Could you please let me know more clearly about which data you stored in
SQL Server and what you want to show up?
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
Thanks for the reply!
Yes i want to just display the text (Russian language data) in the report so
that user can read the data in Russian language without any problem. The data
is stored in the sql server by another application and we just use sql query
in report to select the data and display it in the report. We are able to
see the same data that is stored in the sql server in the report but the data
is not readable. It is like this "Iiia? aa. AAeeoae." in report. when we
select the data from query analyser it shows the same data("Iiia? aa.
AAeeoae.") which is not readble in russian lang.
When we put this data in a sample html page and set the enocding to
"Cyrillic (Windows) it is readable by russian user. But when we open the
report in report manager and set the encoding in the browser to "Cyrillic
(Windows) it is not readable. what we have to do in reports to make it
readable? we tired the report object and the text box language property to
the russian lang setting but we still get the same junk data. I hope this
--
TIA
-PS
--
TIA
-PS
"Wei Lu [MSFT]" wrote:
> Hello PS,
> I would like to know this issue clearly.
> Did you mean that you want to show the text which is in Russian and stored
> in SQL Server database?
> If so, I don't think you need to do any configuration in the reporting
> service and the textbox will show what you stored in the SQL server
> database.
> Could you please let me know more clearly about which data you stored in
> SQL Server and what you want to show up?
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello PS<
I would like to know the data type of your problem column and you could
send me the sample HTML file to get the data and show up correct.
I guess you are using the varchar data type for the data and varchar data
type did not support the unicode. If you insert the Unicode char into it,
it will convert into some unreadable format and you may not conver it back
directly.
I would like to suggest you modify the application which insert the data
into your sql server.
Here is a sample to insert and retrieve the unicode data for varchar data
type. Or you may consider to use the Nvarchar data type.
drop table Russia
create table Russia (id int, mytext varchar(100))
insert Russia values (3, cast(cast (N''as varbinary(100)) as varchar(100)))
select id, cast (convert(varbinary(100), mytext)as nvarchar(100)) from
Russia
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi ,
How is everything going? Please feel free to let me know if you need any
assistance.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
Thanks for the reply.
I changed the varchar data type column to Nvarchar data type as you said but
still getting the same issue. will my old data will be converted to nvarchar
type after changing just the column data type to nvarchar?
Regarding the html output here is the sample html snip from reporting
service. see the russian char are displayed as "#238;ì.." (reporting services
is escaping the high characters) when i view source from the IE.
In the browser output it is displayed as something like this .."�ëèòåë"..
when i applied the correct enocding in the IE and i still cannot view
correctly
<html>
<head>
</head><body>
Snip from Reporting Services <br>
/*+ RULE ORDERED INDEX(C IDX_TDC_PS_COST) */
N.CALLING_PARTY_NUMBER_RID as "�îìåð à á. �",
N.CALLED_PARTY_NUMBER as "�îìåð à á. �",
C.call_start as "�à òà ",
N.CALL_DURATION as "�ëèòåë.",
decode (CALL_DIRECTION, 'O',
</html>
Below is the sample html that i consturted manually with russian data from
db directly. When i use the correct encoding i'm able to view the russioan
data
<html>
<br><br>
Non escaped high characters will convert properly with the browsers View |
Encoding | Cyrllic (Windows) <br>
/*+ RULE ORDERED INDEX(C IDX_TDC_PS_COST) */
N.CALLING_PARTY_NUMBER_RID as "�îìåð à á. �",
N.CALLED_PARTY_NUMBER as "�îìåð à á. �",
C.call_start as "�à òà ",
N.CALL_DURATION as "�ëèòåë.", decode
(CALL_DIRECTION, 'O',
</body>
</html>
--
TIA
-PS
"Wei Lu [MSFT]" wrote:
> Hi ,
> How is everything going? Please feel free to let me know if you need any
> assistance.
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hello PS,
Changing the data type from Varchar to char will not convert it to right.
Since when you insert the Unicode characetors into a Varchar type column,
the information have corrupted yet. And changing the data type will not fix
those old data.
You may need to contact your application vendor to re input the data.
Hope this helps.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Wei,
Thanks for that info.
ok then i will input fresh data and test it and will let you know.
Thanks
--
TIA
-PS
"Wei Lu [MSFT]" wrote:
> Hello PS,
> Changing the data type from Varchar to char will not convert it to right.
> Since when you insert the Unicode characetors into a Varchar type column,
> the information have corrupted yet. And changing the data type will not fix
> those old data.
> You may need to contact your application vendor to re input the data.
> Hope this helps.
>
> Sincerely,
> Wei Lu
> Microsoft Online Community Support
> ==================================================> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ==================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Wei,
we tested the nvarchar changes with new set of data and it did not work.
The issue we have is not Unicode related because the original russian
characters are ISO-1251. ISO-1251 is just using single byte characters not
Unicode double byte characters.
--
TIA
-PS
"PS" wrote:
> Hi Wei,
> Thanks for that info.
> ok then i will input fresh data and test it and will let you know.
> Thanks
> --
> TIA
> -PS
>
> "Wei Lu [MSFT]" wrote:
> > Hello PS,
> >
> > Changing the data type from Varchar to char will not convert it to right.
> > Since when you insert the Unicode characetors into a Varchar type column,
> > the information have corrupted yet. And changing the data type will not fix
> > those old data.
> >
> > You may need to contact your application vendor to re input the data.
> >
> > Hope this helps.
> >
> >
> > Sincerely,
> >
> > Wei Lu
> > Microsoft Online Community Support
> >
> > ==================================================> >
> > When responding to posts, please "Reply to Group" via your newsreader so
> > that others may learn and benefit from your issue.
> >
> > ==================================================> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >|||Hello PS,
I would like to get the sample database data and your collation settings
for the table and database so that I can reproduce this issue.
Could you please get a simple database backup with only on issue table?
You could zip and send it to me.
To reach my real email, please remove the ONLINE in my display email.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hello PS,
Did you send your database yet? If anything I can help, please feel free to
let me know.
Sincerely,
Wei Lu
Microsoft Online Community Support
==================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.
Friday, March 23, 2012
Report Caching
the execution link:
Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
Background:
IIS running on - Pentium, Server 2003, 1.8GHz
SQL is on - Itanium, Server 2003 64 bit
As far as I've seen everything else is working fine.
ThanksDoes the ReportServersTempDB exists? Are the objects owned by dbo? If they
are not you will need to change the owner to dbo.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> When I attempt to set up an snapshot execution I get this error when
clicking
> the execution link:
> Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> Background:
> IIS running on - Pentium, Server 2003, 1.8GHz
> SQL is on - Itanium, Server 2003 64 bit
> As far as I've seen everything else is working fine.
> Thanks|||Sorry - figured it out - the operator ran rsconfig with the TEMPdb and had a
typo.
"Daniel Reib [MSFT]" wrote:
> Does the ReportServersTempDB exists? Are the objects owned by dbo? If they
> are not you will need to change the owner to dbo.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > When I attempt to set up an snapshot execution I get this error when
> clicking
> > the execution link:
> >
> > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> >
> > Background:
> >
> > IIS running on - Pentium, Server 2003, 1.8GHz
> > SQL is on - Itanium, Server 2003 64 bit
> >
> > As far as I've seen everything else is working fine.
> > Thanks
>
>|||I was wrong again - it is not fixed. The typo is ReportServersTempDB instead
of ReportServerTempDB (extra s before temp). I can't find where this is
stored. The database is correctly named and this is clearly the problem -
where is this name registered'
Since I didn't do the installation I'm not sure where it came from - we've
got a 64 bit box so the install was not traditional.
"NPShinn" wrote:
> Sorry - figured it out - the operator ran rsconfig with the TEMPdb and had a
> typo.
> "Daniel Reib [MSFT]" wrote:
> > Does the ReportServersTempDB exists? Are the objects owned by dbo? If they
> > are not you will need to change the owner to dbo.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no rights.
> >
> >
> > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > When I attempt to set up an snapshot execution I get this error when
> > clicking
> > > the execution link:
> > >
> > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > >
> > > Background:
> > >
> > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > SQL is on - Itanium, Server 2003 64 bit
> > >
> > > As far as I've seen everything else is working fine.
> > > Thanks
> >
> >
> >|||The easiest thing for you to do is rename your TempDB to
ReportServersTempDB. This should get you past this problem.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> I was wrong again - it is not fixed. The typo is ReportServersTempDB
instead
> of ReportServerTempDB (extra s before temp). I can't find where this is
> stored. The database is correctly named and this is clearly the problem -
> where is this name registered'
> Since I didn't do the installation I'm not sure where it came from - we've
> got a 64 bit box so the install was not traditional.
> "NPShinn" wrote:
> > Sorry - figured it out - the operator ran rsconfig with the TEMPdb and
had a
> > typo.
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > Does the ReportServersTempDB exists? Are the objects owned by dbo?
If they
> > > are not you will need to change the owner to dbo.
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
rights.
> > >
> > >
> > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > When I attempt to set up an snapshot execution I get this error when
> > > clicking
> > > > the execution link:
> > > >
> > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > >
> > > > Background:
> > > >
> > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > SQL is on - Itanium, Server 2003 64 bit
> > > >
> > > > As far as I've seen everything else is working fine.
> > > > Thanks
> > >
> > >
> > >|||What about all of the stored procedures that point to ReportServerTempDB? I
think I will have many places to change the name.
The box is brand new, we could reinstall especially since the dbs are on a
different server.
"Daniel Reib [MSFT]" wrote:
> The easiest thing for you to do is rename your TempDB to
> ReportServersTempDB. This should get you past this problem.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > I was wrong again - it is not fixed. The typo is ReportServersTempDB
> instead
> > of ReportServerTempDB (extra s before temp). I can't find where this is
> > stored. The database is correctly named and this is clearly the problem -
> > where is this name registered'
> >
> > Since I didn't do the installation I'm not sure where it came from - we've
> > got a 64 bit box so the install was not traditional.
> >
> > "NPShinn" wrote:
> >
> > > Sorry - figured it out - the operator ran rsconfig with the TEMPdb and
> had a
> > > typo.
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > Does the ReportServersTempDB exists? Are the objects owned by dbo?
> If they
> > > > are not you will need to change the owner to dbo.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > > >
> > > >
> > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > When I attempt to set up an snapshot execution I get this error when
> > > > clicking
> > > > > the execution link:
> > > > >
> > > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > > >
> > > > > Background:
> > > > >
> > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > >
> > > > > As far as I've seen everything else is working fine.
> > > > > Thanks
> > > >
> > > >
> > > >
>
>|||It sounds like the SPs are already pointing to that DB, isn't that the error
you are receiving?
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
news:7F0166CD-1852-4A2F-BD3E-3F00C6E59A00@.microsoft.com...
> What about all of the stored procedures that point to ReportServerTempDB?
I
> think I will have many places to change the name.
> The box is brand new, we could reinstall especially since the dbs are on a
> different server.
> "Daniel Reib [MSFT]" wrote:
> > The easiest thing for you to do is rename your TempDB to
> > ReportServersTempDB. This should get you past this problem.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > > I was wrong again - it is not fixed. The typo is ReportServersTempDB
> > instead
> > > of ReportServerTempDB (extra s before temp). I can't find where this
is
> > > stored. The database is correctly named and this is clearly the
problem -
> > > where is this name registered'
> > >
> > > Since I didn't do the installation I'm not sure where it came from -
we've
> > > got a 64 bit box so the install was not traditional.
> > >
> > > "NPShinn" wrote:
> > >
> > > > Sorry - figured it out - the operator ran rsconfig with the TEMPdb
and
> > had a
> > > > typo.
> > > >
> > > > "Daniel Reib [MSFT]" wrote:
> > > >
> > > > > Does the ReportServersTempDB exists? Are the objects owned by
dbo?
> > If they
> > > > > are not you will need to change the owner to dbo.
> > > > >
> > > > > --
> > > > > -Daniel
> > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > rights.
> > > > >
> > > > >
> > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > > When I attempt to set up an snapshot execution I get this error
when
> > > > > clicking
> > > > > > the execution link:
> > > > > >
> > > > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > > > >
> > > > > > Background:
> > > > > >
> > > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > > >
> > > > > > As far as I've seen everything else is working fine.
> > > > > > Thanks
> > > > >
> > > > >
> > > > >
> >
> >
> >|||None of the stored procedures in ReportServer point to the typo - they are
all correct. here is something from the log file:
w3wp!library!924!09/30/2004-10:25:01:: i INFO: Call to
GetPermissions:/Public/WalMartReportNew
w3wp!library!d64!09/30/2004-10:25:01:: i INFO: Call to GetSystemPermissions
w3wp!library!924!09/30/2004-10:25:01:: e ERROR: Throwing
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details., ;
Info:
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
An internal error occurred on the report server. See the error log for more
details. --> System.Data.SqlClient.SqlException: Invalid object name
'ReportServersTempDB.dbo.ExecutionCache'.
at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
at
Microsoft.ReportingServices.Library.SchedulingDBInterface.UpdateTaskProperties(Task task, Boolean updateSqlAgentSchedule)
at
Microsoft.ReportingServices.Library.SchedulingDBInterface.SetSchedulesNextRunTime(Task t)
at
Microsoft.ReportingServices.Library.SchedulingDBInterface.CheckTasksNextRunTime(Task t)
at Microsoft.ReportingServices.Library.SchedulingDBInterface.ListTasks()
at
Microsoft.ReportingServices.Library.ScheduleCoordinator.ListTasksAsArray()
at Microsoft.ReportingServices.Library.RSService.ListSchedules()
-- End of inner exception stack trace --
"Daniel Reib [MSFT]" wrote:
> It sounds like the SPs are already pointing to that DB, isn't that the error
> you are receiving?
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> news:7F0166CD-1852-4A2F-BD3E-3F00C6E59A00@.microsoft.com...
> > What about all of the stored procedures that point to ReportServerTempDB?
> I
> > think I will have many places to change the name.
> >
> > The box is brand new, we could reinstall especially since the dbs are on a
> > different server.
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > The easiest thing for you to do is rename your TempDB to
> > > ReportServersTempDB. This should get you past this problem.
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > > > I was wrong again - it is not fixed. The typo is ReportServersTempDB
> > > instead
> > > > of ReportServerTempDB (extra s before temp). I can't find where this
> is
> > > > stored. The database is correctly named and this is clearly the
> problem -
> > > > where is this name registered'
> > > >
> > > > Since I didn't do the installation I'm not sure where it came from -
> we've
> > > > got a 64 bit box so the install was not traditional.
> > > >
> > > > "NPShinn" wrote:
> > > >
> > > > > Sorry - figured it out - the operator ran rsconfig with the TEMPdb
> and
> > > had a
> > > > > typo.
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > Does the ReportServersTempDB exists? Are the objects owned by
> dbo?
> > > If they
> > > > > > are not you will need to change the owner to dbo.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
> no
> > > rights.
> > > > > >
> > > > > >
> > > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > > > When I attempt to set up an snapshot execution I get this error
> when
> > > > > > clicking
> > > > > > > the execution link:
> > > > > > >
> > > > > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > > > > >
> > > > > > > Background:
> > > > > > >
> > > > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > > > >
> > > > > > > As far as I've seen everything else is working fine.
> > > > > > > Thanks
> > > > > >
> > > > > >
> > > > > >
> > >
> > >
> > >
>
>|||The thing is we don't store this name anywhere. It is only referenced via
the SPs, so some sp is referring to the wrong DB.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
news:9BF8553B-2CC1-427D-BE45-F2E6CD9505C2@.microsoft.com...
> None of the stored procedures in ReportServer point to the typo - they are
> all correct. here is something from the log file:
> w3wp!library!924!09/30/2004-10:25:01:: i INFO: Call to
> GetPermissions:/Public/WalMartReportNew
> w3wp!library!d64!09/30/2004-10:25:01:: i INFO: Call to
GetSystemPermissions
> w3wp!library!924!09/30/2004-10:25:01:: e ERROR: Throwing
>
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
more
> details., ;
> Info:
>
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> An internal error occurred on the report server. See the error log for
more
> details. --> System.Data.SqlClient.SqlException: Invalid object name
> 'ReportServersTempDB.dbo.ExecutionCache'.
> at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> at
>
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> at
>
Microsoft.ReportingServices.Library.SchedulingDBInterface.UpdateTaskProperti
es(Task task, Boolean updateSqlAgentSchedule)
> at
>
Microsoft.ReportingServices.Library.SchedulingDBInterface.SetSchedulesNextRu
nTime(Task t)
> at
>
Microsoft.ReportingServices.Library.SchedulingDBInterface.CheckTasksNextRunT
ime(Task t)
> at
Microsoft.ReportingServices.Library.SchedulingDBInterface.ListTasks()
> at
> Microsoft.ReportingServices.Library.ScheduleCoordinator.ListTasksAsArray()
> at Microsoft.ReportingServices.Library.RSService.ListSchedules()
> -- End of inner exception stack trace --
>
> "Daniel Reib [MSFT]" wrote:
> > It sounds like the SPs are already pointing to that DB, isn't that the
error
> > you are receiving?
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > news:7F0166CD-1852-4A2F-BD3E-3F00C6E59A00@.microsoft.com...
> > > What about all of the stored procedures that point to
ReportServerTempDB?
> > I
> > > think I will have many places to change the name.
> > >
> > > The box is brand new, we could reinstall especially since the dbs are
on a
> > > different server.
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > The easiest thing for you to do is rename your TempDB to
> > > > ReportServersTempDB. This should get you past this problem.
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > > > > I was wrong again - it is not fixed. The typo is
ReportServersTempDB
> > > > instead
> > > > > of ReportServerTempDB (extra s before temp). I can't find where
this
> > is
> > > > > stored. The database is correctly named and this is clearly the
> > problem -
> > > > > where is this name registered'
> > > > >
> > > > > Since I didn't do the installation I'm not sure where it came
from -
> > we've
> > > > > got a 64 bit box so the install was not traditional.
> > > > >
> > > > > "NPShinn" wrote:
> > > > >
> > > > > > Sorry - figured it out - the operator ran rsconfig with the
TEMPdb
> > and
> > > > had a
> > > > > > typo.
> > > > > >
> > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > >
> > > > > > > Does the ReportServersTempDB exists? Are the objects owned by
> > dbo?
> > > > If they
> > > > > > > are not you will need to change the owner to dbo.
> > > > > > >
> > > > > > > --
> > > > > > > -Daniel
> > > > > > > This posting is provided "AS IS" with no warranties, and
confers
> > no
> > > > rights.
> > > > > > >
> > > > > > >
> > > > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > > > > When I attempt to set up an snapshot execution I get this
error
> > when
> > > > > > > clicking
> > > > > > > > the execution link:
> > > > > > > >
> > > > > > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > > > > > >
> > > > > > > > Background:
> > > > > > > >
> > > > > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > > > > >
> > > > > > > > As far as I've seen everything else is working fine.
> > > > > > > > Thanks
> > > > > > >
> > > > > > >
> > > > > > >
> > > >
> > > >
> > > >
> >
> >
> >|||We ended up reinstalling - twice - to resolve our problem. It did point out
an odd thing. Since we're using a 64 bit server, they installed RS by
pointing at our 32 bit development box. Since RS dbs are already on that
box, the operator changed the names of the new dbs to ReportServers and
ReportServersTempDB. The second time he did the install he named them
ReportServer2 and ReportServer2TempDB.
These dbs had to be backed up and restored onto the 64 bit box and thats
when the error change looking for ReportServer2TempDB. So...I went in and
replaced ReportServer2Tempdb back to ReportServerTempdb inall of the stored
procedures. It didn't help, even after restarting all services on both boxes,
with no reference to ReportServer2TempDB in any sp, it was still looking for
it.
We finally solved the problem by installing onto a box that didn't have RS
on it so that we could name the databases correctly. Overall, al pretty odd
day.
If I've left anything out, feel free to ask.
Nancy Shinn
"Daniel Reib [MSFT]" wrote:
> The thing is we don't store this name anywhere. It is only referenced via
> the SPs, so some sp is referring to the wrong DB.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> news:9BF8553B-2CC1-427D-BE45-F2E6CD9505C2@.microsoft.com...
> > None of the stored procedures in ReportServer point to the typo - they are
> > all correct. here is something from the log file:
> >
> > w3wp!library!924!09/30/2004-10:25:01:: i INFO: Call to
> > GetPermissions:/Public/WalMartReportNew
> > w3wp!library!d64!09/30/2004-10:25:01:: i INFO: Call to
> GetSystemPermissions
> > w3wp!library!924!09/30/2004-10:25:01:: e ERROR: Throwing
> >
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > An internal error occurred on the report server. See the error log for
> more
> > details., ;
> > Info:
> >
> Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > An internal error occurred on the report server. See the error log for
> more
> > details. --> System.Data.SqlClient.SqlException: Invalid object name
> > 'ReportServersTempDB.dbo.ExecutionCache'.
> > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> > cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> > at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> > at
> >
> Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> > at
> >
> Microsoft.ReportingServices.Library.SchedulingDBInterface.UpdateTaskProperti
> es(Task task, Boolean updateSqlAgentSchedule)
> > at
> >
> Microsoft.ReportingServices.Library.SchedulingDBInterface.SetSchedulesNextRu
> nTime(Task t)
> > at
> >
> Microsoft.ReportingServices.Library.SchedulingDBInterface.CheckTasksNextRunT
> ime(Task t)
> > at
> Microsoft.ReportingServices.Library.SchedulingDBInterface.ListTasks()
> > at
> > Microsoft.ReportingServices.Library.ScheduleCoordinator.ListTasksAsArray()
> > at Microsoft.ReportingServices.Library.RSService.ListSchedules()
> > -- End of inner exception stack trace --
> >
> >
> > "Daniel Reib [MSFT]" wrote:
> >
> > > It sounds like the SPs are already pointing to that DB, isn't that the
> error
> > > you are receiving?
> > >
> > > --
> > > -Daniel
> > > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> > >
> > >
> > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > news:7F0166CD-1852-4A2F-BD3E-3F00C6E59A00@.microsoft.com...
> > > > What about all of the stored procedures that point to
> ReportServerTempDB?
> > > I
> > > > think I will have many places to change the name.
> > > >
> > > > The box is brand new, we could reinstall especially since the dbs are
> on a
> > > > different server.
> > > >
> > > > "Daniel Reib [MSFT]" wrote:
> > > >
> > > > > The easiest thing for you to do is rename your TempDB to
> > > > > ReportServersTempDB. This should get you past this problem.
> > > > >
> > > > > --
> > > > > -Daniel
> > > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > > >
> > > > >
> > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > > > > > I was wrong again - it is not fixed. The typo is
> ReportServersTempDB
> > > > > instead
> > > > > > of ReportServerTempDB (extra s before temp). I can't find where
> this
> > > is
> > > > > > stored. The database is correctly named and this is clearly the
> > > problem -
> > > > > > where is this name registered'
> > > > > >
> > > > > > Since I didn't do the installation I'm not sure where it came
> from -
> > > we've
> > > > > > got a 64 bit box so the install was not traditional.
> > > > > >
> > > > > > "NPShinn" wrote:
> > > > > >
> > > > > > > Sorry - figured it out - the operator ran rsconfig with the
> TEMPdb
> > > and
> > > > > had a
> > > > > > > typo.
> > > > > > >
> > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > >
> > > > > > > > Does the ReportServersTempDB exists? Are the objects owned by
> > > dbo?
> > > > > If they
> > > > > > > > are not you will need to change the owner to dbo.
> > > > > > > >
> > > > > > > > --
> > > > > > > > -Daniel
> > > > > > > > This posting is provided "AS IS" with no warranties, and
> confers
> > > no
> > > > > rights.
> > > > > > > >
> > > > > > > >
> > > > > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > > > > > When I attempt to set up an snapshot execution I get this
> error
> > > when
> > > > > > > > clicking
> > > > > > > > > the execution link:
> > > > > > > > >
> > > > > > > > > Invalid object name 'ReportServersTempDB.dbo.ExecutionCache'
> > > > > > > > >
> > > > > > > > > Background:
> > > > > > > > >
> > > > > > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > > > > > >
> > > > > > > > > As far as I've seen everything else is working fine.
> > > > > > > > > Thanks
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > >
> > > > >
> > > > >
> > >
> > >
> > >
>
>|||At some point you ran rsconfig correct? If not then you were never pointing
at the new DBs. Other then that I am really stumped as to why it didn't
work.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
news:17E68A5B-97AF-4455-AB84-0F78BDA375B0@.microsoft.com...
> We ended up reinstalling - twice - to resolve our problem. It did point
out
> an odd thing. Since we're using a 64 bit server, they installed RS by
> pointing at our 32 bit development box. Since RS dbs are already on that
> box, the operator changed the names of the new dbs to ReportServers and
> ReportServersTempDB. The second time he did the install he named them
> ReportServer2 and ReportServer2TempDB.
> These dbs had to be backed up and restored onto the 64 bit box and thats
> when the error change looking for ReportServer2TempDB. So...I went in and
> replaced ReportServer2Tempdb back to ReportServerTempdb inall of the
stored
> procedures. It didn't help, even after restarting all services on both
boxes,
> with no reference to ReportServer2TempDB in any sp, it was still looking
for
> it.
> We finally solved the problem by installing onto a box that didn't have RS
> on it so that we could name the databases correctly. Overall, al pretty
odd
> day.
> If I've left anything out, feel free to ask.
> Nancy Shinn
> "Daniel Reib [MSFT]" wrote:
> > The thing is we don't store this name anywhere. It is only referenced
via
> > the SPs, so some sp is referring to the wrong DB.
> >
> > --
> > -Daniel
> > This posting is provided "AS IS" with no warranties, and confers no
rights.
> >
> >
> > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > news:9BF8553B-2CC1-427D-BE45-F2E6CD9505C2@.microsoft.com...
> > > None of the stored procedures in ReportServer point to the typo - they
are
> > > all correct. here is something from the log file:
> > >
> > > w3wp!library!924!09/30/2004-10:25:01:: i INFO: Call to
> > > GetPermissions:/Public/WalMartReportNew
> > > w3wp!library!d64!09/30/2004-10:25:01:: i INFO: Call to
> > GetSystemPermissions
> > > w3wp!library!924!09/30/2004-10:25:01:: e ERROR: Throwing
> > >
> >
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > > An internal error occurred on the report server. See the error log for
> > more
> > > details., ;
> > > Info:
> > >
> >
Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException:
> > > An internal error occurred on the report server. See the error log for
> > more
> > > details. --> System.Data.SqlClient.SqlException: Invalid object name
> > > 'ReportServersTempDB.dbo.ExecutionCache'.
> > > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior
> > > cmdBehavior, RunBehavior runBehavior, Boolean returnStream)
> > > at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
> > > at
> > >
> >
Microsoft.ReportingServices.Library.InstrumentedSqlCommand.ExecuteNonQuery()
> > > at
> > >
> >
Microsoft.ReportingServices.Library.SchedulingDBInterface.UpdateTaskProperti
> > es(Task task, Boolean updateSqlAgentSchedule)
> > > at
> > >
> >
Microsoft.ReportingServices.Library.SchedulingDBInterface.SetSchedulesNextRu
> > nTime(Task t)
> > > at
> > >
> >
Microsoft.ReportingServices.Library.SchedulingDBInterface.CheckTasksNextRunT
> > ime(Task t)
> > > at
> > Microsoft.ReportingServices.Library.SchedulingDBInterface.ListTasks()
> > > at
> > >
Microsoft.ReportingServices.Library.ScheduleCoordinator.ListTasksAsArray()
> > > at Microsoft.ReportingServices.Library.RSService.ListSchedules()
> > > -- End of inner exception stack trace --
> > >
> > >
> > > "Daniel Reib [MSFT]" wrote:
> > >
> > > > It sounds like the SPs are already pointing to that DB, isn't that
the
> > error
> > > > you are receiving?
> > > >
> > > > --
> > > > -Daniel
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > > >
> > > >
> > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > news:7F0166CD-1852-4A2F-BD3E-3F00C6E59A00@.microsoft.com...
> > > > > What about all of the stored procedures that point to
> > ReportServerTempDB?
> > > > I
> > > > > think I will have many places to change the name.
> > > > >
> > > > > The box is brand new, we could reinstall especially since the dbs
are
> > on a
> > > > > different server.
> > > > >
> > > > > "Daniel Reib [MSFT]" wrote:
> > > > >
> > > > > > The easiest thing for you to do is rename your TempDB to
> > > > > > ReportServersTempDB. This should get you past this problem.
> > > > > >
> > > > > > --
> > > > > > -Daniel
> > > > > > This posting is provided "AS IS" with no warranties, and confers
no
> > > > rights.
> > > > > >
> > > > > >
> > > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in message
> > > > > > news:063F8602-5ADE-41FD-AF52-2DD35669B691@.microsoft.com...
> > > > > > > I was wrong again - it is not fixed. The typo is
> > ReportServersTempDB
> > > > > > instead
> > > > > > > of ReportServerTempDB (extra s before temp). I can't find
where
> > this
> > > > is
> > > > > > > stored. The database is correctly named and this is clearly
the
> > > > problem -
> > > > > > > where is this name registered'
> > > > > > >
> > > > > > > Since I didn't do the installation I'm not sure where it came
> > from -
> > > > we've
> > > > > > > got a 64 bit box so the install was not traditional.
> > > > > > >
> > > > > > > "NPShinn" wrote:
> > > > > > >
> > > > > > > > Sorry - figured it out - the operator ran rsconfig with the
> > TEMPdb
> > > > and
> > > > > > had a
> > > > > > > > typo.
> > > > > > > >
> > > > > > > > "Daniel Reib [MSFT]" wrote:
> > > > > > > >
> > > > > > > > > Does the ReportServersTempDB exists? Are the objects
owned by
> > > > dbo?
> > > > > > If they
> > > > > > > > > are not you will need to change the owner to dbo.
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > -Daniel
> > > > > > > > > This posting is provided "AS IS" with no warranties, and
> > confers
> > > > no
> > > > > > rights.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > "NPShinn" <NPShinn@.discussions.microsoft.com> wrote in
message
> > > > > > > > > news:C2693B9F-4A0B-44B5-A355-4B9F85DC4C57@.microsoft.com...
> > > > > > > > > > When I attempt to set up an snapshot execution I get
this
> > error
> > > > when
> > > > > > > > > clicking
> > > > > > > > > > the execution link:
> > > > > > > > > >
> > > > > > > > > > Invalid object name
'ReportServersTempDB.dbo.ExecutionCache'
> > > > > > > > > >
> > > > > > > > > > Background:
> > > > > > > > > >
> > > > > > > > > > IIS running on - Pentium, Server 2003, 1.8GHz
> > > > > > > > > > SQL is on - Itanium, Server 2003 64 bit
> > > > > > > > > >
> > > > > > > > > > As far as I've seen everything else is working fine.
> > > > > > > > > > Thanks
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > >
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> >
> >
> >
Tuesday, February 21, 2012
replication; what is: SqlCeReplication.Subscriber?
As long as Allow Anonymous Subscribers is set to true on the publication, you can set this property to anything you want. It is normal to set it to a value that allows an administrator to easily identify a given mobile device/user so that when using Replication Monitor or enabling replication logging, you can see who is having trouble and know who that is quickly. So for example, I might set my Subscriber property to "DDSHAFF12345" where DDSHAFF is my mobile login ID that my Windows Mobile app wants to see and 12345 is the OEM ID of my mobile device (which I can get by P/Invoking some native code on the device). But you can feel free to set the value to whatever you want, as long as Allow Anonymous Subscriptions is enabled on the server.
If two subscribers should both attempt to replicate with the same value in this property, they are treated uniquely on the server as SQL Server 2000/2005 appends a unique identifier to the end of the value you provide to avoid conflicts.
One thing to make sure you understand clearly is that if you replicate the very first time and a subscription is successfully created and you then change the value in the Subscriber or HostName properties, you need to reinitialize the subscription during the next replication.
In more secure scenarios, it is common for all subscribers to be defined and granted permissions on the server. In a case like this, you need to use the Subscriber name that the administrator created for you in order for replication to succeed. This is a scenario where Allow Anonymous Subscribers is turned off on the publication and is a more secure, centralized approach to managing merge replication topologies.
-Darren Shaffer