How do you report errors from a stored procedure? For example, if the stored
procedure is trying to insert something into a table and the database is
full, how can the stored procedure return an error string to the caller?Hi Swami,
This article might help...
http://www.sqljunkies.com/Article/5...3B6D84BF94.scuk
"Swami" wrote:
> How do you report errors from a stored procedure? For example, if the stor
ed
> procedure is trying to insert something into a table and the database is
> full, how can the stored procedure return an error string to the caller?
>|||Thanks--great article.
"Ryan Randall" wrote:
> Hi Swami,
> This article might help...
> [url]http://www.sqljunkies.com/Article/564F5D77-2F7E-41FB-91C7-353B6D84BF94.scuk[/url
]
>
> "Swami" wrote:
>
Showing posts with label errors. Show all posts
Showing posts with label errors. Show all posts
Thursday, March 29, 2012
Error replication agent is not registered properly
We've been running transactional replication with updatable subscribers for
several months now. his morning we are seeing these errors in the LOG and
QUEUE READER logs.
You Receive Error Message: "The replication agent is not registered
properly. Rerun SQL Server setup.
Any ideas?
SQL Server 2000 SP3
Running the following command would likely resolve the issue:
"%ProgramFiles%\Microsoft SQL Server\80\COM\qrdrsvc.exe" -RegServer
Although I am curious to know if you have installed\uninstalled software
recently on the box that might have caused the problem in the first place.
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:ehtb84P$FHA.740@.TK2MSFTNGP12.phx.gbl...
> We've been running transactional replication with updatable subscribers
> for
> several months now. his morning we are seeing these errors in the LOG and
> QUEUE READER logs.
>
> You Receive Error Message: "The replication agent is not registered
> properly. Rerun SQL Server setup.
>
> Any ideas?
> SQL Server 2000 SP3
>
|||Appreciate the info !
We are investigating if changes to either the OS or SQLServer itself are the
root cause of this problem. We are seeing that in addition to the queue
reader agent, these are also experiencing the same errors:
LOG READER agent
SNAPSHOT agent
DISTRIBUTION agent.
Does this means we also need to run the command below to register the above
agents as well or just 'qrdrsvc.exe' as you indicate?
==============
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:O2nEgfS$FHA.140@.TK2MSFTNGP12.phx.gbl...
> Running the following command would likely resolve the issue:
> "%ProgramFiles%\Microsoft SQL Server\80\COM\qrdrsvc.exe" -RegServer
> Although I am curious to know if you have installed\uninstalled software
> recently on the box that might have caused the problem in the first place.
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:ehtb84P$FHA.740@.TK2MSFTNGP12.phx.gbl...
>
|||This seems really strange, is this a clustered SQL Server instance or was
there a registry restore\repair on the box?
In any case, you can probably resolve the issue that you are seeing by
running the agent executables with the -RegServer parameter:
Snapshot agent - snapshot.exe
Logreader agent - logread.exe
Distribution agent - distrib.exe
If the problem is as extensive as it seems to be you may also need to
re-register the support dlls for the replication agents using regsvr32.exe.
Here is a list off the top of my head:
rinitcom.dll
repldp.dll
rdistcom.dll
-Raymond
"GuayacanSQL" <abraxas1969@.hotmail.com> wrote in message
news:eDajBto$FHA.3864@.TK2MSFTNGP12.phx.gbl...
> Appreciate the info !
>
> We are investigating if changes to either the OS or SQLServer itself are
> the root cause of this problem. We are seeing that in addition to the
> queue reader agent, these are also experiencing the same errors:
>
> LOG READER agent
> SNAPSHOT agent
> DISTRIBUTION agent.
>
> Does this means we also need to run the command below to register the
> above agents as well or just 'qrdrsvc.exe' as you indicate?
>
> ==============
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:O2nEgfS$FHA.140@.TK2MSFTNGP12.phx.gbl...
>
|||This is a 2-node clustered SQLServer environment. Word were are getting is
that an attempt to install a new named instance on the cluster failed
(reason unknown) and had to be uninstalled. We are seeing these errors right
after this happened.
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:%23wyI2D0$FHA.2736@.TK2MSFTNGP11.phx.gbl...
> This seems really strange, is this a clustered SQL Server instance or was
> there a registry restore\repair on the box?
> In any case, you can probably resolve the issue that you are seeing by
> running the agent executables with the -RegServer parameter:
> Snapshot agent - snapshot.exe
> Logreader agent - logread.exe
> Distribution agent - distrib.exe
> If the problem is as extensive as it seems to be you may also need to
> re-register the support dlls for the replication agents using
regsvr32.exe.[vbcol=seagreen]
> Here is a list off the top of my head:
> rinitcom.dll
> repldp.dll
> rdistcom.dll
> -Raymond
> "GuayacanSQL" <abraxas1969@.hotmail.com> wrote in message
> news:eDajBto$FHA.3864@.TK2MSFTNGP12.phx.gbl...
software[vbcol=seagreen]
subscribers
>
|||It was determined that uninstalling one of the SQL instances on the cluster
caused the replication agents to be unregistered. We executed the commands
below and all went well with the exception of the QUEUE READER agent. When
we attempt to register the queue reader agent with 'qrdrsvc.exe regserver'
we get this error:
===================
Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
2000 Microsoft Corporation
Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
exist or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
=======================
Is there something special about registering queue reader agent ?
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:OcDiKc0$FHA.140@.TK2MSFTNGP12.phx.gbl...
> This is a 2-node clustered SQLServer environment. Word were are getting is
> that an attempt to install a new named instance on the cluster failed
> (reason unknown) and had to be uninstalled. We are seeing these errors
right[vbcol=seagreen]
> after this happened.
>
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:%23wyI2D0$FHA.2736@.TK2MSFTNGP11.phx.gbl...
was[vbcol=seagreen]
> regsvr32.exe.
are[vbcol=seagreen]
> software
> subscribers
LOG
>
|||That seems kind of strange as I didn't get any messages when I tried the
same on my machine. But if you can start the queue reader agent from
SEM\SQLServerAgent then I wouldn't worry too much about it.
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:eLNoFckAGHA.1312@.TK2MSFTNGP09.phx.gbl...
> It was determined that uninstalling one of the SQL instances on the
> cluster
> caused the replication agents to be unregistered. We executed the commands
> below and all went well with the exception of the QUEUE READER agent.
> When
> we attempt to register the queue reader agent with
> 'qrdrsvc.exe -regserver'
> we get this error:
> ===================
> Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
> 2000 Microsoft Corporation
> Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
> exist or access denied.
> Unable to connect to Local Distributor
> Queue Reader aborting
> =======================
> Is there something special about registering queue reader agent ?
>
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:OcDiKc0$FHA.140@.TK2MSFTNGP12.phx.gbl...
> right
> was
> are
> LOG
>
|||I'm sorry. Can you please elaborate more on what you mean with
SEM\SQLServerAgent ? We are trying to start the queue reader agent from
Enterprise Manager and keep getting the error:
"The replication agent is not registered properly. Rerun SQL Server setup"
===================
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:OdN0KTmAGHA.204@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> That seems kind of strange as I didn't get any messages when I tried the
> same on my machine. But if you can start the queue reader agent from
> SEM\SQLServerAgent then I wouldn't worry too much about it.
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:eLNoFckAGHA.1312@.TK2MSFTNGP09.phx.gbl...
commands[vbcol=seagreen]
(c)[vbcol=seagreen]
by[vbcol=seagreen]
to[vbcol=seagreen]
itself[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
Server\80\COM\qrdrsvc.exe" -RegServer[vbcol=seagreen]
first[vbcol=seagreen]
registered
>
|||Hi Mark,
When a replication agent is started through a SQL Server Agent job (which is
the same as starting a replication agent from SEM), SQL Server Agent will
activate the replication agent as a COM exe server rather than running it as
a regular executable. That is why I suspect that the COM registration
information for the replication agents was broken when you first reported
the problem. Now from what you have described, your SQL Server installation
was broken due to a clustered instance uninstall so a better course of
action is probably for you to reinstall SQL server rather than trying to fix
bits and pieces of it since nobody knows exactly what pieces are broken.
That said, it is still strange that running 'qrdrsvc.exe -regserver' didn't
return without errors for you (you would want to make sure that Word didn't
mangle the - for you...).
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:u4%234FonAGHA.3872@.TK2MSFTNGP12.phx.gbl...
> I'm sorry. Can you please elaborate more on what you mean with
> SEM\SQLServerAgent ? We are trying to start the queue reader agent from
> Enterprise Manager and keep getting the error:
> "The replication agent is not registered properly. Rerun SQL Server setup"
> ===================
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:OdN0KTmAGHA.204@.TK2MSFTNGP15.phx.gbl...
> commands
> (c)
> by
> to
> itself
> the
> the
> Server\80\COM\qrdrsvc.exe" -RegServer
> first
> registered
>
|||In fact, this is what we are getting when running 'qrdrsvc.exe -regserver'
as a server administrator (with System Administrator role on the SQL server)
Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
2000 Microsoft Corporation
Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
exist or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
The process finished. Use CTRL+C to close this window.
=========================
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:%23USLY0nAGHA.516@.TK2MSFTNGP15.phx.gbl...
> Hi Mark,
> When a replication agent is started through a SQL Server Agent job (which
is
> the same as starting a replication agent from SEM), SQL Server Agent will
> activate the replication agent as a COM exe server rather than running it
as
> a regular executable. That is why I suspect that the COM registration
> information for the replication agents was broken when you first reported
> the problem. Now from what you have described, your SQL Server
installation
> was broken due to a clustered instance uninstall so a better course of
> action is probably for you to reinstall SQL server rather than trying to
fix
> bits and pieces of it since nobody knows exactly what pieces are broken.
> That said, it is still strange that running 'qrdrsvc.exe -regserver'
didn't
> return without errors for you (you would want to make sure that Word
didn't[vbcol=seagreen]
> mangle the - for you...).
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:u4%234FonAGHA.3872@.TK2MSFTNGP12.phx.gbl...
setup"[vbcol=seagreen]
the[vbcol=seagreen]
Copyright[vbcol=seagreen]
not[vbcol=seagreen]
failed[vbcol=seagreen]
errors[vbcol=seagreen]
seeing[vbcol=seagreen]
need[vbcol=seagreen]
to[vbcol=seagreen]
register[vbcol=seagreen]
message
>
several months now. his morning we are seeing these errors in the LOG and
QUEUE READER logs.
You Receive Error Message: "The replication agent is not registered
properly. Rerun SQL Server setup.
Any ideas?
SQL Server 2000 SP3
Running the following command would likely resolve the issue:
"%ProgramFiles%\Microsoft SQL Server\80\COM\qrdrsvc.exe" -RegServer
Although I am curious to know if you have installed\uninstalled software
recently on the box that might have caused the problem in the first place.
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:ehtb84P$FHA.740@.TK2MSFTNGP12.phx.gbl...
> We've been running transactional replication with updatable subscribers
> for
> several months now. his morning we are seeing these errors in the LOG and
> QUEUE READER logs.
>
> You Receive Error Message: "The replication agent is not registered
> properly. Rerun SQL Server setup.
>
> Any ideas?
> SQL Server 2000 SP3
>
|||Appreciate the info !
We are investigating if changes to either the OS or SQLServer itself are the
root cause of this problem. We are seeing that in addition to the queue
reader agent, these are also experiencing the same errors:
LOG READER agent
SNAPSHOT agent
DISTRIBUTION agent.
Does this means we also need to run the command below to register the above
agents as well or just 'qrdrsvc.exe' as you indicate?
==============
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:O2nEgfS$FHA.140@.TK2MSFTNGP12.phx.gbl...
> Running the following command would likely resolve the issue:
> "%ProgramFiles%\Microsoft SQL Server\80\COM\qrdrsvc.exe" -RegServer
> Although I am curious to know if you have installed\uninstalled software
> recently on the box that might have caused the problem in the first place.
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:ehtb84P$FHA.740@.TK2MSFTNGP12.phx.gbl...
>
|||This seems really strange, is this a clustered SQL Server instance or was
there a registry restore\repair on the box?
In any case, you can probably resolve the issue that you are seeing by
running the agent executables with the -RegServer parameter:
Snapshot agent - snapshot.exe
Logreader agent - logread.exe
Distribution agent - distrib.exe
If the problem is as extensive as it seems to be you may also need to
re-register the support dlls for the replication agents using regsvr32.exe.
Here is a list off the top of my head:
rinitcom.dll
repldp.dll
rdistcom.dll
-Raymond
"GuayacanSQL" <abraxas1969@.hotmail.com> wrote in message
news:eDajBto$FHA.3864@.TK2MSFTNGP12.phx.gbl...
> Appreciate the info !
>
> We are investigating if changes to either the OS or SQLServer itself are
> the root cause of this problem. We are seeing that in addition to the
> queue reader agent, these are also experiencing the same errors:
>
> LOG READER agent
> SNAPSHOT agent
> DISTRIBUTION agent.
>
> Does this means we also need to run the command below to register the
> above agents as well or just 'qrdrsvc.exe' as you indicate?
>
> ==============
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:O2nEgfS$FHA.140@.TK2MSFTNGP12.phx.gbl...
>
|||This is a 2-node clustered SQLServer environment. Word were are getting is
that an attempt to install a new named instance on the cluster failed
(reason unknown) and had to be uninstalled. We are seeing these errors right
after this happened.
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:%23wyI2D0$FHA.2736@.TK2MSFTNGP11.phx.gbl...
> This seems really strange, is this a clustered SQL Server instance or was
> there a registry restore\repair on the box?
> In any case, you can probably resolve the issue that you are seeing by
> running the agent executables with the -RegServer parameter:
> Snapshot agent - snapshot.exe
> Logreader agent - logread.exe
> Distribution agent - distrib.exe
> If the problem is as extensive as it seems to be you may also need to
> re-register the support dlls for the replication agents using
regsvr32.exe.[vbcol=seagreen]
> Here is a list off the top of my head:
> rinitcom.dll
> repldp.dll
> rdistcom.dll
> -Raymond
> "GuayacanSQL" <abraxas1969@.hotmail.com> wrote in message
> news:eDajBto$FHA.3864@.TK2MSFTNGP12.phx.gbl...
software[vbcol=seagreen]
subscribers
>
|||It was determined that uninstalling one of the SQL instances on the cluster
caused the replication agents to be unregistered. We executed the commands
below and all went well with the exception of the QUEUE READER agent. When
we attempt to register the queue reader agent with 'qrdrsvc.exe regserver'
we get this error:
===================
Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
2000 Microsoft Corporation
Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
exist or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
=======================
Is there something special about registering queue reader agent ?
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:OcDiKc0$FHA.140@.TK2MSFTNGP12.phx.gbl...
> This is a 2-node clustered SQLServer environment. Word were are getting is
> that an attempt to install a new named instance on the cluster failed
> (reason unknown) and had to be uninstalled. We are seeing these errors
right[vbcol=seagreen]
> after this happened.
>
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:%23wyI2D0$FHA.2736@.TK2MSFTNGP11.phx.gbl...
was[vbcol=seagreen]
> regsvr32.exe.
are[vbcol=seagreen]
> software
> subscribers
LOG
>
|||That seems kind of strange as I didn't get any messages when I tried the
same on my machine. But if you can start the queue reader agent from
SEM\SQLServerAgent then I wouldn't worry too much about it.
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:eLNoFckAGHA.1312@.TK2MSFTNGP09.phx.gbl...
> It was determined that uninstalling one of the SQL instances on the
> cluster
> caused the replication agents to be unregistered. We executed the commands
> below and all went well with the exception of the QUEUE READER agent.
> When
> we attempt to register the queue reader agent with
> 'qrdrsvc.exe -regserver'
> we get this error:
> ===================
> Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
> 2000 Microsoft Corporation
> Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
> exist or access denied.
> Unable to connect to Local Distributor
> Queue Reader aborting
> =======================
> Is there something special about registering queue reader agent ?
>
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:OcDiKc0$FHA.140@.TK2MSFTNGP12.phx.gbl...
> right
> was
> are
> LOG
>
|||I'm sorry. Can you please elaborate more on what you mean with
SEM\SQLServerAgent ? We are trying to start the queue reader agent from
Enterprise Manager and keep getting the error:
"The replication agent is not registered properly. Rerun SQL Server setup"
===================
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:OdN0KTmAGHA.204@.TK2MSFTNGP15.phx.gbl...[vbcol=seagreen]
> That seems kind of strange as I didn't get any messages when I tried the
> same on my machine. But if you can start the queue reader agent from
> SEM\SQLServerAgent then I wouldn't worry too much about it.
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:eLNoFckAGHA.1312@.TK2MSFTNGP09.phx.gbl...
commands[vbcol=seagreen]
(c)[vbcol=seagreen]
by[vbcol=seagreen]
to[vbcol=seagreen]
itself[vbcol=seagreen]
the[vbcol=seagreen]
the[vbcol=seagreen]
Server\80\COM\qrdrsvc.exe" -RegServer[vbcol=seagreen]
first[vbcol=seagreen]
registered
>
|||Hi Mark,
When a replication agent is started through a SQL Server Agent job (which is
the same as starting a replication agent from SEM), SQL Server Agent will
activate the replication agent as a COM exe server rather than running it as
a regular executable. That is why I suspect that the COM registration
information for the replication agents was broken when you first reported
the problem. Now from what you have described, your SQL Server installation
was broken due to a clustered instance uninstall so a better course of
action is probably for you to reinstall SQL server rather than trying to fix
bits and pieces of it since nobody knows exactly what pieces are broken.
That said, it is still strange that running 'qrdrsvc.exe -regserver' didn't
return without errors for you (you would want to make sure that Word didn't
mangle the - for you...).
-Raymond
"CAP" <abraxas1969@.hotmail.com> wrote in message
news:u4%234FonAGHA.3872@.TK2MSFTNGP12.phx.gbl...
> I'm sorry. Can you please elaborate more on what you mean with
> SEM\SQLServerAgent ? We are trying to start the queue reader agent from
> Enterprise Manager and keep getting the error:
> "The replication agent is not registered properly. Rerun SQL Server setup"
> ===================
> "Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
> news:OdN0KTmAGHA.204@.TK2MSFTNGP15.phx.gbl...
> commands
> (c)
> by
> to
> itself
> the
> the
> Server\80\COM\qrdrsvc.exe" -RegServer
> first
> registered
>
|||In fact, this is what we are getting when running 'qrdrsvc.exe -regserver'
as a server administrator (with System Administrator role on the SQL server)
Microsoft SQL Server Replication Queue Reader Agent 8.00.760 Copyright (c)
2000 Microsoft Corporation
Server: SERVER1, Database distribution : ODBC Error:SQL Server does not
exist or access denied.
Unable to connect to Local Distributor
Queue Reader aborting
The process finished. Use CTRL+C to close this window.
=========================
"Raymond Mak [MSFT]" <rmak@.online.microsoft.com> wrote in message
news:%23USLY0nAGHA.516@.TK2MSFTNGP15.phx.gbl...
> Hi Mark,
> When a replication agent is started through a SQL Server Agent job (which
is
> the same as starting a replication agent from SEM), SQL Server Agent will
> activate the replication agent as a COM exe server rather than running it
as
> a regular executable. That is why I suspect that the COM registration
> information for the replication agents was broken when you first reported
> the problem. Now from what you have described, your SQL Server
installation
> was broken due to a clustered instance uninstall so a better course of
> action is probably for you to reinstall SQL server rather than trying to
fix
> bits and pieces of it since nobody knows exactly what pieces are broken.
> That said, it is still strange that running 'qrdrsvc.exe -regserver'
didn't
> return without errors for you (you would want to make sure that Word
didn't[vbcol=seagreen]
> mangle the - for you...).
> -Raymond
> "CAP" <abraxas1969@.hotmail.com> wrote in message
> news:u4%234FonAGHA.3872@.TK2MSFTNGP12.phx.gbl...
setup"[vbcol=seagreen]
the[vbcol=seagreen]
Copyright[vbcol=seagreen]
not[vbcol=seagreen]
failed[vbcol=seagreen]
errors[vbcol=seagreen]
seeing[vbcol=seagreen]
need[vbcol=seagreen]
to[vbcol=seagreen]
register[vbcol=seagreen]
message
>
Tuesday, March 27, 2012
Error reading variable
I keep receiving errors while using variables to pass values to different part of my package. For example ...
Error: 2006-05-04 10:31:59.84
Code: 0xC00470EA
Source: EdwPostProcess
Description: Reading the variable "User::GvPathRoot" failed with error code 0xC0010009.
End Error
The way my variables are constructed is :
First the global variables (Gv*) are set by the parent package; Then local variables (Lv*) are set using the EvaluateAsExpression property and giving it an expression that takes the Gv* variable and concatenate a string to it.At execution time, while the expressions are resolved, I get the above error while it was resolved correctly in a previous task.
I tried different method including duplicating my variables but without success. I'm running out of ideas
Gilles
Sorry I don't have an answer. But just wanted to report a very similar problem I am having. I am also at my wits' end since the problem cannot be reproduced at will.
I am also passing variable from parent package to a child package. There is a loop in the parent package and in each iteration, the value of this variable changes. There are 9 iterations of the loop and so 9 different values of this variable. Most of the times all the loops are successful (particularly if the volume of data is less). If the volume of data processed by the child package is more then I sometimetimes get this error in the 5th or later iteration. I have changed the order of the values of the variable but looks like it does not matter - it fails at different values.
Ketan
|||My variable was used in a script task and in expressions on other tasks. By re-arranging my tasks flow so the script task wouldn't be executed at the same time as another task with the same variable seem to have corrected the problem.
A variable used by a script task is lock in memory even when it is used for read only. So depending on how fast each task completes, it is possible that sometime we encounter the variable locked situation sometime not.
I found a way to eliminate the script task from my flow and everything is fine now.
Gilles
|||Another good technique to minimise locking is to reduce the scope of variables. You may end up with what seem like duplicates, by scoping variables to loops and containers or tasks, but this is more reliable than sharing variables when strictly speaking you never use the value outside of the lower scoped executable.Error reading variable
I keep receiving errors while using variables to pass values to different part of my package. For example ...
Error: 2006-05-04 10:31:59.84
Code: 0xC00470EA
Source: EdwPostProcess
Description: Reading the variable "User::GvPathRoot" failed with error code 0xC0010009.
End Error
The way my variables are constructed is :
First the global variables (Gv*) are set by the parent package; Then local variables (Lv*) are set using the EvaluateAsExpression property and giving it an expression that takes the Gv* variable and concatenate a string to it.At execution time, while the expressions are resolved, I get the above error while it was resolved correctly in a previous task.
I tried different method including duplicating my variables but without success. I'm running out of ideas
Gilles
Sorry I don't have an answer. But just wanted to report a very similar problem I am having. I am also at my wits' end since the problem cannot be reproduced at will.
I am also passing variable from parent package to a child package. There is a loop in the parent package and in each iteration, the value of this variable changes. There are 9 iterations of the loop and so 9 different values of this variable. Most of the times all the loops are successful (particularly if the volume of data is less). If the volume of data processed by the child package is more then I sometimetimes get this error in the 5th or later iteration. I have changed the order of the values of the variable but looks like it does not matter - it fails at different values.
Ketan
|||My variable was used in a script task and in expressions on other tasks. By re-arranging my tasks flow so the script task wouldn't be executed at the same time as another task with the same variable seem to have corrected the problem.
A variable used by a script task is lock in memory even when it is used for read only. So depending on how fast each task completes, it is possible that sometime we encounter the variable locked situation sometime not.
I found a way to eliminate the script task from my flow and everything is fine now.
Gilles
|||Another good technique to minimise locking is to reduce the scope of variables. You may end up with what seem like duplicates, by scoping variables to loops and containers or tasks, but this is more reliable than sharing variables when strictly speaking you never use the value outside of the lower scoped executable.Friday, March 23, 2012
Error on Restoring Database
Hi All,
We are trying to restore a database from a live system to our test system.
However, we are receiving the following errors when attempting to perform
this restore
"Modify file encountered operating system error 112(error code not found)
while attempting to expand the physical file
Cound not adjust the space allocation for file FILENAME"
I have tried searching online for this, but have had no luck. Also, when we
perform a restore of the backup from the test system this works fine.
Any help will be most appreciated
Richard,
Sounds like you might using a disk that was formatted for FAT32. Have you
checked that? FAT32 will only allow file sizes up to 4GB.
Mike C.
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when we
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated
|||Hi,
Our discs are only ever formatted in NTFS
"MACason" wrote:
[vbcol=seagreen]
> Richard,
> Sounds like you might using a disk that was formatted for FAT32. Have you
> checked that? FAT32 will only allow file sizes up to 4GB.
> Mike C.
> "Richardw" wrote:
|||it seems too easy, but: did you verify the space allocation requirements for
the database? Are the permissions on the file system of the test environment
alright?
The message is referable to the SQL Server error 3140, and the possible
causes could be: lack of space on the disk, wrong name of the file, porblems
with the transaction log file; search for SQL Server error 3140 (Google it!)
Gilberto
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when we
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated
|||Hi Gilberto,
Thanks for this, I had just noticed that the disc was seriously short on
space and am just trying to clear some, hopefully it will reolve the issue
"Gilberto Zampatti" wrote:
[vbcol=seagreen]
> it seems too easy, but: did you verify the space allocation requirements for
> the database? Are the permissions on the file system of the test environment
> alright?
> The message is referable to the SQL Server error 3140, and the possible
> causes could be: lack of space on the disk, wrong name of the file, porblems
> with the transaction log file; search for SQL Server error 3140 (Google it!)
> Gilberto
> "Richardw" wrote:
We are trying to restore a database from a live system to our test system.
However, we are receiving the following errors when attempting to perform
this restore
"Modify file encountered operating system error 112(error code not found)
while attempting to expand the physical file
Cound not adjust the space allocation for file FILENAME"
I have tried searching online for this, but have had no luck. Also, when we
perform a restore of the backup from the test system this works fine.
Any help will be most appreciated
Richard,
Sounds like you might using a disk that was formatted for FAT32. Have you
checked that? FAT32 will only allow file sizes up to 4GB.
Mike C.
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when we
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated
|||Hi,
Our discs are only ever formatted in NTFS
"MACason" wrote:
[vbcol=seagreen]
> Richard,
> Sounds like you might using a disk that was formatted for FAT32. Have you
> checked that? FAT32 will only allow file sizes up to 4GB.
> Mike C.
> "Richardw" wrote:
|||it seems too easy, but: did you verify the space allocation requirements for
the database? Are the permissions on the file system of the test environment
alright?
The message is referable to the SQL Server error 3140, and the possible
causes could be: lack of space on the disk, wrong name of the file, porblems
with the transaction log file; search for SQL Server error 3140 (Google it!)
Gilberto
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when we
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated
|||Hi Gilberto,
Thanks for this, I had just noticed that the disc was seriously short on
space and am just trying to clear some, hopefully it will reolve the issue
"Gilberto Zampatti" wrote:
[vbcol=seagreen]
> it seems too easy, but: did you verify the space allocation requirements for
> the database? Are the permissions on the file system of the test environment
> alright?
> The message is referable to the SQL Server error 3140, and the possible
> causes could be: lack of space on the disk, wrong name of the file, porblems
> with the transaction log file; search for SQL Server error 3140 (Google it!)
> Gilberto
> "Richardw" wrote:
Error on Restoring Database
Hi All,
We are trying to restore a database from a live system to our test system.
However, we are receiving the following errors when attempting to perform
this restore
"Modify file encountered operating system error 112(error code not found)
while attempting to expand the physical file
Cound not adjust the space allocation for file FILENAME"
I have tried searching online for this, but have had no luck. Also, when we
perform a restore of the backup from the test system this works fine.
Any help will be most appreciatedRichard,
Sounds like you might using a disk that was formatted for FAT32. Have you
checked that? FAT32 will only allow file sizes up to 4GB.
Mike C.
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when w
e
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated|||Hi,
Our discs are only ever formatted in NTFS
"MACason" wrote:
[vbcol=seagreen]
> Richard,
> Sounds like you might using a disk that was formatted for FAT32. Have you
> checked that? FAT32 will only allow file sizes up to 4GB.
> Mike C.
> "Richardw" wrote:
>|||it seems too easy, but: did you verify the space allocation requirements for
the database? Are the permissions on the file system of the test environment
alright?
The message is referable to the SQL Server error 3140, and the possible
causes could be: lack of space on the disk, wrong name of the file, porblems
with the transaction log file; search for SQL Server error 3140 (Google it!)
Gilberto
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when w
e
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated|||Hi Gilberto,
Thanks for this, I had just noticed that the disc was seriously short on
space and am just trying to clear some, hopefully it will reolve the issue
"Gilberto Zampatti" wrote:
[vbcol=seagreen]
> it seems too easy, but: did you verify the space allocation requirements f
or
> the database? Are the permissions on the file system of the test environme
nt
> alright?
> The message is referable to the SQL Server error 3140, and the possible
> causes could be: lack of space on the disk, wrong name of the file, porble
ms
> with the transaction log file; search for SQL Server error 3140 (Google it
!)
> Gilberto
> "Richardw" wrote:
>
We are trying to restore a database from a live system to our test system.
However, we are receiving the following errors when attempting to perform
this restore
"Modify file encountered operating system error 112(error code not found)
while attempting to expand the physical file
Cound not adjust the space allocation for file FILENAME"
I have tried searching online for this, but have had no luck. Also, when we
perform a restore of the backup from the test system this works fine.
Any help will be most appreciatedRichard,
Sounds like you might using a disk that was formatted for FAT32. Have you
checked that? FAT32 will only allow file sizes up to 4GB.
Mike C.
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when w
e
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated|||Hi,
Our discs are only ever formatted in NTFS
"MACason" wrote:
[vbcol=seagreen]
> Richard,
> Sounds like you might using a disk that was formatted for FAT32. Have you
> checked that? FAT32 will only allow file sizes up to 4GB.
> Mike C.
> "Richardw" wrote:
>|||it seems too easy, but: did you verify the space allocation requirements for
the database? Are the permissions on the file system of the test environment
alright?
The message is referable to the SQL Server error 3140, and the possible
causes could be: lack of space on the disk, wrong name of the file, porblems
with the transaction log file; search for SQL Server error 3140 (Google it!)
Gilberto
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when w
e
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated|||Hi Gilberto,
Thanks for this, I had just noticed that the disc was seriously short on
space and am just trying to clear some, hopefully it will reolve the issue
"Gilberto Zampatti" wrote:
[vbcol=seagreen]
> it seems too easy, but: did you verify the space allocation requirements f
or
> the database? Are the permissions on the file system of the test environme
nt
> alright?
> The message is referable to the SQL Server error 3140, and the possible
> causes could be: lack of space on the disk, wrong name of the file, porble
ms
> with the transaction log file; search for SQL Server error 3140 (Google it
!)
> Gilberto
> "Richardw" wrote:
>
Error on Restoring Database
Hi All,
We are trying to restore a database from a live system to our test system.
However, we are receiving the following errors when attempting to perform
this restore
"Modify file encountered operating system error 112(error code not found)
while attempting to expand the physical file
Cound not adjust the space allocation for file FILENAME"
I have tried searching online for this, but have had no luck. Also, when we
perform a restore of the backup from the test system this works fine.
Any help will be most appreciatedRichard,
Sounds like you might using a disk that was formatted for FAT32. Have you
checked that? FAT32 will only allow file sizes up to 4GB.
Mike C.
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when we
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated|||Hi,
Our discs are only ever formatted in NTFS
"MACason" wrote:
> Richard,
> Sounds like you might using a disk that was formatted for FAT32. Have you
> checked that? FAT32 will only allow file sizes up to 4GB.
> Mike C.
> "Richardw" wrote:
> > Hi All,
> >
> > We are trying to restore a database from a live system to our test system.
> > However, we are receiving the following errors when attempting to perform
> > this restore
> >
> > "Modify file encountered operating system error 112(error code not found)
> > while attempting to expand the physical file
> >
> > Cound not adjust the space allocation for file FILENAME"
> >
> > I have tried searching online for this, but have had no luck. Also, when we
> > perform a restore of the backup from the test system this works fine.
> >
> > Any help will be most appreciated|||it seems too easy, but: did you verify the space allocation requirements for
the database? Are the permissions on the file system of the test environment
alright?
The message is referable to the SQL Server error 3140, and the possible
causes could be: lack of space on the disk, wrong name of the file, porblems
with the transaction log file; search for SQL Server error 3140 (Google it!)
Gilberto
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when we
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated|||Hi Gilberto,
Thanks for this, I had just noticed that the disc was seriously short on
space and am just trying to clear some, hopefully it will reolve the issue
"Gilberto Zampatti" wrote:
> it seems too easy, but: did you verify the space allocation requirements for
> the database? Are the permissions on the file system of the test environment
> alright?
> The message is referable to the SQL Server error 3140, and the possible
> causes could be: lack of space on the disk, wrong name of the file, porblems
> with the transaction log file; search for SQL Server error 3140 (Google it!)
> Gilberto
> "Richardw" wrote:
> > Hi All,
> >
> > We are trying to restore a database from a live system to our test system.
> > However, we are receiving the following errors when attempting to perform
> > this restore
> >
> > "Modify file encountered operating system error 112(error code not found)
> > while attempting to expand the physical file
> >
> > Cound not adjust the space allocation for file FILENAME"
> >
> > I have tried searching online for this, but have had no luck. Also, when we
> > perform a restore of the backup from the test system this works fine.
> >
> > Any help will be most appreciated
We are trying to restore a database from a live system to our test system.
However, we are receiving the following errors when attempting to perform
this restore
"Modify file encountered operating system error 112(error code not found)
while attempting to expand the physical file
Cound not adjust the space allocation for file FILENAME"
I have tried searching online for this, but have had no luck. Also, when we
perform a restore of the backup from the test system this works fine.
Any help will be most appreciatedRichard,
Sounds like you might using a disk that was formatted for FAT32. Have you
checked that? FAT32 will only allow file sizes up to 4GB.
Mike C.
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when we
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated|||Hi,
Our discs are only ever formatted in NTFS
"MACason" wrote:
> Richard,
> Sounds like you might using a disk that was formatted for FAT32. Have you
> checked that? FAT32 will only allow file sizes up to 4GB.
> Mike C.
> "Richardw" wrote:
> > Hi All,
> >
> > We are trying to restore a database from a live system to our test system.
> > However, we are receiving the following errors when attempting to perform
> > this restore
> >
> > "Modify file encountered operating system error 112(error code not found)
> > while attempting to expand the physical file
> >
> > Cound not adjust the space allocation for file FILENAME"
> >
> > I have tried searching online for this, but have had no luck. Also, when we
> > perform a restore of the backup from the test system this works fine.
> >
> > Any help will be most appreciated|||it seems too easy, but: did you verify the space allocation requirements for
the database? Are the permissions on the file system of the test environment
alright?
The message is referable to the SQL Server error 3140, and the possible
causes could be: lack of space on the disk, wrong name of the file, porblems
with the transaction log file; search for SQL Server error 3140 (Google it!)
Gilberto
"Richardw" wrote:
> Hi All,
> We are trying to restore a database from a live system to our test system.
> However, we are receiving the following errors when attempting to perform
> this restore
> "Modify file encountered operating system error 112(error code not found)
> while attempting to expand the physical file
> Cound not adjust the space allocation for file FILENAME"
> I have tried searching online for this, but have had no luck. Also, when we
> perform a restore of the backup from the test system this works fine.
> Any help will be most appreciated|||Hi Gilberto,
Thanks for this, I had just noticed that the disc was seriously short on
space and am just trying to clear some, hopefully it will reolve the issue
"Gilberto Zampatti" wrote:
> it seems too easy, but: did you verify the space allocation requirements for
> the database? Are the permissions on the file system of the test environment
> alright?
> The message is referable to the SQL Server error 3140, and the possible
> causes could be: lack of space on the disk, wrong name of the file, porblems
> with the transaction log file; search for SQL Server error 3140 (Google it!)
> Gilberto
> "Richardw" wrote:
> > Hi All,
> >
> > We are trying to restore a database from a live system to our test system.
> > However, we are receiving the following errors when attempting to perform
> > this restore
> >
> > "Modify file encountered operating system error 112(error code not found)
> > while attempting to expand the physical file
> >
> > Cound not adjust the space allocation for file FILENAME"
> >
> > I have tried searching online for this, but have had no luck. Also, when we
> > perform a restore of the backup from the test system this works fine.
> >
> > Any help will be most appreciated
Monday, March 19, 2012
Error on Creating publication
Hi all, when I create publication with New Publication Wizard. I get the following errors. Did someone meet this before? Can you help me? Thanks!
===================================
SQL Server could not create publication 'JK'. (New Publication Wizard)
===================================
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
Program Location:
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand)
at Microsoft.SqlServer.Replication.ReplicationObject.ExecCommand(String commandIn)
at Microsoft.SqlServer.Replication.ReplicationObject.CommonCreate()
at Microsoft.SqlServer.Replication.Publication.Create()
at Microsoft.SqlServer.Management.UI.CreatePublicationWizard.CreatePublicationThreadMethod()
===================================
Cannot promote the transaction to a distributed transaction because there is an active save point in this transaction.
Changed database context to 'Test'. (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.2047&EvtSrc=MSSQLServer&EvtID=3933&LinkId=20476
Server Name: nxstudio-david\sql2k5_dc
Error Number: 3933
Severity: 16
State: 1
Procedure: sp_addmergepublication
Line Number: 1034
Program Location:
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlCommand.RunExecuteNonQueryTds(String methodName, Boolean async)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType)
Try setting remote proc trans to 0. i.e.
exec sp_configure 'remote proc trans', 0
go
However you may have custom apps that depend on this being enabled, if so, be careful when flipping this switch.
|||Greg, Thanks!
I try to follow your instruction, but I get the following message.
"Configuration option 'remote proc trans' changed from 0 to 0. Run the RECONFIGURE statement to install."
It seems the original value is 0 too.
Monday, March 12, 2012
error of Initializing SQL Server Reconciler has failed using SQL Server CE 2.0
hi,
i'm using SQL Server CE 2.0 in my application.
When i try to synchronize my database by calling
replicator.Synchronize();
errors :
Initializing SQL Server Reconciler has failed.
process could not connect to Distributor
SQL Server does not exists and access denied.
what i did right now is i try to register
regsvr32 "C:\Program Files\Microsoft SQL Server CE 2.0\Server\sscerp20.dll"
regsvr32 "C:\Labs\NorthwindTempFiles\sscesa20.dll"
both of the DLL files were succeed register. However, when i try to re-do the synchronization. The same error still happened!!!
I do not know what's going wrong..=(
Who can help me?!!! HELP~~~~~~~~~
thanks..
June,
Can you connect to the distributor using osql?
Typically, remote connections are disabled by default after installations.
If that is the case, use SAC (Surface Area COnfiguration) to enable the remote connections, recycle the SQL server and try connecting again.|||Just my two cents....
Also check whether you are able to browse the URL or not
/VirtualDirectoryName/sscesa20.dll">http://<IIS-Box-Name>/VirtualDirectoryName/sscesa20.dll from device?
Are you able to browse the general internet/intranet from the device?
If you are able to do both of the above then both connectivity on the device and on the IIS are setup correctly.|||Hi June...
I am also facing the same problem regarding the Initializing SQL Server Reconciler has failed using SQL Server CE 2.0......in my case it happened when i raised the data size in the database befor sync. Actually i am new to this tech can u pls tell me in detail bout wat xactly these dll are for and how to run
"both of the DLL files were succeed register" wat does this mean...pls do take some of ur time to answer my query.It will be a gr8 help from ur side.....
Thanks in advance to you.
Regards,
Asheesh.|||I'm sorry for late response..I've been disconnected from Internet for few days...
By the way, how to connect to my distributor. Actually my distributor is same as my publisher...|||when i type http://IP_address/Virtual_dir_alias/sscesa20.dll
the SQL Server CE Server Agent is shown in my browser|||Hi, Asheesh...
I facing this problem just i try to pull a table from my SQL Server 2000 to my emulator's local database using SQL Server Ce 2.0. I did not try to raise my data size since i just want to create a new database for my emulator. However, i assume i succeed to connect my sscesa20.dll since when i try to browse sscesa20.dll, SQL Server Ce Server Agent message is shown in my browser (no matter in desktop IE or emulator IE)
I try to search online, some suggest that the error occur because of the DLL file that correspond to the SQL Server CE Replication provider is not registered on the computer where SQL Server CE Server Tools is installed. That's y i tried to manually register this DLL file.|||
Mahesh Dudgikar wrote:
June,
Can you connect to the distributor using osql?
Typically, remote connections are disabled by default after installations.
If that is the case, use SAC (Surface Area COnfiguration) to enable the remote connections, recycle the SQL server and try connecting again.
Hi Mahesh,
thanks for reply...
what is SAC...^^;;
i do not know what is that...?
thanks
best regards,
june|||
Hi June,
SAC is Surface Area Configuration Tool that lets you manage how connections are done to this instance of SQL Server.
To access it Click on Start-->All Programs-->Microsoft SQL Server-->Configuration Tools-->SQL Server Surface Area Configuration-->Surface Area Configuration for Services and Connections-->DataBase Engine-->Remote Connections-->Local and Remote conenctions-->Using both TCP/IP and named pipes.
Then recycle the server.
Also try connecting to the SQL Server from a remote machine using osql to see if you can connect to the server.
|||Hi Mahesh,I'm sorry, i didn't mention my SQL Server version in my previous message. Actually i'm using SQL Server 2000...I'm not sure whether SQL Server 2000 having SAC feature..However, i didn't get Configuration Tools in from my MS SQL Server folder...:(
thanks...
june|||And I assumed this was SQL Server 2005 :) dont know why I was under that impression. SAC is only with SQL Server 2005.
So now, you have SQL Server 200 SP3 or SP4?
Can you also try registering replrec.dll? This should be in %ProgramFiles%\Microsoft SQL Server\80\COM directory and retry the synch please.|||June, Could you also please post the connection string you are using to connect to the server.|||Hi,
i'm using SP3a for my SQL Server 2000.
I registered the replrec.dll and re-sync..the error still remain
error messages:
initializing SQL Server Reconciler has failed
process could not connect to Distributor
SQL Server does not exist or access denied..
=(|||Few more questions:
1. Have youever synched successfully previously with this device (subscriber) and publisher?
2. Is this reinitializing?
3. What about permissions for snapshot folder and other items for IIS/SQL Server service. When you setup the virtual directory did you provide all the accounts permissions?|||
ok...my replication declaration:
private const string INTERNETURL = "http://localhost/Northwind/sscesa20.dll";
private const string PUBLISHERSERVER = "TWEEDLEDEE";
private const string PUBLISHERDATABASE = "Northwind";
private const SecurityType PUBLISHERSECURITYMODE =
SecurityType.NTAuthentication;
private const string PUBLICATION = "NorthwindProducts";
private string SUBSCRIBER = Dns.GetHostName();
private const string LOCALDATABASE = "\\My Documents\\products.sdf";
private const string CONNECTIONSTRING = "data source = " + LOCALDATABASE;
i do not sure is it my snapshot folder problem...i'm confuse to the snapshot folder that i created during creating my publication and during set up my virtual directory folder. When i create my publication, my snapshot is C:\Labs\Snapshot (i follow the tutorial)
However, when i set up my virtual directory and enter d same path (C:\Labs\Snapshot), it pop up a message said unable to found the file. Then i enter the snapshot folder as
\\computer_name\C$\Program Files\Microsoft SQL Server\MSSQL$TWEEDLEDEE\ReplData
HOWEVER, when i check out my snapshot location using Enterprise Server
there stated it as \\computer_name\C$\Program Files\Microsoft SQL Server\MSSQL$TWEEDLEDEE\REPLDATA
under generate snapshot in the following location
error of Initializing SQL Server Reconciler has failed using SQL Server CE 2.0
hi,
i'm using SQL Server CE 2.0 in my application.
When i try to synchronize my database by calling
replicator.Synchronize();
errors :
Initializing SQL Server Reconciler has failed.
process could not connect to Distributor
SQL Server does not exists and access denied.
what i did right now is i try to register
regsvr32 "C:\Program Files\Microsoft SQL Server CE 2.0\Server\sscerp20.dll"
regsvr32 "C:\Labs\NorthwindTempFiles\sscesa20.dll"
both of the DLL files were succeed register. However, when i try to re-do the synchronization. The same error still happened!!!
I do not know what's going wrong..=(
Who can help me?!!! HELP~~~~~~~~~
thanks..
June,
Can you connect to the distributor using osql?
Typically, remote connections are disabled by default after installations.
If that is the case, use SAC (Surface Area COnfiguration) to enable the remote connections, recycle the SQL server and try connecting again.|||Just my two cents....
Also check whether you are able to browse the URL or not
/VirtualDirectoryName/sscesa20.dll">http://<IIS-Box-Name>/VirtualDirectoryName/sscesa20.dll from device?
Are you able to browse the general internet/intranet from the device?
If you are able to do both of the above then both connectivity on the device and on the IIS are setup correctly.|||Hi June...
I am also facing the same problem regarding the Initializing SQL Server Reconciler has failed using SQL Server CE 2.0......in my case it happened when i raised the data size in the database befor sync. Actually i am new to this tech can u pls tell me in detail bout wat xactly these dll are for and how to run
"both of the DLL files were succeed register" wat does this mean...pls do take some of ur time to answer my query.It will be a gr8 help from ur side.....
Thanks in advance to you.
Regards,
Asheesh.|||I'm sorry for late response..I've been disconnected from Internet for few days...
By the way, how to connect to my distributor. Actually my distributor is same as my publisher...|||when i type http://IP_address/Virtual_dir_alias/sscesa20.dll
the SQL Server CE Server Agent is shown in my browser|||Hi, Asheesh...
I facing this problem just i try to pull a table from my SQL Server 2000 to my emulator's local database using SQL Server Ce 2.0. I did not try to raise my data size since i just want to create a new database for my emulator. However, i assume i succeed to connect my sscesa20.dll since when i try to browse sscesa20.dll, SQL Server Ce Server Agent message is shown in my browser (no matter in desktop IE or emulator IE)
I try to search online, some suggest that the error occur because of the DLL file that correspond to the SQL Server CE Replication provider is not registered on the computer where SQL Server CE Server Tools is installed. That's y i tried to manually register this DLL file.|||
Mahesh Dudgikar wrote:
June,
Can you connect to the distributor using osql?
Typically, remote connections are disabled by default after installations.
If that is the case, use SAC (Surface Area COnfiguration) to enable the remote connections, recycle the SQL server and try connecting again.
Hi Mahesh,
thanks for reply...
what is SAC...^^;;
i do not know what is that...?
thanks
best regards,
june|||
Hi June,
SAC is Surface Area Configuration Tool that lets you manage how connections are done to this instance of SQL Server.
To access it Click on Start-->All Programs-->Microsoft SQL Server-->Configuration Tools-->SQL Server Surface Area Configuration-->Surface Area Configuration for Services and Connections-->DataBase Engine-->Remote Connections-->Local and Remote conenctions-->Using both TCP/IP and named pipes.
Then recycle the server.
Also try connecting to the SQL Server from a remote machine using osql to see if you can connect to the server.
|||Hi Mahesh,I'm sorry, i didn't mention my SQL Server version in my previous message. Actually i'm using SQL Server 2000...I'm not sure whether SQL Server 2000 having SAC feature..However, i didn't get Configuration Tools in from my MS SQL Server folder...:(
thanks...
june|||And I assumed this was SQL Server 2005 :) dont know why I was under that impression. SAC is only with SQL Server 2005.
So now, you have SQL Server 200 SP3 or SP4?
Can you also try registering replrec.dll? This should be in %ProgramFiles%\Microsoft SQL Server\80\COM directory and retry the synch please.|||June, Could you also please post the connection string you are using to connect to the server.|||Hi,
i'm using SP3a for my SQL Server 2000.
I registered the replrec.dll and re-sync..the error still remain
error messages:
initializing SQL Server Reconciler has failed
process could not connect to Distributor
SQL Server does not exist or access denied..
=(|||Few more questions:
1. Have youever synched successfully previously with this device (subscriber) and publisher?
2. Is this reinitializing?
3. What about permissions for snapshot folder and other items for IIS/SQL Server service. When you setup the virtual directory did you provide all the accounts permissions?|||
ok...my replication declaration:
private const string INTERNETURL = "http://localhost/Northwind/sscesa20.dll";
private const string PUBLISHERSERVER = "TWEEDLEDEE";
private const string PUBLISHERDATABASE = "Northwind";
private const SecurityType PUBLISHERSECURITYMODE =
SecurityType.NTAuthentication;
private const string PUBLICATION = "NorthwindProducts";
private string SUBSCRIBER = Dns.GetHostName();
private const string LOCALDATABASE = "\\My Documents\\products.sdf";
private const string CONNECTIONSTRING = "data source = " + LOCALDATABASE;
i do not sure is it my snapshot folder problem...i'm confuse to the snapshot folder that i created during creating my publication and during set up my virtual directory folder. When i create my publication, my snapshot is C:\Labs\Snapshot (i follow the tutorial)
However, when i set up my virtual directory and enter d same path (C:\Labs\Snapshot), it pop up a message said unable to found the file. Then i enter the snapshot folder as
\\computer_name\C$\Program Files\Microsoft SQL Server\MSSQL$TWEEDLEDEE\ReplData
HOWEVER, when i check out my snapshot location using Enterprise Server
there stated it as \\computer_name\C$\Program Files\Microsoft SQL Server\MSSQL$TWEEDLEDEE\REPLDATA
under generate snapshot in the following location
error of Initializing SQL Server Reconciler has failed using SQL Server CE 2.0
hi,
i'm using SQL Server CE 2.0 in my application.
When i try to synchronize my database by calling
replicator.Synchronize();
errors :
Initializing SQL Server Reconciler has failed.
process could not connect to Distributor
SQL Server does not exists and access denied.
what i did right now is i try to register
regsvr32 "C:\Program Files\Microsoft SQL Server CE 2.0\Server\sscerp20.dll"
regsvr32 "C:\Labs\NorthwindTempFiles\sscesa20.dll"
both of the DLL files were succeed register. However, when i try to re-do the synchronization. The same error still happened!!!
I do not know what's going wrong..=(
Who can help me?!!! HELP~~~~~~~~~
thanks..
June,
Can you connect to the distributor using osql?
Typically, remote connections are disabled by default after installations.
If that is the case, use SAC (Surface Area COnfiguration) to enable the remote connections, recycle the SQL server and try connecting again.|||Just my two cents....
Also check whether you are able to browse the URL or not
/VirtualDirectoryName/sscesa20.dll">http://<IIS-Box-Name>/VirtualDirectoryName/sscesa20.dll from device?
Are you able to browse the general internet/intranet from the device?
If you are able to do both of the above then both connectivity on the device and on the IIS are setup correctly.|||Hi June...
I am also facing the same problem regarding the Initializing SQL Server Reconciler has failed using SQL Server CE 2.0......in my case it happened when i raised the data size in the database befor sync. Actually i am new to this tech can u pls tell me in detail bout wat xactly these dll are for and how to run
"both of the DLL files were succeed register" wat does this mean...pls do take some of ur time to answer my query.It will be a gr8 help from ur side.....
Thanks in advance to you.
Regards,
Asheesh.|||I'm sorry for late response..I've been disconnected from Internet for few days...
By the way, how to connect to my distributor. Actually my distributor is same as my publisher...|||when i type http://IP_address/Virtual_dir_alias/sscesa20.dll
the SQL Server CE Server Agent is shown in my browser|||Hi, Asheesh...
I facing this problem just i try to pull a table from my SQL Server 2000 to my emulator's local database using SQL Server Ce 2.0. I did not try to raise my data size since i just want to create a new database for my emulator. However, i assume i succeed to connect my sscesa20.dll since when i try to browse sscesa20.dll, SQL Server Ce Server Agent message is shown in my browser (no matter in desktop IE or emulator IE)
I try to search online, some suggest that the error occur because of the DLL file that correspond to the SQL Server CE Replication provider is not registered on the computer where SQL Server CE Server Tools is installed. That's y i tried to manually register this DLL file.|||
June,
Can you connect to the distributor using osql?
Typically, remote connections are disabled by default after installations.
If that is the case, use SAC (Surface Area COnfiguration) to enable the remote connections, recycle the SQL server and try connecting again.
Hi Mahesh,
thanks for reply...
what is SAC...^^;;
i do not know what is that...?
thanks
best regards,
june|||
Hi June,
SAC is Surface Area Configuration Tool that lets you manage how connections are done to this instance of SQL Server.
To access it Click on Start-->All Programs-->Microsoft SQL Server-->Configuration Tools-->SQL Server Surface Area Configuration-->Surface Area Configuration for Services and Connections-->DataBase Engine-->Remote Connections-->Local and Remote conenctions-->Using both TCP/IP and named pipes.
Then recycle the server.
Also try connecting to the SQL Server from a remote machine using osql to see if you can connect to the server.
|||Hi Mahesh,I'm sorry, i didn't mention my SQL Server version in my previous message. Actually i'm using SQL Server 2000...I'm not sure whether SQL Server 2000 having SAC feature..However, i didn't get Configuration Tools in from my MS SQL Server folder...:(
thanks...
june|||And I assumed this was SQL Server 2005 :) dont know why I was under that impression. SAC is only with SQL Server 2005.
So now, you have SQL Server 200 SP3 or SP4?
Can you also try registering replrec.dll? This should be in %ProgramFiles%\Microsoft SQL Server\80\COM directory and retry the synch please.|||June, Could you also please post the connection string you are using to connect to the server.|||Hi,
i'm using SP3a for my SQL Server 2000.
I registered the replrec.dll and re-sync..the error still remain
error messages:
initializing SQL Server Reconciler has failed
process could not connect to Distributor
SQL Server does not exist or access denied..
=(|||Few more questions:
1. Have youever synched successfully previously with this device (subscriber) and publisher?
2. Is this reinitializing?
3. What about permissions for snapshot folder and other items for IIS/SQL Server service. When you setup the virtual directory did you provide all the accounts permissions?|||
ok...my replication declaration:
private const string INTERNETURL = "http://localhost/Northwind/sscesa20.dll";
private const string PUBLISHERSERVER = "TWEEDLEDEE";
private const string PUBLISHERDATABASE = "Northwind";
private const SecurityType PUBLISHERSECURITYMODE =
SecurityType.NTAuthentication;
private const string PUBLICATION = "NorthwindProducts";
private string SUBSCRIBER = Dns.GetHostName();
private const string LOCALDATABASE = "\\My Documents\\products.sdf";
private const string CONNECTIONSTRING = "data source = " + LOCALDATABASE;
i do not sure is it my snapshot folder problem...i'm confuse to the snapshot folder that i created during creating my publication and during set up my virtual directory folder. When i create my publication, my snapshot is C:\Labs\Snapshot (i follow the tutorial)
However, when i set up my virtual directory and enter d same path (C:\Labs\Snapshot), it pop up a message said unable to found the file. Then i enter the snapshot folder as
\\computer_name\C$\Program Files\Microsoft SQL Server\MSSQL$TWEEDLEDEE\ReplData
HOWEVER, when i check out my snapshot location using Enterprise Server
there stated it as \\computer_name\C$\Program Files\Microsoft SQL Server\MSSQL$TWEEDLEDEE\REPLDATA
under generate snapshot in the following location
Friday, March 9, 2012
error mssqlserver
Hi all:
The errors always during the maintenance plan, and the last error we have is:
17066; SQL Server Assertion File:<page.cpp>, line=2831
Failed Assertion='spceContig>=Align (spaceNedded)'
What means?
Thank you.
Jose
Did you search KB and Google? Using below search words, I got a number of hits on Google:
SQL 17066
Often Assertion problems are bugs in LSQ server, but then can also be corruption problems in your
database. Run DBCC CHECKDB and also search KB etc and make sure you are current on service pack. If
that doesn't help, consider opening a case with MS Support.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:54AF2F6A-BA57-4309-BE62-C92BD56C4ABD@.microsoft.com...
> Hi all:
> The errors always during the maintenance plan, and the last error we have is:
> 17066; SQL Server Assertion File:<page.cpp>, line=2831
> Failed Assertion='spceContig>=Align (spaceNedded)'
> What means?
> Thank you.
> Jose
The errors always during the maintenance plan, and the last error we have is:
17066; SQL Server Assertion File:<page.cpp>, line=2831
Failed Assertion='spceContig>=Align (spaceNedded)'
What means?
Thank you.
Jose
Did you search KB and Google? Using below search words, I got a number of hits on Google:
SQL 17066
Often Assertion problems are bugs in LSQ server, but then can also be corruption problems in your
database. Run DBCC CHECKDB and also search KB etc and make sure you are current on service pack. If
that doesn't help, consider opening a case with MS Support.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:54AF2F6A-BA57-4309-BE62-C92BD56C4ABD@.microsoft.com...
> Hi all:
> The errors always during the maintenance plan, and the last error we have is:
> 17066; SQL Server Assertion File:<page.cpp>, line=2831
> Failed Assertion='spceContig>=Align (spaceNedded)'
> What means?
> Thank you.
> Jose
error mssqlserver
Hi all:
The errors always during the maintenance plan, and the last error we have is
:
17066; SQL Server Assertion File:<page.cpp>, line=2831
Failed Assertion='spceContig>=Align (spaceNedded)'
What means'
Thank you.
JoseDid you search KB and Google? Using below search words, I got a number of hi
ts on Google:
SQL 17066
Often Assertion problems are bugs in LSQ server, but then can also be corrup
tion problems in your
database. Run DBCC CHECKDB and also search KB etc and make sure you are curr
ent on service pack. If
that doesn't help, consider opening a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:54AF2F6A-BA57-4309-BE62-C92BD56C4ABD@.microsoft.com...
> Hi all:
> The errors always during the maintenance plan, and the last error we have
is:
> 17066; SQL Server Assertion File:<page.cpp>, line=2831
> Failed Assertion='spceContig>=Align (spaceNedded)'
> What means'
> Thank you.
> Jose
The errors always during the maintenance plan, and the last error we have is
:
17066; SQL Server Assertion File:<page.cpp>, line=2831
Failed Assertion='spceContig>=Align (spaceNedded)'
What means'
Thank you.
JoseDid you search KB and Google? Using below search words, I got a number of hi
ts on Google:
SQL 17066
Often Assertion problems are bugs in LSQ server, but then can also be corrup
tion problems in your
database. Run DBCC CHECKDB and also search KB etc and make sure you are curr
ent on service pack. If
that doesn't help, consider opening a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:54AF2F6A-BA57-4309-BE62-C92BD56C4ABD@.microsoft.com...
> Hi all:
> The errors always during the maintenance plan, and the last error we have
is:
> 17066; SQL Server Assertion File:<page.cpp>, line=2831
> Failed Assertion='spceContig>=Align (spaceNedded)'
> What means'
> Thank you.
> Jose
error mssqlserver
Hi all:
The errors always during the maintenance plan, and the last error we have is:
17066; SQL Server Assertion File:<page.cpp>, line=2831
Failed Assertion='spceContig>=Align (spaceNedded)'
What means'
Thank you.
JoseDid you search KB and Google? Using below search words, I got a number of hits on Google:
SQL 17066
Often Assertion problems are bugs in LSQ server, but then can also be corruption problems in your
database. Run DBCC CHECKDB and also search KB etc and make sure you are current on service pack. If
that doesn't help, consider opening a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:54AF2F6A-BA57-4309-BE62-C92BD56C4ABD@.microsoft.com...
> Hi all:
> The errors always during the maintenance plan, and the last error we have is:
> 17066; SQL Server Assertion File:<page.cpp>, line=2831
> Failed Assertion='spceContig>=Align (spaceNedded)'
> What means'
> Thank you.
> Jose
The errors always during the maintenance plan, and the last error we have is:
17066; SQL Server Assertion File:<page.cpp>, line=2831
Failed Assertion='spceContig>=Align (spaceNedded)'
What means'
Thank you.
JoseDid you search KB and Google? Using below search words, I got a number of hits on Google:
SQL 17066
Often Assertion problems are bugs in LSQ server, but then can also be corruption problems in your
database. Run DBCC CHECKDB and also search KB etc and make sure you are current on service pack. If
that doesn't help, consider opening a case with MS Support.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Jose Rojas" <JoseRojas@.discussions.microsoft.com> wrote in message
news:54AF2F6A-BA57-4309-BE62-C92BD56C4ABD@.microsoft.com...
> Hi all:
> The errors always during the maintenance plan, and the last error we have is:
> 17066; SQL Server Assertion File:<page.cpp>, line=2831
> Failed Assertion='spceContig>=Align (spaceNedded)'
> What means'
> Thank you.
> Jose
Wednesday, February 15, 2012
error message
I am getting an error message that I can't debug.
Processing Errors
An unexpected error occured in Report Processing.
Index was out of range. Must be non-negative and less than the size of the
collection. Parameter name: index
Now the problem, I am running reporting services off of a stored procedure,
that does not have an index or a parameter named index. Why am I getting
this error and how can I correct the problem?We will need some more information to narrow down why this is occurring.
Does this occur when
* Previewing the report
* Rendering the report on the server (if so which render)
* Exporting to Excel
* Some other place
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank" <Frank@.discussions.microsoft.com> wrote in message
news:A4EA56BF-2AF0-403F-89D7-F0F636CDA7DF@.microsoft.com...
> I am getting an error message that I can't debug.
> Processing Errors
> An unexpected error occured in Report Processing.
> Index was out of range. Must be non-negative and less than the size of
the
> collection. Parameter name: index
> Now the problem, I am running reporting services off of a stored
procedure,
> that does not have an index or a parameter named index. Why am I getting
> this error and how can I correct the problem?
>|||Try setting a datakeyfield?
"Bruce Johnson [MSFT]" wrote:
> We will need some more information to narrow down why this is occurring.
> Does this occur when
> * Previewing the report
> * Rendering the report on the server (if so which render)
> * Exporting to Excel
> * Some other place
>
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Frank" <Frank@.discussions.microsoft.com> wrote in message
> news:A4EA56BF-2AF0-403F-89D7-F0F636CDA7DF@.microsoft.com...
> > I am getting an error message that I can't debug.
> >
> > Processing Errors
> >
> > An unexpected error occured in Report Processing.
> > Index was out of range. Must be non-negative and less than the size of
> the
> > collection. Parameter name: index
> >
> > Now the problem, I am running reporting services off of a stored
> procedure,
> > that does not have an index or a parameter named index. Why am I getting
> > this error and how can I correct the problem?
> >
> >
>
>
Processing Errors
An unexpected error occured in Report Processing.
Index was out of range. Must be non-negative and less than the size of the
collection. Parameter name: index
Now the problem, I am running reporting services off of a stored procedure,
that does not have an index or a parameter named index. Why am I getting
this error and how can I correct the problem?We will need some more information to narrow down why this is occurring.
Does this occur when
* Previewing the report
* Rendering the report on the server (if so which render)
* Exporting to Excel
* Some other place
Bruce Johnson [MSFT]
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Frank" <Frank@.discussions.microsoft.com> wrote in message
news:A4EA56BF-2AF0-403F-89D7-F0F636CDA7DF@.microsoft.com...
> I am getting an error message that I can't debug.
> Processing Errors
> An unexpected error occured in Report Processing.
> Index was out of range. Must be non-negative and less than the size of
the
> collection. Parameter name: index
> Now the problem, I am running reporting services off of a stored
procedure,
> that does not have an index or a parameter named index. Why am I getting
> this error and how can I correct the problem?
>|||Try setting a datakeyfield?
"Bruce Johnson [MSFT]" wrote:
> We will need some more information to narrow down why this is occurring.
> Does this occur when
> * Previewing the report
> * Rendering the report on the server (if so which render)
> * Exporting to Excel
> * Some other place
>
> --
> Bruce Johnson [MSFT]
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Frank" <Frank@.discussions.microsoft.com> wrote in message
> news:A4EA56BF-2AF0-403F-89D7-F0F636CDA7DF@.microsoft.com...
> > I am getting an error message that I can't debug.
> >
> > Processing Errors
> >
> > An unexpected error occured in Report Processing.
> > Index was out of range. Must be non-negative and less than the size of
> the
> > collection. Parameter name: index
> >
> > Now the problem, I am running reporting services off of a stored
> procedure,
> > that does not have an index or a parameter named index. Why am I getting
> > this error and how can I correct the problem?
> >
> >
>
>
Subscribe to:
Posts (Atom)