Hi all,
I have an application in production that use a lot of stored procedures and the application doesnt record any error if any during the operation. (There is only a RESUME NEXT sentence).
So I want to know if there is a way to make SQL Server to register an error if any during the execution of a Stored Procedure without changing any of them. Say, that I want SQL Server to register an error during an execution of an user defined Stored Procedure as an internal error.
Thanks in advance.
God Bless.Is there a problem trapping the error in the application (get rid of the resume next and handle the error) ?|||Originally posted by rnealejr
Is there a problem trapping the error in the application (get rid of the resume next and handle the error) ?
Yes, the application is in the production environment and we have to solve the problem as soon as posible. If we change the code in the application then after that we should test the app, and we dont have time.|||Off the top of my head - you could use alerts (but that would be tedious) - do you know what errors you want to trap ?
Showing posts with label production. Show all posts
Showing posts with label production. Show all posts
Tuesday, March 27, 2012
Sunday, March 11, 2012
Error Number - 10040 - Invalid error handling
Any answer to this error message will be appreacited. Gets
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.Aboki (waco361@.hotmail.com) writes:
> Any answer to this error message will be appreacited. Gets
> this when an application is ran on sql server 2000
> database on production. The same application works fine on
> test database even after refreshing of the test with a
> copy of production database is still works fine on test
> databse on test server and not on production.
There does not seem to be any message 10040 in master..sysmessages. Can
you post the completely error message with prefixes and all, so we
can get an idea from where the error message might come?
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||Is this error being generated by the application rather than SQL Server ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Aboki" <waco361@.hotmail.com> wrote in message
news:02cf01c34d6c$5ed1a470$a401280a@.phx.gbl...
Any answer to this error message will be appreacited. Gets
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.Aboki (waco361@.hotmail.com) writes:
> Any answer to this error message will be appreacited. Gets
> this when an application is ran on sql server 2000
> database on production. The same application works fine on
> test database even after refreshing of the test with a
> copy of production database is still works fine on test
> databse on test server and not on production.
There does not seem to be any message 10040 in master..sysmessages. Can
you post the completely error message with prefixes and all, so we
can get an idea from where the error message might come?
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||Is this error being generated by the application rather than SQL Server ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Aboki" <waco361@.hotmail.com> wrote in message
news:02cf01c34d6c$5ed1a470$a401280a@.phx.gbl...
Any answer to this error message will be appreacited. Gets
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.
Error Number - 10040 - Invalid error handling
Any answer to this error message will be appreacited. Gets
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.Aboki (waco361@.hotmail.com) writes:
> Any answer to this error message will be appreacited. Gets
> this when an application is ran on sql server 2000
> database on production. The same application works fine on
> test database even after refreshing of the test with a
> copy of production database is still works fine on test
> databse on test server and not on production.
There does not seem to be any message 10040 in master..sysmessages. Can
you post the completely error message with prefixes and all, so we
can get an idea from where the error message might come?
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||Is this error being generated by the application rather than SQL Server ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Aboki" <waco361@.hotmail.com> wrote in message
news:02cf01c34d6c$5ed1a470$a401280a@.phx.gbl...
Any answer to this error message will be appreacited. Gets
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.Aboki (waco361@.hotmail.com) writes:
> Any answer to this error message will be appreacited. Gets
> this when an application is ran on sql server 2000
> database on production. The same application works fine on
> test database even after refreshing of the test with a
> copy of production database is still works fine on test
> databse on test server and not on production.
There does not seem to be any message 10040 in master..sysmessages. Can
you post the completely error message with prefixes and all, so we
can get an idea from where the error message might come?
Erland Sommarskog, SQL Server MVP, sommar@.algonet.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp|||Is this error being generated by the application rather than SQL Server ?
--
HTH
Jasper Smith (SQL Server MVP)
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Aboki" <waco361@.hotmail.com> wrote in message
news:02cf01c34d6c$5ed1a470$a401280a@.phx.gbl...
Any answer to this error message will be appreacited. Gets
this when an application is ran on sql server 2000
database on production. The same application works fine on
test database even after refreshing of the test with a
copy of production database is still works fine on test
databse on test server and not on production.
Thanks,
Henry.
Wednesday, March 7, 2012
Error message:
One of our production box is running really slow right now.. and I issue the following statement: DBCC MEMUSAGE and I got back the following error message:
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:204858) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206393) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206392) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
The comment doesn't even finish. I thought there were some corruption on our databases, but I schedule a job and ran it through all our databases with DBCC checkdb. None of them seems to have any integrity or data corruption problem.
Any idea where else I should look for any possible problems? I free the buffer and procedure cache using
DBCC FREEPROCCACHE
go
DBCC DROPCLEANBUFFERS
go
already!
help!
What sql server build are you on? You might consider going through
826433 PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
http://support.microsoft.com/?id=826433 and also considre opening a case
with PSS Support for this.
In the meantime, I'd suggest you check your Application and Sys event logs
for hardware errors. Also check your backups. Do you see the same error
message after restoring them?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:204858) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206393) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206392) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
The comment doesn't even finish. I thought there were some corruption on our databases, but I schedule a job and ran it through all our databases with DBCC checkdb. None of them seems to have any integrity or data corruption problem.
Any idea where else I should look for any possible problems? I free the buffer and procedure cache using
DBCC FREEPROCCACHE
go
DBCC DROPCLEANBUFFERS
go
already!
help!
What sql server build are you on? You might consider going through
826433 PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
http://support.microsoft.com/?id=826433 and also considre opening a case
with PSS Support for this.
In the meantime, I'd suggest you check your Application and Sys event logs
for hardware errors. Also check your backups. Do you see the same error
message after restoring them?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Error message:
One of our production box is running really slow right now.. and I issue the
following statement: DBCC MEMUSAGE and I got back the following error mess
age:
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:204858) with latch type SH. VerifyPageId fa
iled.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206393) with latch type SH. VerifyPageId fa
iled.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206392) with latch type SH. VerifyPageId fa
iled.
Server: Msg 8966, Level 16, State 1, Line 1
The comment doesn't even finish. I thought there were some corruption on ou
r databases, but I schedule a job and ran it through all our databases with
DBCC checkdb. None of them seems to have any integrity or data corruption p
roblem.
Any idea where else I should look for any possible problems? I free the buf
fer and procedure cache using
DBCC FREEPROCCACHE
go
DBCC DROPCLEANBUFFERS
go
already!
help!What sql server build are you on? You might consider going through
826433 PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
http://support.microsoft.com/?id=826433 and also considre opening a case
with PSS Support for this.
In the meantime, I'd suggest you check your Application and Sys event logs
for hardware errors. Also check your backups. Do you see the same error
message after restoring them?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
following statement: DBCC MEMUSAGE and I got back the following error mess
age:
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:204858) with latch type SH. VerifyPageId fa
iled.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206393) with latch type SH. VerifyPageId fa
iled.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206392) with latch type SH. VerifyPageId fa
iled.
Server: Msg 8966, Level 16, State 1, Line 1
The comment doesn't even finish. I thought there were some corruption on ou
r databases, but I schedule a job and ran it through all our databases with
DBCC checkdb. None of them seems to have any integrity or data corruption p
roblem.
Any idea where else I should look for any possible problems? I free the buf
fer and procedure cache using
DBCC FREEPROCCACHE
go
DBCC DROPCLEANBUFFERS
go
already!
help!What sql server build are you on? You might consider going through
826433 PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
http://support.microsoft.com/?id=826433 and also considre opening a case
with PSS Support for this.
In the meantime, I'd suggest you check your Application and Sys event logs
for hardware errors. Also check your backups. Do you see the same error
message after restoring them?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Sunday, February 26, 2012
Error message:
One of our production box is running really slow right now.. and I issue the following statement: DBCC MEMUSAGE and I got back the following error message:
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:204858) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206393) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206392) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
The comment doesn't even finish. I thought there were some corruption on our databases, but I schedule a job and ran it through all our databases with DBCC checkdb. None of them seems to have any integrity or data corruption problem.
Any idea where else I should look for any possible problems? I free the buffer and procedure cache using
DBCC FREEPROCCACHE
go
DBCC DROPCLEANBUFFERS
go
already!
help!What sql server build are you on? You might consider going through
826433 PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
http://support.microsoft.com/?id=826433 and also considre opening a case
with PSS Support for this.
In the meantime, I'd suggest you check your Application and Sys event logs
for hardware errors. Also check your backups. Do you see the same error
message after restoring them?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Server: Msg 8966, Level 16, State 4, Line 1
Could not read and latch page (1:204858) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206393) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
Could not read and latch page (1:206392) with latch type SH. VerifyPageId failed.
Server: Msg 8966, Level 16, State 1, Line 1
The comment doesn't even finish. I thought there were some corruption on our databases, but I schedule a job and ran it through all our databases with DBCC checkdb. None of them seems to have any integrity or data corruption problem.
Any idea where else I should look for any possible problems? I free the buffer and procedure cache using
DBCC FREEPROCCACHE
go
DBCC DROPCLEANBUFFERS
go
already!
help!What sql server build are you on? You might consider going through
826433 PRB: Additional SQL Server Diagnostics Added to Detect Unreported I/O
http://support.microsoft.com/?id=826433 and also considre opening a case
with PSS Support for this.
In the meantime, I'd suggest you check your Application and Sys event logs
for hardware errors. Also check your backups. Do you see the same error
message after restoring them?
Vikram Jayaram
Microsoft, SQL Server
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to MSDN & use http://msdn.microsoft.com/newsgroups.
Error Message When Deploying Report - The Item '/Data Sources'
Hi All,
I am wondering is someone can point me in the right direction,
I updated to the latest service pack on my Report Server Production Machine
and now when I attempt to deloy a report I get the following message
The Item '/Data Sources' already exists
I have tried everything I can think of to stop the message
~ Disabling and Enabling the OverwriteDataSources
~ Adding the Shared Datasource directly into the SQL frontend...
~ Running around like a chicken with no head
all seem to have the same effect...
Currently all other reports seem to work ok...
Has anyone got idea... apart from never ever ever updating to the latest
patches ;)
...Cheers
MattOn Sep 11, 10:26 pm, Aussie Matt
<AussieM...@.discussions.microsoft.com> wrote:
> Hi All,
> I am wondering is someone can point me in the right direction,
> I updated to the latest service pack on my Report Server Production Machine
> and now when I attempt to deloy a report I get the following message
> The Item '/Data Sources' already exists
> I have tried everything I can think of to stop the message
> ~ Disabling and Enabling the OverwriteDataSources
> ~ Adding the Shared Datasource directly into the SQL frontend...
> ~ Running around like a chicken with no head
> all seem to have the same effect...
> Currently all other reports seem to work ok...
> Has anyone got idea... apart from never ever ever updating to the latest
> patches ;)
> ...Cheers
> Matt
This might be overly simplistic, but have you tried to reselect the
datasource in the Report Mgr for the report? I have installed SP2 on a
couple different Report Servers w/no problems.
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Enrique,
Hi mate... yes that seems to be ok..
The report actually renders ok in the development environment...
I even tried creating a new report to see if that would overwrite the
existing shared data source but it has the same problemâ?¦. I am wondering if
it actually related to IIS6 somehow.. thou all the permissions look ok...
Thanks for the advice thou,
Cheers
Matt
"EMartinez" wrote:
> On Sep 11, 10:26 pm, Aussie Matt
> <AussieM...@.discussions.microsoft.com> wrote:
> > Hi All,
> > I am wondering is someone can point me in the right direction,
> > I updated to the latest service pack on my Report Server Production Machine
> > and now when I attempt to deloy a report I get the following message
> >
> > The Item '/Data Sources' already exists
> >
> > I have tried everything I can think of to stop the message
> > ~ Disabling and Enabling the OverwriteDataSources
> > ~ Adding the Shared Datasource directly into the SQL frontend...
> > ~ Running around like a chicken with no head
> >
> > all seem to have the same effect...
> >
> > Currently all other reports seem to work ok...
> >
> > Has anyone got idea... apart from never ever ever updating to the latest
> > patches ;)
> >
> > ...Cheers
> >
> > Matt
>
> This might be overly simplistic, but have you tried to reselect the
> datasource in the Report Mgr for the report? I have installed SP2 on a
> couple different Report Servers w/no problems.
> Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||Hello Again,
Well I fixed it, not sure how / why it got screwy, to fix it I went to the
Reporting Services Configuration Manager
and reset the default properties for the the Report Server Virtual
Directory and Report Manager Virtual Directory... this seem to rectify
whatever the problem
was...
Cheers
Matt
"Aussie Matt" wrote:
> Enrique,
> Hi mate... yes that seems to be ok..
> The report actually renders ok in the development environment...
> I even tried creating a new report to see if that would overwrite the
> existing shared data source but it has the same problemâ?¦. I am wondering if
> it actually related to IIS6 somehow.. thou all the permissions look ok...
> Thanks for the advice thou,
> Cheers
> Matt
> "EMartinez" wrote:
> > On Sep 11, 10:26 pm, Aussie Matt
> > <AussieM...@.discussions.microsoft.com> wrote:
> > > Hi All,
> > > I am wondering is someone can point me in the right direction,
> > > I updated to the latest service pack on my Report Server Production Machine
> > > and now when I attempt to deloy a report I get the following message
> > >
> > > The Item '/Data Sources' already exists
> > >
> > > I have tried everything I can think of to stop the message
> > > ~ Disabling and Enabling the OverwriteDataSources
> > > ~ Adding the Shared Datasource directly into the SQL frontend...
> > > ~ Running around like a chicken with no head
> > >
> > > all seem to have the same effect...
> > >
> > > Currently all other reports seem to work ok...
> > >
> > > Has anyone got idea... apart from never ever ever updating to the latest
> > > patches ;)
> > >
> > > ...Cheers
> > >
> > > Matt
> >
> >
> > This might be overly simplistic, but have you tried to reselect the
> > datasource in the Report Mgr for the report? I have installed SP2 on a
> > couple different Report Servers w/no problems.
> > Hope this helps.
> >
> > Regards,
> >
> > Enrique Martinez
> > Sr. Software Consultant
> >
> >|||On Sep 12, 5:24 am, Aussie Matt <AussieM...@.discussions.microsoft.com>
wrote:
> Hello Again,
> Well I fixed it, not sure how / why it got screwy, to fix it I went to the
> Reporting Services Configuration Manager
> and reset the default properties for the the Report Server Virtual
> Directory and Report Manager Virtual Directory... this seem to rectify
> whatever the problem
> was...
> Cheers
> Matt
> "Aussie Matt" wrote:
> > Enrique,
> > Hi mate... yes that seems to be ok..
> > The report actually renders ok in the development environment...
> > I even tried creating a new report to see if that would overwrite the
> > existing shared data source but it has the same problem... I am wondering if
> > it actually related to IIS6 somehow.. thou all the permissions look ok...
> > Thanks for the advice thou,
> > Cheers
> > Matt
> > "EMartinez" wrote:
> > > On Sep 11, 10:26 pm, Aussie Matt
> > > <AussieM...@.discussions.microsoft.com> wrote:
> > > > Hi All,
> > > > I am wondering is someone can point me in the right direction,
> > > > I updated to the latest service pack on my Report Server Production Machine
> > > > and now when I attempt to deloy a report I get the following message
> > > > The Item '/Data Sources' already exists
> > > > I have tried everything I can think of to stop the message
> > > > ~ Disabling and Enabling the OverwriteDataSources
> > > > ~ Adding the Shared Datasource directly into the SQL frontend...
> > > > ~ Running around like a chicken with no head
> > > > all seem to have the same effect...
> > > > Currently all other reports seem to work ok...
> > > > Has anyone got idea... apart from never ever ever updating to the latest
> > > > patches ;)
> > > > ...Cheers
> > > > Matt
> > > This might be overly simplistic, but have you tried to reselect the
> > > datasource in the Report Mgr for the report? I have installed SP2 on a
> > > couple different Report Servers w/no problems.
> > > Hope this helps.
> > > Regards,
> > > Enrique Martinez
> > > Sr. Software Consultant
I'm surprised that this resolved the issue; however, I'm glad you
fixed the problem. Let me know if I can be of further assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||I just spent a considerable amount of time trying to debug this error, and in
the end it was a permissions problem. As a new employee I had been given
access to the Reports folder but not to the Data Sources folder.
Hopefully this note can save someone else some time (and frustration)
diagnosing this error.
I am wondering is someone can point me in the right direction,
I updated to the latest service pack on my Report Server Production Machine
and now when I attempt to deloy a report I get the following message
The Item '/Data Sources' already exists
I have tried everything I can think of to stop the message
~ Disabling and Enabling the OverwriteDataSources
~ Adding the Shared Datasource directly into the SQL frontend...
~ Running around like a chicken with no head
all seem to have the same effect...
Currently all other reports seem to work ok...
Has anyone got idea... apart from never ever ever updating to the latest
patches ;)
...Cheers
MattOn Sep 11, 10:26 pm, Aussie Matt
<AussieM...@.discussions.microsoft.com> wrote:
> Hi All,
> I am wondering is someone can point me in the right direction,
> I updated to the latest service pack on my Report Server Production Machine
> and now when I attempt to deloy a report I get the following message
> The Item '/Data Sources' already exists
> I have tried everything I can think of to stop the message
> ~ Disabling and Enabling the OverwriteDataSources
> ~ Adding the Shared Datasource directly into the SQL frontend...
> ~ Running around like a chicken with no head
> all seem to have the same effect...
> Currently all other reports seem to work ok...
> Has anyone got idea... apart from never ever ever updating to the latest
> patches ;)
> ...Cheers
> Matt
This might be overly simplistic, but have you tried to reselect the
datasource in the Report Mgr for the report? I have installed SP2 on a
couple different Report Servers w/no problems.
Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Enrique,
Hi mate... yes that seems to be ok..
The report actually renders ok in the development environment...
I even tried creating a new report to see if that would overwrite the
existing shared data source but it has the same problemâ?¦. I am wondering if
it actually related to IIS6 somehow.. thou all the permissions look ok...
Thanks for the advice thou,
Cheers
Matt
"EMartinez" wrote:
> On Sep 11, 10:26 pm, Aussie Matt
> <AussieM...@.discussions.microsoft.com> wrote:
> > Hi All,
> > I am wondering is someone can point me in the right direction,
> > I updated to the latest service pack on my Report Server Production Machine
> > and now when I attempt to deloy a report I get the following message
> >
> > The Item '/Data Sources' already exists
> >
> > I have tried everything I can think of to stop the message
> > ~ Disabling and Enabling the OverwriteDataSources
> > ~ Adding the Shared Datasource directly into the SQL frontend...
> > ~ Running around like a chicken with no head
> >
> > all seem to have the same effect...
> >
> > Currently all other reports seem to work ok...
> >
> > Has anyone got idea... apart from never ever ever updating to the latest
> > patches ;)
> >
> > ...Cheers
> >
> > Matt
>
> This might be overly simplistic, but have you tried to reselect the
> datasource in the Report Mgr for the report? I have installed SP2 on a
> couple different Report Servers w/no problems.
> Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>|||Hello Again,
Well I fixed it, not sure how / why it got screwy, to fix it I went to the
Reporting Services Configuration Manager
and reset the default properties for the the Report Server Virtual
Directory and Report Manager Virtual Directory... this seem to rectify
whatever the problem
was...
Cheers
Matt
"Aussie Matt" wrote:
> Enrique,
> Hi mate... yes that seems to be ok..
> The report actually renders ok in the development environment...
> I even tried creating a new report to see if that would overwrite the
> existing shared data source but it has the same problemâ?¦. I am wondering if
> it actually related to IIS6 somehow.. thou all the permissions look ok...
> Thanks for the advice thou,
> Cheers
> Matt
> "EMartinez" wrote:
> > On Sep 11, 10:26 pm, Aussie Matt
> > <AussieM...@.discussions.microsoft.com> wrote:
> > > Hi All,
> > > I am wondering is someone can point me in the right direction,
> > > I updated to the latest service pack on my Report Server Production Machine
> > > and now when I attempt to deloy a report I get the following message
> > >
> > > The Item '/Data Sources' already exists
> > >
> > > I have tried everything I can think of to stop the message
> > > ~ Disabling and Enabling the OverwriteDataSources
> > > ~ Adding the Shared Datasource directly into the SQL frontend...
> > > ~ Running around like a chicken with no head
> > >
> > > all seem to have the same effect...
> > >
> > > Currently all other reports seem to work ok...
> > >
> > > Has anyone got idea... apart from never ever ever updating to the latest
> > > patches ;)
> > >
> > > ...Cheers
> > >
> > > Matt
> >
> >
> > This might be overly simplistic, but have you tried to reselect the
> > datasource in the Report Mgr for the report? I have installed SP2 on a
> > couple different Report Servers w/no problems.
> > Hope this helps.
> >
> > Regards,
> >
> > Enrique Martinez
> > Sr. Software Consultant
> >
> >|||On Sep 12, 5:24 am, Aussie Matt <AussieM...@.discussions.microsoft.com>
wrote:
> Hello Again,
> Well I fixed it, not sure how / why it got screwy, to fix it I went to the
> Reporting Services Configuration Manager
> and reset the default properties for the the Report Server Virtual
> Directory and Report Manager Virtual Directory... this seem to rectify
> whatever the problem
> was...
> Cheers
> Matt
> "Aussie Matt" wrote:
> > Enrique,
> > Hi mate... yes that seems to be ok..
> > The report actually renders ok in the development environment...
> > I even tried creating a new report to see if that would overwrite the
> > existing shared data source but it has the same problem... I am wondering if
> > it actually related to IIS6 somehow.. thou all the permissions look ok...
> > Thanks for the advice thou,
> > Cheers
> > Matt
> > "EMartinez" wrote:
> > > On Sep 11, 10:26 pm, Aussie Matt
> > > <AussieM...@.discussions.microsoft.com> wrote:
> > > > Hi All,
> > > > I am wondering is someone can point me in the right direction,
> > > > I updated to the latest service pack on my Report Server Production Machine
> > > > and now when I attempt to deloy a report I get the following message
> > > > The Item '/Data Sources' already exists
> > > > I have tried everything I can think of to stop the message
> > > > ~ Disabling and Enabling the OverwriteDataSources
> > > > ~ Adding the Shared Datasource directly into the SQL frontend...
> > > > ~ Running around like a chicken with no head
> > > > all seem to have the same effect...
> > > > Currently all other reports seem to work ok...
> > > > Has anyone got idea... apart from never ever ever updating to the latest
> > > > patches ;)
> > > > ...Cheers
> > > > Matt
> > > This might be overly simplistic, but have you tried to reselect the
> > > datasource in the Report Mgr for the report? I have installed SP2 on a
> > > couple different Report Servers w/no problems.
> > > Hope this helps.
> > > Regards,
> > > Enrique Martinez
> > > Sr. Software Consultant
I'm surprised that this resolved the issue; however, I'm glad you
fixed the problem. Let me know if I can be of further assistance.
Regards,
Enrique Martinez
Sr. Software Consultant|||I just spent a considerable amount of time trying to debug this error, and in
the end it was a permissions problem. As a new employee I had been given
access to the Reports folder but not to the Data Sources folder.
Hopefully this note can save someone else some time (and frustration)
diagnosing this error.
Error message when creating replication with generated SQL scripts
Hi all SQL Replication experts :)
I have created my production server as a distributor and a publication on that server. On my backup server I have created a pull subscription. After that I have generated SQL scripts on my backup server so I can create the pull subscription anytime.
To test my script I used sp_removedbreplication 'dbname' to remove replication on the backup server. I then used the generated SQL script to create the pull subscription again. I got this error message
Job 'ProdServName_DBName-BackServName-DBName401A48AE-D8DC-4F29-A610-13916370CD0B' started successfully.
Server: Msg 208, Level 16, State 1, Procedure sp_addsubscription, Line 135
Invalid object name 'syspublications'.
What does this Error message mean and what can I do about it?
Grateful for all answers
Best,
/M
Subscribe to:
Posts (Atom)