Error:
The OLE DB provider "SQLNCLI" for linked server reported an error. Execution
terminated by the provider because a resource limit was reached.
Situation:
Large query is pulled from one server to another (data warehouse).
Suspect:
DTC on the Windows server 2003 where the source server is located (SQL 2k)
does not have DTC enabled:
Looking for:
A work-around as we are in a situation where the server cannot yet be
rebooted.
Question:
Is there a way to configure named pipes to effectively handle the resource
limitation on linked servers?
--
Regards,
JamieAs a workaround, can you try using TCP\IP provider for linking?
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:A4DB5E7F-56F3-46AE-9858-0F67546B82ED@.microsoft.com...
> Error:
> The OLE DB provider "SQLNCLI" for linked server reported an error.
> Execution
> terminated by the provider because a resource limit was reached.
> Situation:
> Large query is pulled from one server to another (data warehouse).
> Suspect:
> DTC on the Windows server 2003 where the source server is located (SQL 2k)
> does not have DTC enabled:
> Looking for:
> A work-around as we are in a situation where the server cannot yet be
> rebooted.
> Question:
> Is there a way to configure named pipes to effectively handle the resource
> limitation on linked servers?
> --
> Regards,
> Jamie|||I think I may be misunderstanding. I'm unaware of TCP/IP configurations
other than what I already use. Which it may be that you misunderstood my
question, thinking I am using named pipes (not so - have named pipes turned
off).
Thought is - Will named pipes offer a temporary solution to overcome the
resource limitation imposed by the WinSvr2003 R2 without the DTC turned on?
Dunno enough to guess whether there is something in it that will work.
BACKGROUND:
I currently use TCP/IP and aliasing and I suspect the linked servers use
that already to communicate.
When we access a view on a SQL 2000 server using SQL 2005 on another server
(both are WinSvr 2003 R2 64 bit).
There is a problem with the DTC (I did not mention this one - I am waiting
for a server reboot to fix it - http://support.microsoft.com/kb/329332 or
http://support.microsoft.com/?kbid=873160 The operation could not be
performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
distributed transaction. OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a]. [OLE/DB provider
returned message: New transaction cannot enlist in the specified transaction
coordinator. ]).
The one housing SQL 2000 does not yet have DTC setup for network access.
The situation does not allow us to reboot (short of an emergency of which
this is not - instead each view must be re-written to get around the resource
issue - usually just create a sub-query in place of the view).
Herein lies the problem: After rewriting a bunch of failing views we
discovered that if a view is altered and consumes more resources, the
borderline ones we use for data-warehousing archive information at night can
fail for no other reason than that - view times out - resource limit
reached... blah blah). I hate it when a job fails.
Regards,
Jamie
"TheSQLGuru" wrote:
> As a workaround, can you try using TCP\IP provider for linking?
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:A4DB5E7F-56F3-46AE-9858-0F67546B82ED@.microsoft.com...
> > Error:
> > The OLE DB provider "SQLNCLI" for linked server reported an error.
> > Execution
> > terminated by the provider because a resource limit was reached.
> > Situation:
> > Large query is pulled from one server to another (data warehouse).
> > Suspect:
> > DTC on the Windows server 2003 where the source server is located (SQL 2k)
> > does not have DTC enabled:
> > Looking for:
> > A work-around as we are in a situation where the server cannot yet be
> > rebooted.
> >
> > Question:
> > Is there a way to configure named pipes to effectively handle the resource
> > limitation on linked servers?
> > --
> > Regards,
> > Jamie
>
>|||Misread first post. My bad. I don't know that there is a way to cut DTC
out of the loop, regardless of what connection mechanism you are using. I
don't have any other suggestions for possible workarounds for your issue
either. :(
--
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:AF702DC6-3A07-4D85-9713-8C5406099EED@.microsoft.com...
>I think I may be misunderstanding. I'm unaware of TCP/IP configurations
> other than what I already use. Which it may be that you misunderstood my
> question, thinking I am using named pipes (not so - have named pipes
> turned
> off).
> Thought is - Will named pipes offer a temporary solution to overcome the
> resource limitation imposed by the WinSvr2003 R2 without the DTC turned
> on?
> Dunno enough to guess whether there is something in it that will work.
> BACKGROUND:
> I currently use TCP/IP and aliasing and I suspect the linked servers use
> that already to communicate.
> When we access a view on a SQL 2000 server using SQL 2005 on another
> server
> (both are WinSvr 2003 R2 64 bit).
> There is a problem with the DTC (I did not mention this one - I am waiting
> for a server reboot to fix it - http://support.microsoft.com/kb/329332 or
> http://support.microsoft.com/?kbid=873160 The operation could not be
> performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
> distributed transaction. OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]. [OLE/DB provider
> returned message: New transaction cannot enlist in the specified
> transaction
> coordinator. ]).
> The one housing SQL 2000 does not yet have DTC setup for network access.
> The situation does not allow us to reboot (short of an emergency of which
> this is not - instead each view must be re-written to get around the
> resource
> issue - usually just create a sub-query in place of the view).
> Herein lies the problem: After rewriting a bunch of failing views we
> discovered that if a view is altered and consumes more resources, the
> borderline ones we use for data-warehousing archive information at night
> can
> fail for no other reason than that - view times out - resource limit
> reached... blah blah). I hate it when a job fails.
>
> --
> Regards,
> Jamie
>
> "TheSQLGuru" wrote:
>> As a workaround, can you try using TCP\IP provider for linking?
>> --
>> Kevin G. Boles
>> Indicium Resources, Inc.
>> SQL Server MVP
>> kgboles a earthlink dt net
>>
>> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
>> news:A4DB5E7F-56F3-46AE-9858-0F67546B82ED@.microsoft.com...
>> > Error:
>> > The OLE DB provider "SQLNCLI" for linked server reported an error.
>> > Execution
>> > terminated by the provider because a resource limit was reached.
>> > Situation:
>> > Large query is pulled from one server to another (data warehouse).
>> > Suspect:
>> > DTC on the Windows server 2003 where the source server is located (SQL
>> > 2k)
>> > does not have DTC enabled:
>> > Looking for:
>> > A work-around as we are in a situation where the server cannot yet be
>> > rebooted.
>> >
>> > Question:
>> > Is there a way to configure named pipes to effectively handle the
>> > resource
>> > limitation on linked servers?
>> > --
>> > Regards,
>> > Jamie
>>
Showing posts with label error. Show all posts
Showing posts with label error. Show all posts
Friday, March 30, 2012
resource limit was reached
Error:
The OLE DB provider "SQLNCLI" for linked server reported an error. Execution
terminated by the provider because a resource limit was reached.
Situation:
Large query is pulled from one server to another (data warehouse).
Suspect:
DTC on the Windows server 2003 where the source server is located (SQL 2k)
does not have DTC enabled:
Looking for:
A work-around as we are in a situation where the server cannot yet be
rebooted.
Question:
Is there a way to configure named pipes to effectively handle the resource
limitation on linked servers?
Regards,
Jamie
As a workaround, can you try using TCP\IP provider for linking?
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:A4DB5E7F-56F3-46AE-9858-0F67546B82ED@.microsoft.com...
> Error:
> The OLE DB provider "SQLNCLI" for linked server reported an error.
> Execution
> terminated by the provider because a resource limit was reached.
> Situation:
> Large query is pulled from one server to another (data warehouse).
> Suspect:
> DTC on the Windows server 2003 where the source server is located (SQL 2k)
> does not have DTC enabled:
> Looking for:
> A work-around as we are in a situation where the server cannot yet be
> rebooted.
> Question:
> Is there a way to configure named pipes to effectively handle the resource
> limitation on linked servers?
> --
> Regards,
> Jamie
|||I think I may be misunderstanding. I'm unaware of TCP/IP configurations
other than what I already use. Which it may be that you misunderstood my
question, thinking I am using named pipes (not so - have named pipes turned
off).
Thought is - Will named pipes offer a temporary solution to overcome the
resource limitation imposed by the WinSvr2003 R2 without the DTC turned on?
Dunno enough to guess whether there is something in it that will work.
BACKGROUND:
I currently use TCP/IP and aliasing and I suspect the linked servers use
that already to communicate.
When we access a view on a SQL 2000 server using SQL 2005 on another server
(both are WinSvr 2003 R2 64 bit).
There is a problem with the DTC (I did not mention this one - I am waiting
for a server reboot to fix it - http://support.microsoft.com/kb/329332 or
http://support.microsoft.com/?kbid=873160 The operation could not be
performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
distributed transaction. OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a]. [OLE/DB provider
returned message: New transaction cannot enlist in the specified transaction
coordinator. ]).
The one housing SQL 2000 does not yet have DTC setup for network access.
The situation does not allow us to reboot (short of an emergency of which
this is not - instead each view must be re-written to get around the resource
issue - usually just create a sub-query in place of the view).
Herein lies the problem: After rewriting a bunch of failing views we
discovered that if a view is altered and consumes more resources, the
borderline ones we use for data-warehousing archive information at night can
fail for no other reason than that - view times out - resource limit
reached... blah blah). I hate it when a job fails.
Regards,
Jamie
"TheSQLGuru" wrote:
> As a workaround, can you try using TCP\IP provider for linking?
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:A4DB5E7F-56F3-46AE-9858-0F67546B82ED@.microsoft.com...
>
>
|||Misread first post. My bad. I don't know that there is a way to cut DTC
out of the loop, regardless of what connection mechanism you are using. I
don't have any other suggestions for possible workarounds for your issue
either.
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:AF702DC6-3A07-4D85-9713-8C5406099EED@.microsoft.com...[vbcol=seagreen]
>I think I may be misunderstanding. I'm unaware of TCP/IP configurations
> other than what I already use. Which it may be that you misunderstood my
> question, thinking I am using named pipes (not so - have named pipes
> turned
> off).
> Thought is - Will named pipes offer a temporary solution to overcome the
> resource limitation imposed by the WinSvr2003 R2 without the DTC turned
> on?
> Dunno enough to guess whether there is something in it that will work.
> BACKGROUND:
> I currently use TCP/IP and aliasing and I suspect the linked servers use
> that already to communicate.
> When we access a view on a SQL 2000 server using SQL 2005 on another
> server
> (both are WinSvr 2003 R2 64 bit).
> There is a problem with the DTC (I did not mention this one - I am waiting
> for a server reboot to fix it - http://support.microsoft.com/kb/329332 or
> http://support.microsoft.com/?kbid=873160 The operation could not be
> performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
> distributed transaction. OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]. [OLE/DB provider
> returned message: New transaction cannot enlist in the specified
> transaction
> coordinator. ]).
> The one housing SQL 2000 does not yet have DTC setup for network access.
> The situation does not allow us to reboot (short of an emergency of which
> this is not - instead each view must be re-written to get around the
> resource
> issue - usually just create a sub-query in place of the view).
> Herein lies the problem: After rewriting a bunch of failing views we
> discovered that if a view is altered and consumes more resources, the
> borderline ones we use for data-warehousing archive information at night
> can
> fail for no other reason than that - view times out - resource limit
> reached... blah blah). I hate it when a job fails.
>
> --
> Regards,
> Jamie
>
> "TheSQLGuru" wrote:
The OLE DB provider "SQLNCLI" for linked server reported an error. Execution
terminated by the provider because a resource limit was reached.
Situation:
Large query is pulled from one server to another (data warehouse).
Suspect:
DTC on the Windows server 2003 where the source server is located (SQL 2k)
does not have DTC enabled:
Looking for:
A work-around as we are in a situation where the server cannot yet be
rebooted.
Question:
Is there a way to configure named pipes to effectively handle the resource
limitation on linked servers?
Regards,
Jamie
As a workaround, can you try using TCP\IP provider for linking?
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:A4DB5E7F-56F3-46AE-9858-0F67546B82ED@.microsoft.com...
> Error:
> The OLE DB provider "SQLNCLI" for linked server reported an error.
> Execution
> terminated by the provider because a resource limit was reached.
> Situation:
> Large query is pulled from one server to another (data warehouse).
> Suspect:
> DTC on the Windows server 2003 where the source server is located (SQL 2k)
> does not have DTC enabled:
> Looking for:
> A work-around as we are in a situation where the server cannot yet be
> rebooted.
> Question:
> Is there a way to configure named pipes to effectively handle the resource
> limitation on linked servers?
> --
> Regards,
> Jamie
|||I think I may be misunderstanding. I'm unaware of TCP/IP configurations
other than what I already use. Which it may be that you misunderstood my
question, thinking I am using named pipes (not so - have named pipes turned
off).
Thought is - Will named pipes offer a temporary solution to overcome the
resource limitation imposed by the WinSvr2003 R2 without the DTC turned on?
Dunno enough to guess whether there is something in it that will work.
BACKGROUND:
I currently use TCP/IP and aliasing and I suspect the linked servers use
that already to communicate.
When we access a view on a SQL 2000 server using SQL 2005 on another server
(both are WinSvr 2003 R2 64 bit).
There is a problem with the DTC (I did not mention this one - I am waiting
for a server reboot to fix it - http://support.microsoft.com/kb/329332 or
http://support.microsoft.com/?kbid=873160 The operation could not be
performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
distributed transaction. OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
ITransactionJoin::JoinTransaction returned 0x8004d00a]. [OLE/DB provider
returned message: New transaction cannot enlist in the specified transaction
coordinator. ]).
The one housing SQL 2000 does not yet have DTC setup for network access.
The situation does not allow us to reboot (short of an emergency of which
this is not - instead each view must be re-written to get around the resource
issue - usually just create a sub-query in place of the view).
Herein lies the problem: After rewriting a bunch of failing views we
discovered that if a view is altered and consumes more resources, the
borderline ones we use for data-warehousing archive information at night can
fail for no other reason than that - view times out - resource limit
reached... blah blah). I hate it when a job fails.
Regards,
Jamie
"TheSQLGuru" wrote:
> As a workaround, can you try using TCP\IP provider for linking?
> --
> Kevin G. Boles
> Indicium Resources, Inc.
> SQL Server MVP
> kgboles a earthlink dt net
>
> "thejamie" <thejamie@.discussions.microsoft.com> wrote in message
> news:A4DB5E7F-56F3-46AE-9858-0F67546B82ED@.microsoft.com...
>
>
|||Misread first post. My bad. I don't know that there is a way to cut DTC
out of the loop, regardless of what connection mechanism you are using. I
don't have any other suggestions for possible workarounds for your issue
either.
Kevin G. Boles
Indicium Resources, Inc.
SQL Server MVP
kgboles a earthlink dt net
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:AF702DC6-3A07-4D85-9713-8C5406099EED@.microsoft.com...[vbcol=seagreen]
>I think I may be misunderstanding. I'm unaware of TCP/IP configurations
> other than what I already use. Which it may be that you misunderstood my
> question, thinking I am using named pipes (not so - have named pipes
> turned
> off).
> Thought is - Will named pipes offer a temporary solution to overcome the
> resource limitation imposed by the WinSvr2003 R2 without the DTC turned
> on?
> Dunno enough to guess whether there is something in it that will work.
> BACKGROUND:
> I currently use TCP/IP and aliasing and I suspect the linked servers use
> that already to communicate.
> When we access a view on a SQL 2000 server using SQL 2005 on another
> server
> (both are WinSvr 2003 R2 64 bit).
> There is a problem with the DTC (I did not mention this one - I am waiting
> for a server reboot to fix it - http://support.microsoft.com/kb/329332 or
> http://support.microsoft.com/?kbid=873160 The operation could not be
> performed because the OLE DB provider 'SQLOLEDB' was unable to begin a
> distributed transaction. OLE DB error trace [OLE/DB Provider 'SQLOLEDB'
> ITransactionJoin::JoinTransaction returned 0x8004d00a]. [OLE/DB provider
> returned message: New transaction cannot enlist in the specified
> transaction
> coordinator. ]).
> The one housing SQL 2000 does not yet have DTC setup for network access.
> The situation does not allow us to reboot (short of an emergency of which
> this is not - instead each view must be re-written to get around the
> resource
> issue - usually just create a sub-query in place of the view).
> Herein lies the problem: After rewriting a bunch of failing views we
> discovered that if a view is altered and consumes more resources, the
> borderline ones we use for data-warehousing archive information at night
> can
> fail for no other reason than that - view times out - resource limit
> reached... blah blah). I hate it when a job fails.
>
> --
> Regards,
> Jamie
>
> "TheSQLGuru" wrote:
resource file 'msmdsrv.rll' for locale '1049' could not be loaded
Hi forum,
does anyone know the cause of this error message?
23-Mar-2007 16:03:50
Computer: <ComputerName>
Source: MSSQLServerOLAPService
Category: None
Type: Error
Event ID: 25
Description: The resource file 'msmdsrv.rll' for locale '1049' could not be loaded. Switching to US English (1033) if available.
Tia,
/Gert
There is no localized version for locale 1049, or it was not installed.|||Hello I'm with the same problem but from spanish(1034):
How can I solve it?
|||You need to install a version that includes the specific resource files for your locale. I'm not sure if one is available or not.resource file 'msmdsrv.rll' for locale '1049' could not be loaded
Hi forum,
does anyone know the cause of this error message?
23-Mar-2007 16:03:50
Computer: <ComputerName>
Source: MSSQLServerOLAPService
Category: None
Type: Error
Event ID: 25
Description: The resource file 'msmdsrv.rll' for locale '1049' could not be loaded. Switching to US English (1033) if available.
Tia,
/Gert
There is no localized version for locale 1049, or it was not installed.|||Hello I'm with the same problem but from spanish(1034):
How can I solve it?
|||You need to install a version that includes the specific resource files for your locale. I'm not sure if one is available or not.RESOLVED Re: SQL Server 7: Query fails with error 7607
It turned out that I had to reapply SP4 once I installed FTS over
a previously installed server. Now it works fine. Thanks for
your assistance.
Ernie Limperis wrote:
> John,
> Looks like I misspoke. The build number on the machine in question
> is 7.00.1063. The machine with 1094 is our production box and I
> have't tried running FTS on it yet (can't build the index during
> business hours, and anyhow nobody got around to installing FTS on
> that machine). I know it's hard to say, but do you think the issue
> would go away if I install the security patch on this machine?
>
> ohn Kane wrote:
>
>
==============================================
Ernie Limperis home 510-525-8801
ernie@.sonic.net cell 510-682-6373
==============================================
You're welcome, Ernie,
No, I don't think that just installing the post-SP4 security hotfix roll-up
would of resolved this issue, as hotfixes are specific and this one is
specific to security issues. However, this post-SP4 security hotfix roll-up
does prevent you from re-installing SP4 once the security hotfix is
installed.
I'm glad you were able to resolve this via my original recommendation and
that I asked you what exact build you were on and you provided the info
(@.@.version) is most important in resolving SQL FTS issues!
Regards,
John
"Ernie Limperis" <ernie@.dnai.com> wrote in message
news:#nwevpV4EHA.1976@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> It turned out that I had to reapply SP4 once I installed FTS over
> a previously installed server. Now it works fine. Thanks for
> your assistance.
> Ernie Limperis wrote:
most[vbcol=seagreen]
a[vbcol=seagreen]
had[vbcol=seagreen]
or[vbcol=seagreen]
security[vbcol=seagreen]
especially[vbcol=seagreen]
table[vbcol=seagreen]
'insurance')
>
> --
> ==============================================
> Ernie Limperis home 510-525-8801
> ernie@.sonic.net cell 510-682-6373
> ==============================================
>
sql
a previously installed server. Now it works fine. Thanks for
your assistance.
Ernie Limperis wrote:
> John,
> Looks like I misspoke. The build number on the machine in question
> is 7.00.1063. The machine with 1094 is our production box and I
> have't tried running FTS on it yet (can't build the index during
> business hours, and anyhow nobody got around to installing FTS on
> that machine). I know it's hard to say, but do you think the issue
> would go away if I install the security patch on this machine?
>
> ohn Kane wrote:
>
>
==============================================
Ernie Limperis home 510-525-8801
ernie@.sonic.net cell 510-682-6373
==============================================
You're welcome, Ernie,
No, I don't think that just installing the post-SP4 security hotfix roll-up
would of resolved this issue, as hotfixes are specific and this one is
specific to security issues. However, this post-SP4 security hotfix roll-up
does prevent you from re-installing SP4 once the security hotfix is
installed.
I'm glad you were able to resolve this via my original recommendation and
that I asked you what exact build you were on and you provided the info
(@.@.version) is most important in resolving SQL FTS issues!
Regards,
John
"Ernie Limperis" <ernie@.dnai.com> wrote in message
news:#nwevpV4EHA.1976@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> It turned out that I had to reapply SP4 once I installed FTS over
> a previously installed server. Now it works fine. Thanks for
> your assistance.
> Ernie Limperis wrote:
most[vbcol=seagreen]
a[vbcol=seagreen]
had[vbcol=seagreen]
or[vbcol=seagreen]
security[vbcol=seagreen]
especially[vbcol=seagreen]
table[vbcol=seagreen]
'insurance')
>
> --
> ==============================================
> Ernie Limperis home 510-525-8801
> ernie@.sonic.net cell 510-682-6373
> ==============================================
>
sql
RESOLVED - Help with SQL Query - "The multi-part identifier "alias field Name" co
Hi Everyone
This is the query and I am getting follwoing error message
This is the query and I am getting follwoing error message
"The multi-part identifier "InvDate.Account Reference" could not be bound."
SELECT MAX([DATE NOTE ADDED]) AS LASTDATE,By the way its SQL Server 2005 Environment.
CC.[COMPANY],
CC.[ACCOUNT REFERENCE],
INVDATE.[LASTORDERDATE]
FROM CUSTOMERCONTACTNOTES AS CCN,
(SELECT *
FROM CUSTOMER) AS CC,
(SELECT MAX([INVOICE DATE]) AS LASTORDERDATE,
[ACCOUNT REFERENCE]
FROM INVOICEDATA
GROUP BY [ACCOUNT REFERENCE]) AS INVDATE
WHERE CCN.[COMPANY] = CC.[COMPANY]
AND CC.[ACCOUNT REFERENCE] COLLATE SQL_LATIN1_GENERAL_CP1_CI_AS IN (SELECT DISTINCT ([ACCOUNT REFERENCE])
FROM INVOICEDATA)
AND CC.[ACCOUNT REFERENCE] COLLATE SQL_LATIN1_GENERAL_CP1_CI_AS = INVDATE.[ACCOUNT REFERENCE]
GROUP BY CC.[COMPANY],CC.[ACCOUNT REFERENCE]
ORDER BY CC.COMPANY ASC
Mitesh
Well how about getting rid of:
- (select * from customer) -- just use a simple join to customer
- get rid of the collate statements in your where clauses.
Also, you'll need to add INVDATE.[LASTORDERDATE] to your group by statement.
SELECT MAX([DATE NOTE ADDED]) AS LASTDATE,
CC.[COMPANY],
CC.[ACCOUNT REFERENCE],
INVDATE.[LASTORDERDATE]
FROM CUSTOMERCONTACTNOTES AS CCN,
CUSTOMER AS CC,
(SELECT MAX([INVOICE DATE]) AS LASTORDERDATE,
[ACCOUNT REFERENCE]
FROM INVOICEDATA
GROUP BY [ACCOUNT REFERENCE]) AS INVDATE
WHERE CCN.[COMPANY] = CC.[COMPANY]
AND CC.[ACCOUNT REFERENCE] IN (SELECT DISTINCT ([ACCOUNT REFERENCE]) FROM INVOICEDATA)
AND CC.[ACCOUNT REFERENCE] = INVDATE.[ACCOUNT REFERENCE]
GROUP BY CC.[COMPANY],CC.[ACCOUNT REFERENCE], INVDATE.[LASTORDERDATE]
ORDER BY CC.COMPANY ASC|||Thanks Phill,
Your solution was just spot on.
Just out of curosity, how do you read any SQL Query, for e.g. like mine and find what is wrong.
Mitesh|||Experience, I guess. When you work with it enough, you can just "read" SQL and understand what's going on.
I really don't think you need the "select distinct [account reference] from invoicedata" query in your where clause though. You already have a distinct list from the INVDATE query in your FROM statement. Your where clause should probably be:
WHERE CCN.[COMPANY] = CC.[COMPANY]
AND CC.[ACCOUNT REFERENCE] = INVDATE.[ACCOUNT REFERENCE]
Friday, March 23, 2012
Reset Report Manager
I've done something bad that prevents Report Manager from running. Every time I try to call it up in a browser, I get error messages complaining about a null object.
Is there a way to get the report manager to "start fresh"? For example, would deleting the entries in the catalog table do the trick.
Thanks for any help.
What exception do you see in the report server log file?|||The log shows:
<Header>
<Product>Microsoft SQL Server Reporting Services Version 9.00.1399.00</Product>
<Locale>en-US</Locale>
<TimeZone>Eastern Daylight Time</TimeZone>
<Path>C:\Program Files\Microsoft SQL Server\MSSQL.2\Reporting Services\LogFiles\ReportServerWebApp__04_18_2006_07_52_53.log</Path>
<SystemName>MERCURY</SystemName>
<OSName>Microsoft Windows NT 5.2.3790 Service Pack 1</OSName>
<OSVersion>5.2.3790.65536</OSVersion>
</Header>
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing ReportBuilderTrustLevel to '0' as specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing MaxActiveReqForOneUser to '20' requests(s) as specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing MaxScheduleWait to default value of '1' second(s) because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing DatabaseQueryTimeout to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing ProcessRecycleOptions to default value of '0' because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing RunningRequestsScavengerCycle to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing RunningRequestsDbCycle to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing RunningRequestsAge to default value of '30' second(s) because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing CleanupCycleMinutes to default value of '10' minute(s) because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing DailyCleanupMinuteOfDay to default value of '120' minutes since midnight because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing WatsonFlags to default value of '1064' because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing WatsonDumpOnExceptions to default value of 'Microsoft.ReportingServices.Diagnostics.Utilities.InternalCatalogException,Microsoft.ReportingServices.Modeling.InternalModelingException' because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing WatsonDumpExcludeIfContainsExceptions to default value of 'System.Data.SqlClient.SqlException,System.Threading.ThreadAbortException' because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing SecureConnectionLevel to default value of '1' because it was not specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing DisplayErrorLink to 'True' as specified in Configuration file.
w3wp!library!1!4/18/2006-07:52:54:: i INFO: Initializing WebServiceUseFileShareStorage to default value of 'False' because it was not specified in Configuration file.
w3wp!ui!1!4/18/2006-07:52:55:: Unhandled exception: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.ReportingServices.UI.GlobalApp.Application_AuthenticateRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I found my problem.
I had authentication mode set to "None" in web.config. As soon as I changed it to "Windows" the problem went away.
Reset Excel Destination for Error Logging
I am using sheets in an Excel spreadsheet to receive redirected error rows. The trouble is that it keeps appending the rows to the bottom of the sheet - even if I delete the rows in the spreadsheet. If I remove the spreadsheet all together then I need to set-up the Excel Desitnation Sheets again.
Each time I run the Control Flow I would like it to be removing old log entries and writing in the new ones.
There must be an easy way?
Unfortunately the Excel driver does not support anything like TRUNCATE TABLE. Even if you opened Excel and cleared the contents of those rows, the driver would still see them as "used" ... the only solution is to delete the rows themselves from within Excel. And you would want to check the range definition to make sure that you were in fact deleting all the rows in the range.
Of course the cleaner solution would be to drop and recreate the table. You could use an Execute SQL task for this purpose, and probably get one of the SSIS components to write the SQL for you to copy and paste in.
-Doug
Wednesday, March 21, 2012
Reserved Error importing Access 2003 Report into VS2005 Report Module, How do I troublesho
Hi,
I'm trying to Import an existing Access 2003 report into into an existing
VS2005 Report Project, I am getting the following error. Is there a way to
troubleshoot what is causing this error?
Importing reports from 'C:\db2.mdb'...
Error : An error occurred while the report Test Report Form was being
imported: Reserved ErrorWe ran across a few reports with this issue. I reviewed my notes but didn't
come up with anything.
I found this in a group:
2 From: Albert Yen [MSFT] - view profile
Date: Tues, Jul 26 2005 3:51 pm
Email: "Albert Yen [MSFT]" <albe...@.online.microsoft.com>
Groups: microsoft.public.sqlserver.reportingsvcs
Not yet ratedRating:
show options
Reply | Reply to Author | Forward | Print | Individual Message | Show
original | Report Abuse | Find messages by this author
The first error could be coming from Access. Could you try the following?
Open your database in Microsoft Access. Create a new Module and paste the
following code into it:
Sub Export()
Application.ExportXML ObjectType:=acExportReport, _
DataSource:="DailySales ", _
ImageTarget:=".", _
PresentationTarget:="DailySales .xsl", _
OtherFlags:=acPersistReportML
End Sub
Set the cursor at the beginning of the Sub and click the Run button. If
ExportXML succeeds, it should create a file called "DailySales_report.xml"
in your "My Documents" folder. If you can send the file to me, I'll look at
it. If ExportXML fails, then it's an Access problem. You could try the
Access newsgroups for help.
Albert Yen
SQL Server Reporting Services
Steve MunLeeuw
"Rob Dob" <robdob20012002@.yahoo.com> wrote in message
news:u8Pq0zJ7GHA.4708@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I'm trying to Import an existing Access 2003 report into into an existing
> VS2005 Report Project, I am getting the following error. Is there a way
> to troubleshoot what is causing this error?
> Importing reports from 'C:\db2.mdb'...
> Error : An error occurred while the report Test Report Form was being
> imported: Reserved Error
>
I'm trying to Import an existing Access 2003 report into into an existing
VS2005 Report Project, I am getting the following error. Is there a way to
troubleshoot what is causing this error?
Importing reports from 'C:\db2.mdb'...
Error : An error occurred while the report Test Report Form was being
imported: Reserved ErrorWe ran across a few reports with this issue. I reviewed my notes but didn't
come up with anything.
I found this in a group:
2 From: Albert Yen [MSFT] - view profile
Date: Tues, Jul 26 2005 3:51 pm
Email: "Albert Yen [MSFT]" <albe...@.online.microsoft.com>
Groups: microsoft.public.sqlserver.reportingsvcs
Not yet ratedRating:
show options
Reply | Reply to Author | Forward | Print | Individual Message | Show
original | Report Abuse | Find messages by this author
The first error could be coming from Access. Could you try the following?
Open your database in Microsoft Access. Create a new Module and paste the
following code into it:
Sub Export()
Application.ExportXML ObjectType:=acExportReport, _
DataSource:="DailySales ", _
ImageTarget:=".", _
PresentationTarget:="DailySales .xsl", _
OtherFlags:=acPersistReportML
End Sub
Set the cursor at the beginning of the Sub and click the Run button. If
ExportXML succeeds, it should create a file called "DailySales_report.xml"
in your "My Documents" folder. If you can send the file to me, I'll look at
it. If ExportXML fails, then it's an Access problem. You could try the
Access newsgroups for help.
Albert Yen
SQL Server Reporting Services
Steve MunLeeuw
"Rob Dob" <robdob20012002@.yahoo.com> wrote in message
news:u8Pq0zJ7GHA.4708@.TK2MSFTNGP05.phx.gbl...
> Hi,
> I'm trying to Import an existing Access 2003 report into into an existing
> VS2005 Report Project, I am getting the following error. Is there a way
> to troubleshoot what is causing this error?
> Importing reports from 'C:\db2.mdb'...
> Error : An error occurred while the report Test Report Form was being
> imported: Reserved Error
>
reserved character issue in create folder
When I try and create a folder using the following syntax:
folder/subfolder/anotherfolder
I get the following error
The item name is not valid. Item names cannot contain the following reserved
characters ;?:@.&=+$,\*<>|"/, and cannot consist exclusively of dots or spaces.
When checking the MSDN documentation for the ReportServices CreatFolder I
noticed it contains the following comment:
Folder names cannot be null, consist of empty strings, or contain the
following reserved characters:
: ? ; @. & = + $ , \ * > < | . "
The difference is the message my ReportServer is giving me includes the '/'
character, while the documentaion does not.
This is causing a great deal of pain with my deployment scripts and I can't
find any information on this issue.Hi
Generally, you need to create folders one level at a time.
folder
cd folder
then
subfolder
cd subfolder
then
anotherfolder
cd anotherfolder
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"DerrickBrown100" <DerrickBrown100@.discussions.microsoft.com> wrote in
message news:D7B14559-8330-453C-A86D-6E137D2AE287@.microsoft.com...
> When I try and create a folder using the following syntax:
> folder/subfolder/anotherfolder
> I get the following error
> The item name is not valid. Item names cannot contain the following
> reserved
> characters ;?:@.&=+$,\*<>|"/, and cannot consist exclusively of dots or
> spaces.
> When checking the MSDN documentation for the ReportServices CreatFolder I
> noticed it contains the following comment:
> Folder names cannot be null, consist of empty strings, or contain the
> following reserved characters:
> : ? ; @. & = + $ , \ * > < | . "
> The difference is the message my ReportServer is giving me includes the
> '/'
> character, while the documentaion does not.
> This is causing a great deal of pain with my deployment scripts and I
> can't
> find any information on this issue.
>|||Thanks for the reply. Perhaps a little more information regarding the
situation would help. I am currently working on a setup/deployment project
that will install our SRS reports on the target machine. I am using the web
service interface to set up the directory structure and deploy reports via
the CreateFolder method. Including the '/' in the CreateFolder call works on
every machine in the organization except my local developer installation.
Furthermore, the MSDN docs do not list the '/' as a reserved character.
However, my SRS installation returns an error listing the '/' as a reserved
character. I would assume this is a bug having to do with my configuration
and was wondering id anyone else had experienced this.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Generally, you need to create folders one level at a time.
> folder
> cd folder
> then
> subfolder
> cd subfolder
> then
> anotherfolder
> cd anotherfolder
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "DerrickBrown100" <DerrickBrown100@.discussions.microsoft.com> wrote in
> message news:D7B14559-8330-453C-A86D-6E137D2AE287@.microsoft.com...
> > When I try and create a folder using the following syntax:
> >
> > folder/subfolder/anotherfolder
> >
> > I get the following error
> > The item name is not valid. Item names cannot contain the following
> > reserved
> > characters ;?:@.&=+$,\*<>|"/, and cannot consist exclusively of dots or
> > spaces.
> >
> > When checking the MSDN documentation for the ReportServices CreatFolder I
> > noticed it contains the following comment:
> >
> > Folder names cannot be null, consist of empty strings, or contain the
> > following reserved characters:
> > : ? ; @. & = + $ , \ * > < | . "
> >
> > The difference is the message my ReportServer is giving me includes the
> > '/'
> > character, while the documentaion does not.
> >
> > This is causing a great deal of pain with my deployment scripts and I
> > can't
> > find any information on this issue.
> >
> >
>
>
folder/subfolder/anotherfolder
I get the following error
The item name is not valid. Item names cannot contain the following reserved
characters ;?:@.&=+$,\*<>|"/, and cannot consist exclusively of dots or spaces.
When checking the MSDN documentation for the ReportServices CreatFolder I
noticed it contains the following comment:
Folder names cannot be null, consist of empty strings, or contain the
following reserved characters:
: ? ; @. & = + $ , \ * > < | . "
The difference is the message my ReportServer is giving me includes the '/'
character, while the documentaion does not.
This is causing a great deal of pain with my deployment scripts and I can't
find any information on this issue.Hi
Generally, you need to create folders one level at a time.
folder
cd folder
then
subfolder
cd subfolder
then
anotherfolder
cd anotherfolder
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"DerrickBrown100" <DerrickBrown100@.discussions.microsoft.com> wrote in
message news:D7B14559-8330-453C-A86D-6E137D2AE287@.microsoft.com...
> When I try and create a folder using the following syntax:
> folder/subfolder/anotherfolder
> I get the following error
> The item name is not valid. Item names cannot contain the following
> reserved
> characters ;?:@.&=+$,\*<>|"/, and cannot consist exclusively of dots or
> spaces.
> When checking the MSDN documentation for the ReportServices CreatFolder I
> noticed it contains the following comment:
> Folder names cannot be null, consist of empty strings, or contain the
> following reserved characters:
> : ? ; @. & = + $ , \ * > < | . "
> The difference is the message my ReportServer is giving me includes the
> '/'
> character, while the documentaion does not.
> This is causing a great deal of pain with my deployment scripts and I
> can't
> find any information on this issue.
>|||Thanks for the reply. Perhaps a little more information regarding the
situation would help. I am currently working on a setup/deployment project
that will install our SRS reports on the target machine. I am using the web
service interface to set up the directory structure and deploy reports via
the CreateFolder method. Including the '/' in the CreateFolder call works on
every machine in the organization except my local developer installation.
Furthermore, the MSDN docs do not list the '/' as a reserved character.
However, my SRS installation returns an error listing the '/' as a reserved
character. I would assume this is a bug having to do with my configuration
and was wondering id anyone else had experienced this.
"Mike Epprecht (SQL MVP)" wrote:
> Hi
> Generally, you need to create folders one level at a time.
> folder
> cd folder
> then
> subfolder
> cd subfolder
> then
> anotherfolder
> cd anotherfolder
> Regards
> --
> Mike Epprecht, Microsoft SQL Server MVP
> Zurich, Switzerland
> IM: mike@.epprecht.net
> MVP Program: http://www.microsoft.com/mvp
> Blog: http://www.msmvps.com/epprecht/
> "DerrickBrown100" <DerrickBrown100@.discussions.microsoft.com> wrote in
> message news:D7B14559-8330-453C-A86D-6E137D2AE287@.microsoft.com...
> > When I try and create a folder using the following syntax:
> >
> > folder/subfolder/anotherfolder
> >
> > I get the following error
> > The item name is not valid. Item names cannot contain the following
> > reserved
> > characters ;?:@.&=+$,\*<>|"/, and cannot consist exclusively of dots or
> > spaces.
> >
> > When checking the MSDN documentation for the ReportServices CreatFolder I
> > noticed it contains the following comment:
> >
> > Folder names cannot be null, consist of empty strings, or contain the
> > following reserved characters:
> > : ? ; @. & = + $ , \ * > < | . "
> >
> > The difference is the message my ReportServer is giving me includes the
> > '/'
> > character, while the documentaion does not.
> >
> > This is causing a great deal of pain with my deployment scripts and I
> > can't
> > find any information on this issue.
> >
> >
>
>
Tuesday, March 20, 2012
Re-raising error
In a stored procedure I usually check @.@.ERROR after every
INSERT/UPDATE/DELETE. If any error, then I exit SP with this error
code. A client application does not receive much information
with this code, so it displays a message like "Cannot insert/update record.
Error : NNN".
Is there a way to get more detailed information about an error?
RAISERROR only throws user-defined errors. Any ideas?"Tumurbaatar S." <spam_tumur@.magicnet.mn> wrote in message
news:u6%23Wmxd8FHA.3132@.TK2MSFTNGP12.phx.gbl...
> In a stored procedure I usually check @.@.ERROR after every
> INSERT/UPDATE/DELETE. If any error, then I exit SP with this error
> code. A client application does not receive much information
> with this code, so it displays a message like "Cannot insert/update
> record. Error : NNN".
> Is there a way to get more detailed information about an error?
> RAISERROR only throws user-defined errors. Any ideas?
>
Unless you use TSQL TRY/CATCH the client will recieve both the original
error and the stored procedure return code. Different client libraries
interpret this data differently, but most have a way to grab the error.
David|||Is your client application SQLServer or something else (dotnet, java etc)?
If SQL then @.@.error is fine unless you want to catch the specific error from
sysmessages. I only ever use raiserror(@.text,1,1) for triggers and i don't
use triggers so I don't really use it.
If it is an external App and you are not a GOTOless programmer then try
something like below then just call the entries from the log table in the
external App:
If @.@.ERROR <> 0 or @.@.ROWCOUNT <= 0
begin
select @.text = 'Error -50: Could not update TableAdata for w
.'
select @.result = -50
GOTO ERROR_POINT
end
ERROR_POINT:
PRINT 'ERROR_POINT'
GOTO FINISH
FINISH:
select @.resultText = 'RoutineName: ' + @.text + ' from User ' + @.pWho + ' at
' + convert(varchar(15),getdate(),3) + ' ' + convert(varchar(15),getdate(),1
4)
INSERT INTO log VALUES (@.resultText, 'RoutineName', getdate(), 'Y')
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
SET NOCOUNT OFF
GO|||No pun intended, but please explain how this one works.
There must be something missing from the sample you posted.
All statements will be executed - even if there is no error and the rowcount
is above 0, and in such a case a null value (or an unexpected one) will be
inserted into the log.
Do you actually use this in your production code?
ML|||Thank you!
But you are both talking about SQL2005? If I'm not mistaken,
SQL2000 does not support TRY/CATCH exception handling. And that
is only reason why I asked for how to re-raise (read "rethrow") an error.
If there was try/catch handling in SQL2000, I had no problem.|||"Tumurbaatar S." <spam_tumur@.magicnet.mn> wrote in message
news:%235tAGhh8FHA.3984@.TK2MSFTNGP11.phx.gbl...
> Thank you!
> But you are both talking about SQL2005? If I'm not mistaken,
> SQL2000 does not support TRY/CATCH exception handling. And that
> is only reason why I asked for how to re-raise (read "rethrow") an error.
> If there was try/catch handling in SQL2000, I had no problem.
>
IN SQL 2000 there is no way to prevent the error message from propagating to
the client. If the client is using, for instance, .NET the calling code
will get a SqlException. Only in SQL 2005 is there a way to stop the error
from going to the client (CATCH), and so only there is there any need to
"rethrow" the error in SQL Server.
David|||> IN SQL 2000 there is no way to prevent the error message from propagating
> to the client. If the client is using, for instance, .NET the calling
> code will get a SqlException.
But how does a client receive an error? For example, a SP executes
INSERT that fails due to some constraint violation:
INSERT ...
IF @.@.ERROR <> 0
...
What happens in this case? SP execution stops before IF @.@.ERROR,
exits with an error notification and the client engine receives a standard
SQL error. Or SQL server remembers this error, the SP continues processing
and when SP exits normally (i.e. RETURN @.some_value) the client engine
receives
this return code (@.some_value), but also it receives the previously saved
error too?|||"Tumurbaatar S." <spam_tumur@.magicnet.mn> wrote in message
news:e2m$$tq8FHA.472@.TK2MSFTNGP15.phx.gbl...
> But how does a client receive an error? For example, a SP executes
> INSERT that fails due to some constraint violation:
> INSERT ...
> IF @.@.ERROR <> 0
> ...
> What happens in this case? SP execution stops before IF @.@.ERROR,
> exits with an error notification and the client engine receives a standard
> SQL error. Or SQL server remembers this error, the SP continues processing
> and when SP exits normally (i.e. RETURN @.some_value) the client engine
> receives
> this return code (@.some_value), but also it receives the previously saved
> error too?
Sort of, yes. The client gets the return code and any errors which occured.
Most client libraries don't expose both through the API, however. If an
error occurs, you will likely not get a return code from the procedure.
David|||Many thanks!
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:e$Zbolw8FHA.740@.TK2MSFTNGP11.phx.gbl...
> "Tumurbaatar S." <spam_tumur@.magicnet.mn> wrote in message
> news:e2m$$tq8FHA.472@.TK2MSFTNGP15.phx.gbl...
> Sort of, yes. The client gets the return code and any errors which
> occured. Most client libraries don't expose both through the API, however.
> If an error occurs, you will likely not get a return code from the
> procedure.
> David
>
>
INSERT/UPDATE/DELETE. If any error, then I exit SP with this error
code. A client application does not receive much information
with this code, so it displays a message like "Cannot insert/update record.
Error : NNN".
Is there a way to get more detailed information about an error?
RAISERROR only throws user-defined errors. Any ideas?"Tumurbaatar S." <spam_tumur@.magicnet.mn> wrote in message
news:u6%23Wmxd8FHA.3132@.TK2MSFTNGP12.phx.gbl...
> In a stored procedure I usually check @.@.ERROR after every
> INSERT/UPDATE/DELETE. If any error, then I exit SP with this error
> code. A client application does not receive much information
> with this code, so it displays a message like "Cannot insert/update
> record. Error : NNN".
> Is there a way to get more detailed information about an error?
> RAISERROR only throws user-defined errors. Any ideas?
>
Unless you use TSQL TRY/CATCH the client will recieve both the original
error and the stored procedure return code. Different client libraries
interpret this data differently, but most have a way to grab the error.
David|||Is your client application SQLServer or something else (dotnet, java etc)?
If SQL then @.@.error is fine unless you want to catch the specific error from
sysmessages. I only ever use raiserror(@.text,1,1) for triggers and i don't
use triggers so I don't really use it.
If it is an external App and you are not a GOTOless programmer then try
something like below then just call the entries from the log table in the
external App:
If @.@.ERROR <> 0 or @.@.ROWCOUNT <= 0
begin
select @.text = 'Error -50: Could not update TableAdata for w
.'select @.result = -50
GOTO ERROR_POINT
end
ERROR_POINT:
PRINT 'ERROR_POINT'
GOTO FINISH
FINISH:
select @.resultText = 'RoutineName: ' + @.text + ' from User ' + @.pWho + ' at
' + convert(varchar(15),getdate(),3) + ' ' + convert(varchar(15),getdate(),1
4)
INSERT INTO log VALUES (@.resultText, 'RoutineName', getdate(), 'Y')
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
SET NOCOUNT OFF
GO|||No pun intended, but please explain how this one works.
There must be something missing from the sample you posted.
All statements will be executed - even if there is no error and the rowcount
is above 0, and in such a case a null value (or an unexpected one) will be
inserted into the log.
Do you actually use this in your production code?
ML|||Thank you!
But you are both talking about SQL2005? If I'm not mistaken,
SQL2000 does not support TRY/CATCH exception handling. And that
is only reason why I asked for how to re-raise (read "rethrow") an error.
If there was try/catch handling in SQL2000, I had no problem.|||"Tumurbaatar S." <spam_tumur@.magicnet.mn> wrote in message
news:%235tAGhh8FHA.3984@.TK2MSFTNGP11.phx.gbl...
> Thank you!
> But you are both talking about SQL2005? If I'm not mistaken,
> SQL2000 does not support TRY/CATCH exception handling. And that
> is only reason why I asked for how to re-raise (read "rethrow") an error.
> If there was try/catch handling in SQL2000, I had no problem.
>
IN SQL 2000 there is no way to prevent the error message from propagating to
the client. If the client is using, for instance, .NET the calling code
will get a SqlException. Only in SQL 2005 is there a way to stop the error
from going to the client (CATCH), and so only there is there any need to
"rethrow" the error in SQL Server.
David|||> IN SQL 2000 there is no way to prevent the error message from propagating
> to the client. If the client is using, for instance, .NET the calling
> code will get a SqlException.
But how does a client receive an error? For example, a SP executes
INSERT that fails due to some constraint violation:
INSERT ...
IF @.@.ERROR <> 0
...
What happens in this case? SP execution stops before IF @.@.ERROR,
exits with an error notification and the client engine receives a standard
SQL error. Or SQL server remembers this error, the SP continues processing
and when SP exits normally (i.e. RETURN @.some_value) the client engine
receives
this return code (@.some_value), but also it receives the previously saved
error too?|||"Tumurbaatar S." <spam_tumur@.magicnet.mn> wrote in message
news:e2m$$tq8FHA.472@.TK2MSFTNGP15.phx.gbl...
> But how does a client receive an error? For example, a SP executes
> INSERT that fails due to some constraint violation:
> INSERT ...
> IF @.@.ERROR <> 0
> ...
> What happens in this case? SP execution stops before IF @.@.ERROR,
> exits with an error notification and the client engine receives a standard
> SQL error. Or SQL server remembers this error, the SP continues processing
> and when SP exits normally (i.e. RETURN @.some_value) the client engine
> receives
> this return code (@.some_value), but also it receives the previously saved
> error too?
Sort of, yes. The client gets the return code and any errors which occured.
Most client libraries don't expose both through the API, however. If an
error occurs, you will likely not get a return code from the procedure.
David|||Many thanks!
"David Browne" <davidbaxterbrowne no potted meat@.hotmail.com> wrote in
message news:e$Zbolw8FHA.740@.TK2MSFTNGP11.phx.gbl...
> "Tumurbaatar S." <spam_tumur@.magicnet.mn> wrote in message
> news:e2m$$tq8FHA.472@.TK2MSFTNGP15.phx.gbl...
> Sort of, yes. The client gets the return code and any errors which
> occured. Most client libraries don't expose both through the API, however.
> If an error occurs, you will likely not get a return code from the
> procedure.
> David
>
>
required filter on Ad-hoc reports
When using the Report Builder in SQL 2005 some larger reports give me an
error message = filter required.
I assume this is somthing is a setting somwhere but where?
--
Peter
Peter.freeborn@.halliburton.comGo to Filter from the menu bar and select a column for the filter, you can
have prompt as well for the user to select the values.
I think, the Adhoc is designed in such a way that you need to set a filter,
because without filter it will be a long running query and will have great
effects on various things.
Amarnath
"Peter" wrote:
> When using the Report Builder in SQL 2005 some larger reports give me an
> error message = filter required.
> I assume this is somthing is a setting somwhere but where?
> --
> Peter
> Peter.freeborn@.halliburton.com
error message = filter required.
I assume this is somthing is a setting somwhere but where?
--
Peter
Peter.freeborn@.halliburton.comGo to Filter from the menu bar and select a column for the filter, you can
have prompt as well for the user to select the values.
I think, the Adhoc is designed in such a way that you need to set a filter,
because without filter it will be a long running query and will have great
effects on various things.
Amarnath
"Peter" wrote:
> When using the Report Builder in SQL 2005 some larger reports give me an
> error message = filter required.
> I assume this is somthing is a setting somwhere but where?
> --
> Peter
> Peter.freeborn@.halliburton.com
Monday, March 12, 2012
Required .Net error during installation....
Hello friends, I have been trying to install SQL Server2005 but I can't. I have .Net framwork 2.0 on my computer. At the end of installation at Reporting Services the following error occurs.
Error: The required version of .Net framwork is not installed.
So first I installed .Net framwork SDK, the problem was same. After that I install .Net framwork 3.0 direct from microsoft but all in vain.
Now I need help about which of the .Net framwork must be installed on computer before installing SQL Server2005.
Thaks a lot..
if you want to setup a RS Server you seem to not have the ASP.NET component registered on the server. Change to the C:\Windows\Microsoft.NET\Framework\v2.0.50727 directory and use the aspnet_regiis.exe -i command for registering the asp.Net extensions to your web server.
If this does not work try the following: You will need to have the .NET 2.0 Framework installed on the Server. This is normally done through the prerequisites pages. Open the Setup of SQL Server 2005 after deleting all instances of the .NET Framework which could be found by the installer. then try to install RS Server again.
HTH, Jens K. Suessmeyer.
http://www.sqlserver2005.de
|||Hey, I have did this aspnet_regiis.exe -i . Its not worked.
But I want to say one thing that I have already installed Visual Studio 2005 Professional Edition, .Net framwork v2.0.50727 and .Net framwork v3.0 on the same machine...
Now I am trying to install SQL Server2005 too. After very first installation of SQL Server its worked every thing, I made data base on the installed server. And after rebooting my system next day Server is not running. I tried to run all the server services manually but its worked. I used Sql server management studio too, all in vain...
What can I do?
Request to IIS failed
hi
i having having an error request to IIs failed evertime.i have even uinstall my firewall but it is still not wking.here is my sql server diagnotics
SQL Server Mobile Server Agent Diagnostics
2006/07/15 15:57:03
i dont kno how to solve the database reconciler.i am not able to synchronize.my coding is as follows:
Dim repl As New SqlCeReplication()
Dim strpath As String
strpath = "\Program Files\Flight_PPC\SQLFlight.sdf"
repl.InternetUrl = "http://nisha/SQLMobile/sqlcesa30.dll"
repl.Publisher = "NISHA"
repl.PublisherDatabase = "flightDatabase"
repl.PublisherSecurityMode = SecurityType.DBAuthentication
repl.PublisherLogin = "sa"
repl.PublisherPassword = "pradha"
repl.Publication = "SQLMobile"
repl.Subscriber = "SQLMobile"
repl.SubscriberConnectionString = "Data Source=" + strpath
Try
repl.Synchronize()
Catch err As SqlCeException
MessageBox.Show(err.ToString)
End Try
Try increasing your default timeout value on the IIS server and also the timeout from the client and see if that helps.|||Hi, I'm having the same problem...The timeout of my IIS is set to 120 seconds, so I don't think that is the problem. I have the same exact display page as posted above. Any other idea?
Thanks
|||
Hi, I still have the same issue. Any other suggestions will be appreciated. Thanks.
|||Can you post the error message? You can see the log within "Replication Monitor". Open up SQL Server Managment Studio. Right click on "Replication" and choose "Launch Replication Monitor".
Request to IIS failed
hi
i having having an error request to IIs failed evertime.i have even uinstall my firewall but it is still not wking.here is my sql server diagnotics
SQL Server Mobile Server Agent Diagnostics
2006/07/15 15:57:03
i dont kno how to solve the database reconciler.i am not able to synchronize.my coding is as follows:
Dim repl AsNew SqlCeReplication()
Dim strpath AsString
strpath = "\Program Files\Flight_PPC\SQLFlight.sdf"
repl.InternetUrl = "http://nisha/SQLMobile/sqlcesa30.dll"
repl.Publisher = "NISHA"
repl.PublisherDatabase = "flightDatabase"
repl.PublisherSecurityMode = SecurityType.DBAuthentication
repl.PublisherLogin = "sa"
repl.PublisherPassword = "pradha"
repl.Publication = "SQLMobile"
repl.Subscriber = "SQLMobile"
repl.SubscriberConnectionString = "Data Source=" + strpath
Try
repl.Synchronize()
Catch err As SqlCeException
MessageBox.Show(err.ToString)
EndTry
Try increasing your default timeout value on the IIS server and also the timeout from the client and see if that helps.|||Hi, I'm having the same problem...The timeout of my IIS is set to 120 seconds, so I don't think that is the problem. I have the same exact display page as posted above. Any other idea?
Thanks
|||
Hi, I still have the same issue. Any other suggestions will be appreciated. Thanks.
|||Can you post the error message? You can see the log within "Replication Monitor". Open up SQL Server Managment Studio. Right click on "Replication" and choose "Launch Replication Monitor".
Request to IIS failed
hi
i having having an error request to IIs failed evertime.i have even uinstall my firewall but it is still not wking.here is my sql server diagnotics
SQL Server Mobile Server Agent Diagnostics
2006/07/15 15:57:03
i dont kno how to solve the database reconciler.i am not able to synchronize.my coding is as follows:
Dim repl As New SqlCeReplication()
Dim strpath As String
strpath = "\Program Files\Flight_PPC\SQLFlight.sdf"
repl.InternetUrl = "http://nisha/SQLMobile/sqlcesa30.dll"
repl.Publisher = "NISHA"
repl.PublisherDatabase = "flightDatabase"
repl.PublisherSecurityMode = SecurityType.DBAuthentication
repl.PublisherLogin = "sa"
repl.PublisherPassword = "pradha"
repl.Publication = "SQLMobile"
repl.Subscriber = "SQLMobile"
repl.SubscriberConnectionString = "Data Source=" + strpath
Try
repl.Synchronize()
Catch err As SqlCeException
MessageBox.Show(err.ToString)
End Try
Try increasing your default timeout value on the IIS server and also the timeout from the client and see if that helps.|||Hi, I'm having the same problem...
The timeout of my IIS is set to 120 seconds, so I don't think that is the problem. I have the same exact display page as posted above. Any other idea?
Thanks|||
Hi, I still have the same issue. Any other suggestions will be appreciated. Thanks.
|||Can you post the error message? You can see the log within "Replication Monitor". Open up SQL Server Managment Studio. Right click on "Replication" and choose "Launch Replication Monitor".
Friday, March 9, 2012
Request for confirmation: This bug is fixed
Hello World,
One of our customers keeps getting the following error:
ODBC error code: -1
Net library error code: 2746x (10054)
SQLState: 01000
Description: ConnectionWrite(send())
I have looked up on the Microsoft web pages and have found:
http://support.microsoft.com/kb/q303120/
The description on this page states that this bug was fixed with SQL
Server 2000, service pack 2, so I asked the customer about the server
version number of his SQL Server 2000.
He has 8.00.818 (and lightweight pooling to default, which is off).
Accorind to the SQL Server 2000, service pack 3 description, an
installed SP3 has number 8.00.760.
Due to this circumstances I suppose our customer has a fixed version of
SQL Server 2000 and the problem is located somewhere else. Am I right?
Thanks for your help and best regards
Andreas
--
Andreas Tscharner andreas.tscharner@.metromec.ch
---
Das Denken eines Programmierers ist stets logisch (IF 1=2 THEN CALL
MainProgram), immer strukturiert und von keinerlei Vorurteilen
beeinträchtigt (ON Hunger GOSUB Aldi ELSE RETURN).
-- aus Murphy's Computergesetzen8.00.818 is the version number for the MS03-031 security patch. It was released after SP3a.
/risun
>--Original Message--
>Hello World,
>One of our customers keeps getting the following error:
>ODBC error code: -1
>Net library error code: 2746x (10054)
>SQLState: 01000
>Description: ConnectionWrite(send())
>I have looked up on the Microsoft web pages and have found:
>http://support.microsoft.com/kb/q303120/
>The description on this page states that this bug was fixed with SQL >Server 2000, service pack 2, so I asked the customer about the server >version number of his SQL Server 2000.
>He has 8.00.818 (and lightweight pooling to default, which is off). >Accorind to the SQL Server 2000, service pack 3 description, an >installed SP3 has number 8.00.760.
>Due to this circumstances I suppose our customer has a fixed version of >SQL Server 2000 and the problem is located somewhere else. Am I right?
>Thanks for your help and best regards
> Andreas
>-- >Andreas Tscharner andreas.tscharner@.metromec.ch
>----
--
>Das Denken eines Programmierers ist stets logisch (IF 1=3D2 THEN CALL
>MainProgram), immer strukturiert und von keinerlei Vorurteilen
>beeintr=E4chtigt (ON Hunger GOSUB Aldi ELSE RETURN).
> -- aus Murphy's Computergesetzen
>.
>|||Anthony,
Please stop confusing people by referring to build 817 (or 818 or 819
or MS03-031) as the "Slammer Worm build." This has nothing to do with
Slammer. As I've already pointed out, and as you can verify by reading
the security bulletins, MS03-031 addresses three post-Slammer
vulnerabilities. Like all Microsoft hotfixes, it is cumulative, but it
is definitely not the "Slammer Worm build," and it was released long
after the patch and service pack addressing the Slammer vulnerability
were released.
SK
AnthonyThomas wrote:
>Actually, 817 is the MS03-031 Slammer Worm build. 818 fixes an error MS03-031 introduced into the DTSGUI.dll and build 819 fixes a SQLEM password error introduced by the 818 fix. You should have build 819 to have all the tools fixed.
>Also, there have been three other publicly available hot fixes since then, 839, 859, and the latest, 879.
>Sincerely,
>
>Anthony Thomas
>
>|||Thanks for clearing this up, Anthony!
SK
AnthonyThomas wrote:
>My apologies to everyone. You, of course, are absolutely right. The Sapphire/Slammer Worm attacked Jan. 25, 2003, but the patches were available the prior summer but had not been applied by many. Obviously, MS03-031 was deployed until later 2003. Both deal with protocol hijacking and buffer overrun issues and, since we had been applying SP3, then shortly thereafter, SP3a, this seemed like the proactive release.
>The confusion was entirely my own.
>Sincerely,
>
>Anthony Thomas
>
>
One of our customers keeps getting the following error:
ODBC error code: -1
Net library error code: 2746x (10054)
SQLState: 01000
Description: ConnectionWrite(send())
I have looked up on the Microsoft web pages and have found:
http://support.microsoft.com/kb/q303120/
The description on this page states that this bug was fixed with SQL
Server 2000, service pack 2, so I asked the customer about the server
version number of his SQL Server 2000.
He has 8.00.818 (and lightweight pooling to default, which is off).
Accorind to the SQL Server 2000, service pack 3 description, an
installed SP3 has number 8.00.760.
Due to this circumstances I suppose our customer has a fixed version of
SQL Server 2000 and the problem is located somewhere else. Am I right?
Thanks for your help and best regards
Andreas
--
Andreas Tscharner andreas.tscharner@.metromec.ch
---
Das Denken eines Programmierers ist stets logisch (IF 1=2 THEN CALL
MainProgram), immer strukturiert und von keinerlei Vorurteilen
beeinträchtigt (ON Hunger GOSUB Aldi ELSE RETURN).
-- aus Murphy's Computergesetzen8.00.818 is the version number for the MS03-031 security patch. It was released after SP3a.
/risun
>--Original Message--
>Hello World,
>One of our customers keeps getting the following error:
>ODBC error code: -1
>Net library error code: 2746x (10054)
>SQLState: 01000
>Description: ConnectionWrite(send())
>I have looked up on the Microsoft web pages and have found:
>http://support.microsoft.com/kb/q303120/
>The description on this page states that this bug was fixed with SQL >Server 2000, service pack 2, so I asked the customer about the server >version number of his SQL Server 2000.
>He has 8.00.818 (and lightweight pooling to default, which is off). >Accorind to the SQL Server 2000, service pack 3 description, an >installed SP3 has number 8.00.760.
>Due to this circumstances I suppose our customer has a fixed version of >SQL Server 2000 and the problem is located somewhere else. Am I right?
>Thanks for your help and best regards
> Andreas
>-- >Andreas Tscharner andreas.tscharner@.metromec.ch
>----
--
>Das Denken eines Programmierers ist stets logisch (IF 1=3D2 THEN CALL
>MainProgram), immer strukturiert und von keinerlei Vorurteilen
>beeintr=E4chtigt (ON Hunger GOSUB Aldi ELSE RETURN).
> -- aus Murphy's Computergesetzen
>.
>|||Anthony,
Please stop confusing people by referring to build 817 (or 818 or 819
or MS03-031) as the "Slammer Worm build." This has nothing to do with
Slammer. As I've already pointed out, and as you can verify by reading
the security bulletins, MS03-031 addresses three post-Slammer
vulnerabilities. Like all Microsoft hotfixes, it is cumulative, but it
is definitely not the "Slammer Worm build," and it was released long
after the patch and service pack addressing the Slammer vulnerability
were released.
SK
AnthonyThomas wrote:
>Actually, 817 is the MS03-031 Slammer Worm build. 818 fixes an error MS03-031 introduced into the DTSGUI.dll and build 819 fixes a SQLEM password error introduced by the 818 fix. You should have build 819 to have all the tools fixed.
>Also, there have been three other publicly available hot fixes since then, 839, 859, and the latest, 879.
>Sincerely,
>
>Anthony Thomas
>
>|||Thanks for clearing this up, Anthony!
SK
AnthonyThomas wrote:
>My apologies to everyone. You, of course, are absolutely right. The Sapphire/Slammer Worm attacked Jan. 25, 2003, but the patches were available the prior summer but had not been applied by many. Obviously, MS03-031 was deployed until later 2003. Both deal with protocol hijacking and buffer overrun issues and, since we had been applying SP3, then shortly thereafter, SP3a, this seemed like the proactive release.
>The confusion was entirely my own.
>Sincerely,
>
>Anthony Thomas
>
>
Wednesday, March 7, 2012
Republisher (publishing subscriber) merge replication
Hi,
I am trying to have a republisher run with Merge replication, but am getting error messages anytime I try to publish to the third tier.
Any suggestions on where I can find more info?
Thanks
Wil
I ran into touble once trying that until I set the subscriber type
(sp_AddMergeSubscription) to Global. You might want to check your setting.
Paul
"Wil" <wil@.canoemail.com> wrote in message
news:258CA56C-2CE7-4531-8998-704C698E6DA3@.microsoft.com...
> Hi,
> I am trying to have a republisher run with Merge replication, but am
getting error messages anytime I try to publish to the third tier.
> Any suggestions on where I can find more info?
> Thanks
> Wil
|||what is your error message?
"Wil" <wil@.canoemail.com> wrote in message
news:258CA56C-2CE7-4531-8998-704C698E6DA3@.microsoft.com...
> Hi,
> I am trying to have a republisher run with Merge replication, but am
getting error messages anytime I try to publish to the third tier.
> Any suggestions on where I can find more info?
> Thanks
> Wil
I am trying to have a republisher run with Merge replication, but am getting error messages anytime I try to publish to the third tier.
Any suggestions on where I can find more info?
Thanks
Wil
I ran into touble once trying that until I set the subscriber type
(sp_AddMergeSubscription) to Global. You might want to check your setting.
Paul
"Wil" <wil@.canoemail.com> wrote in message
news:258CA56C-2CE7-4531-8998-704C698E6DA3@.microsoft.com...
> Hi,
> I am trying to have a republisher run with Merge replication, but am
getting error messages anytime I try to publish to the third tier.
> Any suggestions on where I can find more info?
> Thanks
> Wil
|||what is your error message?
"Wil" <wil@.canoemail.com> wrote in message
news:258CA56C-2CE7-4531-8998-704C698E6DA3@.microsoft.com...
> Hi,
> I am trying to have a republisher run with Merge replication, but am
getting error messages anytime I try to publish to the third tier.
> Any suggestions on where I can find more info?
> Thanks
> Wil
reprot subscription error
1).I got an error:
subscription cannot be created because the credentials used to run the
report are not stored, the report is using a user-defined parameter value...
However, can I solve this issue.
2). Is there any step by step guide to configure subscription.
ThanksThis is not complaining about Parameters, but about the data source... Open
the data source (on the report server) that this report uses, and select the
box , credentials stored securely on the server... then choose whichever
suboption suites you..
When a subscription is run, no user is running the report, instead the
server is running the report, so the login has to be stored. The server will
then use that login to run the subscription.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"qjlee" <qjlee@.discussions.microsoft.com> wrote in message
news:24A30193-13D9-41E9-8F48-AA572D4101D0@.microsoft.com...
> 1).I got an error:
> subscription cannot be created because the credentials used to run the
> report are not stored, the report is using a user-defined parameter
> value...
> However, can I solve this issue.
> 2). Is there any step by step guide to configure subscription.
> Thanks
>
subscription cannot be created because the credentials used to run the
report are not stored, the report is using a user-defined parameter value...
However, can I solve this issue.
2). Is there any step by step guide to configure subscription.
ThanksThis is not complaining about Parameters, but about the data source... Open
the data source (on the report server) that this report uses, and select the
box , credentials stored securely on the server... then choose whichever
suboption suites you..
When a subscription is run, no user is running the report, instead the
server is running the report, so the login has to be stored. The server will
then use that login to run the subscription.
--
Wayne Snyder MCDBA, SQL Server MVP
Mariner, Charlotte, NC
(Please respond only to the newsgroup.)
I support the Professional Association for SQL Server ( PASS) and it's
community of SQL Professionals.
"qjlee" <qjlee@.discussions.microsoft.com> wrote in message
news:24A30193-13D9-41E9-8F48-AA572D4101D0@.microsoft.com...
> 1).I got an error:
> subscription cannot be created because the credentials used to run the
> report are not stored, the report is using a user-defined parameter
> value...
> However, can I solve this issue.
> 2). Is there any step by step guide to configure subscription.
> Thanks
>
Reposting: Database Version Issue
I just installed SP2 for 2005 standard edition and am getting the following
error when trying to use report server:
"The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
version is 'C.0.8.43'. To continue, update the version of the report server
database and verify access rights. (rsInvalidReportServerDatabase)"
When I go into Reporting service configuration tool, the update button
returns the following:
"The database version matches your Reporting services installation"
and the database version is reported as 'C.0.8.54'.
this is critical and I need to get this up and running again. Any ideas?
--
John Cleveland
Network Manager
Urban systems LtdHave you installed any SQL service packs BEFORE adding other parts
like 'reporting services'
Also, there was a critical patch sent through windows update that
updates SQL server. Not sure if that is causing you problems.
On Apr 13, 1:16 am, John Cleveland
<JohnClevel...@.discussions.microsoft.com> wrote:
> I just installed SP2 for 2005 standard edition and am getting the following
> error when trying to use report server:
> "The version of the report server database is either in a format that is not
> valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> version is 'C.0.8.43'. To continue, update the version of the report server
> database and verify access rights. (rsInvalidReportServerDatabase)"
> When I go into Reporting service configuration tool, the update button
> returns the following:
> "The database version matches your Reporting services installation"
> and the database version is reported as 'C.0.8.54'.
> this is critical and I need to get this up and running again. Any ideas?
> --
> John Cleveland
> Network Manager
> Urban systems Ltd|||SP1 was already installed. reporting services was installed pre sp1.
I've narrowed down the sequence of events that lead to this issue. It seems
there was a reporting services update that was installed without my knowledge
that was intended for sp2 installs. SP2 wasn't installed yet. even though
sp2 is now installed, i still get the error message listed previously.
--
John Cleveland
Network Manager
Urban systems Ltd
"gommo" wrote:
> Have you installed any SQL service packs BEFORE adding other parts
> like 'reporting services'
> Also, there was a critical patch sent through windows update that
> updates SQL server. Not sure if that is causing you problems.
> On Apr 13, 1:16 am, John Cleveland
> <JohnClevel...@.discussions.microsoft.com> wrote:
> > I just installed SP2 for 2005 standard edition and am getting the following
> > error when trying to use report server:
> >
> > "The version of the report server database is either in a format that is not
> > valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> > version is 'C.0.8.43'. To continue, update the version of the report server
> > database and verify access rights. (rsInvalidReportServerDatabase)"
> >
> > When I go into Reporting service configuration tool, the update button
> > returns the following:
> >
> > "The database version matches your Reporting services installation"
> >
> > and the database version is reported as 'C.0.8.54'.
> >
> > this is critical and I need to get this up and running again. Any ideas?
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
>
>|||Is there a possibility that you actually have two different db's and your
reportserver instance is pointed at the "wrong" one frm the POV of the one
that your web application thinks it should connect to?
This might have happened if the person applying the update is not the
administrator of the box. See
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213
It can also happen if you apply the update in the wrong identity, even if
you are an administrator (I know that from personal experience <sigh> FWIW
the ReportServer database has a sprocwhere this is hard coded. I kid you
not. I think it gets adjusted during upgrades with a file called
catalog.sql. )
Short version of the fix described in that thread: you have to stop IIS and
RS and copy the files that were truly upgraded to the correct location --
but you should probably read the thread.
HTH,
>L<
"John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
news:C797E3E5-38CA-4547-AD46-2215A50529A4@.microsoft.com...
>I just installed SP2 for 2005 standard edition and am getting the following
> error when trying to use report server:
> "The version of the report server database is either in a format that is
> not
> valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> version is 'C.0.8.43'. To continue, update the version of the report
> server
> database and verify access rights. (rsInvalidReportServerDatabase)"
> When I go into Reporting service configuration tool, the update button
> returns the following:
> "The database version matches your Reporting services installation"
> and the database version is reported as 'C.0.8.54'.
> this is critical and I need to get this up and running again. Any ideas?
>
> --
> John Cleveland
> Network Manager
> Urban systems Ltd
>|||I actually have this fixed now, it was caused by the sp2 upgrade. I
uninstalled rs, reinstalled and applied sp2 once again and all is fine.
Reports cam back properly, but the data sources had to be reconfigured. No
biggie.
Thanks for your suggestions though.
--
John Cleveland
Network Manager
Urban systems Ltd
"Lisa Slater Nicholls" wrote:
> Is there a possibility that you actually have two different db's and your
> reportserver instance is pointed at the "wrong" one frm the POV of the one
> that your web application thinks it should connect to?
> This might have happened if the person applying the update is not the
> administrator of the box. See
> http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213
> It can also happen if you apply the update in the wrong identity, even if
> you are an administrator (I know that from personal experience <sigh> FWIW
> the ReportServer database has a sprocwhere this is hard coded. I kid you
> not. I think it gets adjusted during upgrades with a file called
> catalog.sql. )
> Short version of the fix described in that thread: you have to stop IIS and
> RS and copy the files that were truly upgraded to the correct location --
> but you should probably read the thread.
> HTH,
> >L<
>
> "John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
> news:C797E3E5-38CA-4547-AD46-2215A50529A4@.microsoft.com...
> >I just installed SP2 for 2005 standard edition and am getting the following
> > error when trying to use report server:
> >
> > "The version of the report server database is either in a format that is
> > not
> > valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> > version is 'C.0.8.43'. To continue, update the version of the report
> > server
> > database and verify access rights. (rsInvalidReportServerDatabase)"
> >
> > When I go into Reporting service configuration tool, the update button
> > returns the following:
> >
> > "The database version matches your Reporting services installation"
> >
> > and the database version is reported as 'C.0.8.54'.
> >
> > this is critical and I need to get this up and running again. Any ideas?
> >
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
> >
>
error when trying to use report server:
"The version of the report server database is either in a format that is not
valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
version is 'C.0.8.43'. To continue, update the version of the report server
database and verify access rights. (rsInvalidReportServerDatabase)"
When I go into Reporting service configuration tool, the update button
returns the following:
"The database version matches your Reporting services installation"
and the database version is reported as 'C.0.8.54'.
this is critical and I need to get this up and running again. Any ideas?
--
John Cleveland
Network Manager
Urban systems LtdHave you installed any SQL service packs BEFORE adding other parts
like 'reporting services'
Also, there was a critical patch sent through windows update that
updates SQL server. Not sure if that is causing you problems.
On Apr 13, 1:16 am, John Cleveland
<JohnClevel...@.discussions.microsoft.com> wrote:
> I just installed SP2 for 2005 standard edition and am getting the following
> error when trying to use report server:
> "The version of the report server database is either in a format that is not
> valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> version is 'C.0.8.43'. To continue, update the version of the report server
> database and verify access rights. (rsInvalidReportServerDatabase)"
> When I go into Reporting service configuration tool, the update button
> returns the following:
> "The database version matches your Reporting services installation"
> and the database version is reported as 'C.0.8.54'.
> this is critical and I need to get this up and running again. Any ideas?
> --
> John Cleveland
> Network Manager
> Urban systems Ltd|||SP1 was already installed. reporting services was installed pre sp1.
I've narrowed down the sequence of events that lead to this issue. It seems
there was a reporting services update that was installed without my knowledge
that was intended for sp2 installs. SP2 wasn't installed yet. even though
sp2 is now installed, i still get the error message listed previously.
--
John Cleveland
Network Manager
Urban systems Ltd
"gommo" wrote:
> Have you installed any SQL service packs BEFORE adding other parts
> like 'reporting services'
> Also, there was a critical patch sent through windows update that
> updates SQL server. Not sure if that is causing you problems.
> On Apr 13, 1:16 am, John Cleveland
> <JohnClevel...@.discussions.microsoft.com> wrote:
> > I just installed SP2 for 2005 standard edition and am getting the following
> > error when trying to use report server:
> >
> > "The version of the report server database is either in a format that is not
> > valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> > version is 'C.0.8.43'. To continue, update the version of the report server
> > database and verify access rights. (rsInvalidReportServerDatabase)"
> >
> > When I go into Reporting service configuration tool, the update button
> > returns the following:
> >
> > "The database version matches your Reporting services installation"
> >
> > and the database version is reported as 'C.0.8.54'.
> >
> > this is critical and I need to get this up and running again. Any ideas?
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
>
>|||Is there a possibility that you actually have two different db's and your
reportserver instance is pointed at the "wrong" one frm the POV of the one
that your web application thinks it should connect to?
This might have happened if the person applying the update is not the
administrator of the box. See
http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213
It can also happen if you apply the update in the wrong identity, even if
you are an administrator (I know that from personal experience <sigh> FWIW
the ReportServer database has a sprocwhere this is hard coded. I kid you
not. I think it gets adjusted during upgrades with a file called
catalog.sql. )
Short version of the fix described in that thread: you have to stop IIS and
RS and copy the files that were truly upgraded to the correct location --
but you should probably read the thread.
HTH,
>L<
"John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
news:C797E3E5-38CA-4547-AD46-2215A50529A4@.microsoft.com...
>I just installed SP2 for 2005 standard edition and am getting the following
> error when trying to use report server:
> "The version of the report server database is either in a format that is
> not
> valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> version is 'C.0.8.43'. To continue, update the version of the report
> server
> database and verify access rights. (rsInvalidReportServerDatabase)"
> When I go into Reporting service configuration tool, the update button
> returns the following:
> "The database version matches your Reporting services installation"
> and the database version is reported as 'C.0.8.54'.
> this is critical and I need to get this up and running again. Any ideas?
>
> --
> John Cleveland
> Network Manager
> Urban systems Ltd
>|||I actually have this fixed now, it was caused by the sp2 upgrade. I
uninstalled rs, reinstalled and applied sp2 once again and all is fine.
Reports cam back properly, but the data sources had to be reconfigured. No
biggie.
Thanks for your suggestions though.
--
John Cleveland
Network Manager
Urban systems Ltd
"Lisa Slater Nicholls" wrote:
> Is there a possibility that you actually have two different db's and your
> reportserver instance is pointed at the "wrong" one frm the POV of the one
> that your web application thinks it should connect to?
> This might have happened if the person applying the update is not the
> administrator of the box. See
> http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=150&messageid=293213
> It can also happen if you apply the update in the wrong identity, even if
> you are an administrator (I know that from personal experience <sigh> FWIW
> the ReportServer database has a sprocwhere this is hard coded. I kid you
> not. I think it gets adjusted during upgrades with a file called
> catalog.sql. )
> Short version of the fix described in that thread: you have to stop IIS and
> RS and copy the files that were truly upgraded to the correct location --
> but you should probably read the thread.
> HTH,
> >L<
>
> "John Cleveland" <JohnCleveland@.discussions.microsoft.com> wrote in message
> news:C797E3E5-38CA-4547-AD46-2215A50529A4@.microsoft.com...
> >I just installed SP2 for 2005 standard edition and am getting the following
> > error when trying to use report server:
> >
> > "The version of the report server database is either in a format that is
> > not
> > valid, or it cannot be read. The found version is 'C.0.8.54'. The expected
> > version is 'C.0.8.43'. To continue, update the version of the report
> > server
> > database and verify access rights. (rsInvalidReportServerDatabase)"
> >
> > When I go into Reporting service configuration tool, the update button
> > returns the following:
> >
> > "The database version matches your Reporting services installation"
> >
> > and the database version is reported as 'C.0.8.54'.
> >
> > this is critical and I need to get this up and running again. Any ideas?
> >
> >
> > --
> > John Cleveland
> > Network Manager
> > Urban systems Ltd
> >
>
Subscribe to:
Posts (Atom)