Thursday, March 29, 2012
Error restoring sql backup
I was trying to restore a sql server backup in a Windows 2000 Advanced
Server cluster running SQL Server Enterprise Edition Service Pack 3, in two
nodes.
I have restored successfully some databases, buy I can not restore two
databases. I have obtained the error bellow:
Error 3241 Severity 16 State 1
The media family on device 'f:\backupsql\file.bak' is incorrectly formed.
SQL Server cannot process this media family.
I have tried the Microsoft Article Q297104, but the error continues.
Can anybody help me?
Thanks in advance,
Guillermo Roldan
Spain
Hi
I am not sure what is happening here, but if the KB article is not working,
and you have used the trace flag correctly, then you may want to try some of
the following:
viewing the header only,
restoring the backup onto a different machine,
check the cluster resources allow access to this drive and the files
destination of the MDF and LDF are available.
John
"Guillermo Roldan" <GuillermoRoldan@.discussions.microsoft.com> wrote in
message news:D840177A-3E92-4FB3-B3A9-60656A195E3A@.microsoft.com...
> Hi All,
> I was trying to restore a sql server backup in a Windows 2000 Advanced
> Server cluster running SQL Server Enterprise Edition Service Pack 3, in
> two
> nodes.
> I have restored successfully some databases, buy I can not restore two
> databases. I have obtained the error bellow:
> Error 3241 Severity 16 State 1
> The media family on device 'f:\backupsql\file.bak' is incorrectly formed.
> SQL Server cannot process this media family.
> I have tried the Microsoft Article Q297104, but the error continues.
> Can anybody help me?
> Thanks in advance,
> Guillermo Roldan
> Spain
>
|||Hi John,
I have tried to execute RESTORE HEADERONLY, resulting in an ***INCOMPLETE***
message. I do not understand, because I have checked maintenance plan every
day, and backups was OK. Now, there are only two backups, and there are
incomplete.
It is possible to recover an incomplete backup? There is a full database
backup, with no transactional log backups.
I would like to try the MSSQLRecovery tool on Monday…
Thanks for your answer, John
Guillermo Roldan
Spain
"John Bell" escribió:
> Hi
> I am not sure what is happening here, but if the KB article is not working,
> and you have used the trace flag correctly, then you may want to try some of
> the following:
> viewing the header only,
> restoring the backup onto a different machine,
> check the cluster resources allow access to this drive and the files
> destination of the MDF and LDF are available.
> John
> "Guillermo Roldan" <GuillermoRoldan@.discussions.microsoft.com> wrote in
> message news:D840177A-3E92-4FB3-B3A9-60656A195E3A@.microsoft.com...
>
>
|||Hi
I can only think that it may be disc corruption, although I would have
expected you to have other things to indicate such a failure. If you
have a backup elsewhere you may want to try that, if not a call to PSS
may required.
John
|||Hi John,
I have discover why it is an Incomplete backup. The tape-robot was offline
since 22/11/2005 because a hardware problem, so somebody copy the sql server
backup files to a Novell Netware share. This is the problem: This Novell
Netware share has a limit of 4.194.304 KB. But the real backup was about
8,5GB !!
Finally, i can restore a new backup from tape. This new backup it's older
(18/11/2005), but it run sucesfully !
Thanks John, for your answers
Guillermo Roldan
"John Bell" wrote:
> Hi
> I can only think that it may be disc corruption, although I would have
> expected you to have other things to indicate such a failure. If you
> have a backup elsewhere you may want to try that, if not a call to PSS
> may required.
> John
>
sql
Error restoring sql backup
I was trying to restore a sql server backup in a Windows 2000 Advanced
Server cluster running SQL Server Enterprise Edition Service Pack 3, in two
nodes.
I have restored successfully some databases, buy I can not restore two
databases. I have obtained the error bellow:
Error 3241 Severity 16 State 1
The media family on device 'f:\backupsql\file.bak' is incorrectly formed.
SQL Server cannot process this media family.
I have tried the Microsoft Article Q297104, but the error continues.
Can anybody help me?
Thanks in advance,
Guillermo Roldan
SpainHi
I am not sure what is happening here, but if the KB article is not working,
and you have used the trace flag correctly, then you may want to try some of
the following:
viewing the header only,
restoring the backup onto a different machine,
check the cluster resources allow access to this drive and the files
destination of the MDF and LDF are available.
John
"Guillermo Roldan" <GuillermoRoldan@.discussions.microsoft.com> wrote in
message news:D840177A-3E92-4FB3-B3A9-60656A195E3A@.microsoft.com...
> Hi All,
> I was trying to restore a sql server backup in a Windows 2000 Advanced
> Server cluster running SQL Server Enterprise Edition Service Pack 3, in
> two
> nodes.
> I have restored successfully some databases, buy I can not restore two
> databases. I have obtained the error bellow:
> Error 3241 Severity 16 State 1
> The media family on device 'f:\backupsql\file.bak' is incorrectly formed.
> SQL Server cannot process this media family.
> I have tried the Microsoft Article Q297104, but the error continues.
> Can anybody help me?
> Thanks in advance,
> Guillermo Roldan
> Spain
>|||Hi John,
I have tried to execute RESTORE HEADERONLY, resulting in an ***INCOMPLETE***
message. I do not understand, because I have checked maintenance plan every
day, and backups was OK. Now, there are only two backups, and there are
incomplete.
It is possible to recover an incomplete backup? There is a full database
backup, with no transactional log backups.
I would like to try the MSSQLRecovery tool on Mondayâ?¦
Thanks for your answer, John
Guillermo Roldan
Spain
"John Bell" escribió:
> Hi
> I am not sure what is happening here, but if the KB article is not working,
> and you have used the trace flag correctly, then you may want to try some of
> the following:
> viewing the header only,
> restoring the backup onto a different machine,
> check the cluster resources allow access to this drive and the files
> destination of the MDF and LDF are available.
> John
> "Guillermo Roldan" <GuillermoRoldan@.discussions.microsoft.com> wrote in
> message news:D840177A-3E92-4FB3-B3A9-60656A195E3A@.microsoft.com...
> > Hi All,
> >
> > I was trying to restore a sql server backup in a Windows 2000 Advanced
> > Server cluster running SQL Server Enterprise Edition Service Pack 3, in
> > two
> > nodes.
> >
> > I have restored successfully some databases, buy I can not restore two
> > databases. I have obtained the error bellow:
> >
> > Error 3241 Severity 16 State 1
> > The media family on device 'f:\backupsql\file.bak' is incorrectly formed.
> > SQL Server cannot process this media family.
> >
> > I have tried the Microsoft Article Q297104, but the error continues.
> >
> > Can anybody help me?
> >
> > Thanks in advance,
> > Guillermo Roldan
> > Spain
> >
>
>|||Hi
I can only think that it may be disc corruption, although I would have
expected you to have other things to indicate such a failure. If you
have a backup elsewhere you may want to try that, if not a call to PSS
may required.
John|||Hi John,
I have discover why it is an Incomplete backup. The tape-robot was offline
since 22/11/2005 because a hardware problem, so somebody copy the sql server
backup files to a Novell Netware share. This is the problem: This Novell
Netware share has a limit of 4.194.304 KB. But the real backup was about
8,5GB !!
Finally, i can restore a new backup from tape. This new backup it's older
(18/11/2005), but it run sucesfully !
Thanks John, for your answers
Guillermo Roldan
"John Bell" wrote:
> Hi
> I can only think that it may be disc corruption, although I would have
> expected you to have other things to indicate such a failure. If you
> have a backup elsewhere you may want to try that, if not a call to PSS
> may required.
> John
>
Error restoring sql backup
I was trying to restore a sql server backup in a Windows 2000 Advanced
Server cluster running SQL Server Enterprise Edition Service Pack 3, in two
nodes.
I have restored successfully some databases, buy I can not restore two
databases. I have obtained the error bellow:
Error 3241 Severity 16 State 1
The media family on device 'f:\backupsql\file.bak' is incorrectly formed.
SQL Server cannot process this media family.
I have tried the Microsoft Article Q297104, but the error continues.
Can anybody help me?
Thanks in advance,
Guillermo Roldan
SpainHi
I am not sure what is happening here, but if the KB article is not working,
and you have used the trace flag correctly, then you may want to try some of
the following:
viewing the header only,
restoring the backup onto a different machine,
check the cluster resources allow access to this drive and the files
destination of the MDF and LDF are available.
John
"Guillermo Roldan" <GuillermoRoldan@.discussions.microsoft.com> wrote in
message news:D840177A-3E92-4FB3-B3A9-60656A195E3A@.microsoft.com...
> Hi All,
> I was trying to restore a sql server backup in a Windows 2000 Advanced
> Server cluster running SQL Server Enterprise Edition Service Pack 3, in
> two
> nodes.
> I have restored successfully some databases, buy I can not restore two
> databases. I have obtained the error bellow:
> Error 3241 Severity 16 State 1
> The media family on device 'f:\backupsql\file.bak' is incorrectly formed.
> SQL Server cannot process this media family.
> I have tried the Microsoft Article Q297104, but the error continues.
> Can anybody help me?
> Thanks in advance,
> Guillermo Roldan
> Spain
>|||Hi John,
I have tried to execute RESTORE HEADERONLY, resulting in an ***INCOMPLETE***
message. I do not understand, because I have checked maintenance plan every
day, and backups was OK. Now, there are only two backups, and there are
incomplete.
It is possible to recover an incomplete backup? There is a full database
backup, with no transactional log backups.
I would like to try the MSSQLRecovery tool on Monday…
Thanks for your answer, John
Guillermo Roldan
Spain
"John Bell" escribió:
> Hi
> I am not sure what is happening here, but if the KB article is not working
,
> and you have used the trace flag correctly, then you may want to try some
of
> the following:
> viewing the header only,
> restoring the backup onto a different machine,
> check the cluster resources allow access to this drive and the files
> destination of the MDF and LDF are available.
> John
> "Guillermo Roldan" <GuillermoRoldan@.discussions.microsoft.com> wrote in
> message news:D840177A-3E92-4FB3-B3A9-60656A195E3A@.microsoft.com...
>
>|||Hi
I can only think that it may be disc corruption, although I would have
expected you to have other things to indicate such a failure. If you
have a backup elsewhere you may want to try that, if not a call to PSS
may required.
John|||Hi John,
I have discover why it is an Incomplete backup. The tape-robot was offline
since 22/11/2005 because a hardware problem, so somebody copy the sql server
backup files to a Novell Netware share. This is the problem: This Novell
Netware share has a limit of 4.194.304 KB. But the real backup was about
8,5GB !!
Finally, i can restore a new backup from tape. This new backup it's older
(18/11/2005), but it run sucesfully !
Thanks John, for your answers
Guillermo Roldan
"John Bell" wrote:
> Hi
> I can only think that it may be disc corruption, although I would have
> expected you to have other things to indicate such a failure. If you
> have a backup elsewhere you may want to try that, if not a call to PSS
> may required.
> John
>
Error replication agent is not registered properly
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
>
Error Rendering SSRS Reports via SOAP
server. The configuration has been unchanged for approx. 3 weeks. Suddenly
over the last two days, reports being accessed via an ASP.NET 2.0 application
(on Windows 2003 Server with IIS 6) using a SOAP call to the reportserver
became inaccessable. End users received the following error:
********************************************************
Message: An error occurred during rendering of the report. -->
An error occurred during rendering of the report. -->
An error occurred during rendering of the report. -->
An error occurred during rendering of the report. -->
Attempted to read or write protected memory. This is often an indication
that other memory is corrupt.
Stack Trace: at
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
methodName, Object[] parameters)
at IFA.CAP.SQLReportingService.ReportingService.Render(String Report,
String Format, String HistoryID, String DeviceInfo, ParameterValue[]
Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle,
String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed,
Warning[]& Warnings, String[]& StreamIds) in C:\Applications\IFACAP\Web
References\SQLReportingService\Reference.vb:line 1319
at IFA.CAP.BusinessObjects.Reports.Certificate(Int32 certificateID,
Boolean isDraft, Boolean isCertified) in
C:\Applications\IFACAP\BusinessObjects\IFA.CAP.BusinessObjects.Report.vb:line
551
at IFA.CAP.CertificateDetail.PrintCertificate(Object sender, EventArgs e)
in C:\Applications\IFACAP\Main\CertificateDetail.aspx.vb:line 2287
********************************************************
A short term resolution has been to perform iisrest on the ReportServer.
However, the problem reappears later at random intervals.
This only seems to be an issue with reports being called using SOAP.
Reports being rendering in the .NET Report Viewer control appear unaffected.
Here is some sample code to illustrate how we call some of our reports from
ASP.NET through the SSRS web service:
************************************************************
Private callback As New
System.Net.Security.RemoteCertificateValidationCallback(AddressOf
RemoteCertificateValidationCallback)
Private Function RemoteCertificateValidationCallback(ByVal sender As Object, _
ByVal cert As
System.Security.Cryptography.X509Certificates.X509Certificate, _
ByVal chain As
System.Security.Cryptography.X509Certificates.X509Chain, _
ByVal sslPolicyErrors As System.Net.Security.SslPolicyErrors) As Boolean
Return True
End Function
Sub RenderReport()
Dim rs As New SQLReportingService.ReportingService
Dim results As [Byte]() = Nothing
System.Net.ServicePointManager.ServerCertificateValidationCallback = callback
rs.Credentials = New System.Net.NetworkCredential("User", "Password",
"Domain")
results = rs.Render(String.Concat("TargerFolder", "ReportName"), "PDF",
Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing,
Nothing, Nothing)
Response.Clear()
Response.Buffer = True
Response.Expires = 0
Response.ContentType = "application/pdf"
Response.AppendHeader("Content-Disposition", "attachment;
filename=Report.pdf")
Response.BinaryWrite(results)
Response.End()
End Sub
************************************************************
Does anyone see a problem with the above code. It has been in production
for 3 weeks now and has been working fine until yesterday. Any help would be
greatly appreciated!Try running memtest: www.memtest.org. You may have bad memory.
"mjorangehawk" wrote:
> I am running SQL Reporting Services and SQL Server 2005 on a Windows 2003
> server. The configuration has been unchanged for approx. 3 weeks. Suddenly
> over the last two days, reports being accessed via an ASP.NET 2.0 application
> (on Windows 2003 Server with IIS 6) using a SOAP call to the reportserver
> became inaccessable. End users received the following error:
> ********************************************************
> Message: An error occurred during rendering of the report. -->
> An error occurred during rendering of the report. -->
> An error occurred during rendering of the report. -->
> An error occurred during rendering of the report. -->
> Attempted to read or write protected memory. This is often an indication
> that other memory is corrupt.
> Stack Trace: at
> System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
> at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> methodName, Object[] parameters)
> at IFA.CAP.SQLReportingService.ReportingService.Render(String Report,
> String Format, String HistoryID, String DeviceInfo, ParameterValue[]
> Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle,
> String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed,
> Warning[]& Warnings, String[]& StreamIds) in C:\Applications\IFACAP\Web
> References\SQLReportingService\Reference.vb:line 1319
> at IFA.CAP.BusinessObjects.Reports.Certificate(Int32 certificateID,
> Boolean isDraft, Boolean isCertified) in
> C:\Applications\IFACAP\BusinessObjects\IFA.CAP.BusinessObjects.Report.vb:line
> 551
> at IFA.CAP.CertificateDetail.PrintCertificate(Object sender, EventArgs e)
> in C:\Applications\IFACAP\Main\CertificateDetail.aspx.vb:line 2287
> ********************************************************
> A short term resolution has been to perform iisrest on the ReportServer.
> However, the problem reappears later at random intervals.
> This only seems to be an issue with reports being called using SOAP.
> Reports being rendering in the .NET Report Viewer control appear unaffected.
> Here is some sample code to illustrate how we call some of our reports from
> ASP.NET through the SSRS web service:
> ************************************************************
> Private callback As New
> System.Net.Security.RemoteCertificateValidationCallback(AddressOf
> RemoteCertificateValidationCallback)
> Private Function RemoteCertificateValidationCallback(ByVal sender As Object, _
> ByVal cert As
> System.Security.Cryptography.X509Certificates.X509Certificate, _
> ByVal chain As
> System.Security.Cryptography.X509Certificates.X509Chain, _
> ByVal sslPolicyErrors As System.Net.Security.SslPolicyErrors) As Boolean
> Return True
> End Function
>
> Sub RenderReport()
> Dim rs As New SQLReportingService.ReportingService
> Dim results As [Byte]() = Nothing
> System.Net.ServicePointManager.ServerCertificateValidationCallback = callback
> rs.Credentials = New System.Net.NetworkCredential("User", "Password",
> "Domain")
> results = rs.Render(String.Concat("TargerFolder", "ReportName"), "PDF",
> Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing,
> Nothing, Nothing)
>
> Response.Clear()
> Response.Buffer = True
> Response.Expires = 0
> Response.ContentType = "application/pdf"
> Response.AppendHeader("Content-Disposition", "attachment;
> filename=Report.pdf")
> Response.BinaryWrite(results)
> Response.End()
> End Sub
> ************************************************************
> Does anyone see a problem with the above code. It has been in production
> for 3 weeks now and has been working fine until yesterday. Any help would be
> greatly appreciated!
>|||Actually, it turns out the problem was related to a database image that was
being loaded into the report dynamically. The image control on the report
had a MIME type of jpg but we had a few cases of images that had been
inserted into the database as TIF's. Once we replaced those with JPG
versions the problem went away.
"breno" wrote:
> Try running memtest: www.memtest.org. You may have bad memory.
> "mjorangehawk" wrote:
> > I am running SQL Reporting Services and SQL Server 2005 on a Windows 2003
> > server. The configuration has been unchanged for approx. 3 weeks. Suddenly
> > over the last two days, reports being accessed via an ASP.NET 2.0 application
> > (on Windows 2003 Server with IIS 6) using a SOAP call to the reportserver
> > became inaccessable. End users received the following error:
> >
> > ********************************************************
> >
> > Message: An error occurred during rendering of the report. -->
> > An error occurred during rendering of the report. -->
> > An error occurred during rendering of the report. -->
> > An error occurred during rendering of the report. -->
> > Attempted to read or write protected memory. This is often an indication
> > that other memory is corrupt.
> >
> > Stack Trace: at
> > System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
> > at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String
> > methodName, Object[] parameters)
> > at IFA.CAP.SQLReportingService.ReportingService.Render(String Report,
> > String Format, String HistoryID, String DeviceInfo, ParameterValue[]
> > Parameters, DataSourceCredentials[] Credentials, String ShowHideToggle,
> > String& Encoding, String& MimeType, ParameterValue[]& ParametersUsed,
> > Warning[]& Warnings, String[]& StreamIds) in C:\Applications\IFACAP\Web
> > References\SQLReportingService\Reference.vb:line 1319
> > at IFA.CAP.BusinessObjects.Reports.Certificate(Int32 certificateID,
> > Boolean isDraft, Boolean isCertified) in
> > C:\Applications\IFACAP\BusinessObjects\IFA.CAP.BusinessObjects.Report.vb:line
> > 551
> > at IFA.CAP.CertificateDetail.PrintCertificate(Object sender, EventArgs e)
> > in C:\Applications\IFACAP\Main\CertificateDetail.aspx.vb:line 2287
> >
> > ********************************************************
> >
> > A short term resolution has been to perform iisrest on the ReportServer.
> > However, the problem reappears later at random intervals.
> >
> > This only seems to be an issue with reports being called using SOAP.
> > Reports being rendering in the .NET Report Viewer control appear unaffected.
> >
> > Here is some sample code to illustrate how we call some of our reports from
> > ASP.NET through the SSRS web service:
> >
> > ************************************************************
> >
> > Private callback As New
> > System.Net.Security.RemoteCertificateValidationCallback(AddressOf
> > RemoteCertificateValidationCallback)
> >
> > Private Function RemoteCertificateValidationCallback(ByVal sender As Object, _
> > ByVal cert As
> > System.Security.Cryptography.X509Certificates.X509Certificate, _
> > ByVal chain As
> > System.Security.Cryptography.X509Certificates.X509Chain, _
> > ByVal sslPolicyErrors As System.Net.Security.SslPolicyErrors) As Boolean
> >
> > Return True
> >
> > End Function
> >
> >
> > Sub RenderReport()
> > Dim rs As New SQLReportingService.ReportingService
> > Dim results As [Byte]() = Nothing
> >
> > System.Net.ServicePointManager.ServerCertificateValidationCallback = callback
> >
> > rs.Credentials = New System.Net.NetworkCredential("User", "Password",
> > "Domain")
> >
> > results = rs.Render(String.Concat("TargerFolder", "ReportName"), "PDF",
> > Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing, Nothing,
> > Nothing, Nothing)
> >
> >
> > Response.Clear()
> > Response.Buffer = True
> > Response.Expires = 0
> > Response.ContentType = "application/pdf"
> > Response.AppendHeader("Content-Disposition", "attachment;
> > filename=Report.pdf")
> > Response.BinaryWrite(results)
> > Response.End()
> > End Sub
> >
> > ************************************************************
> >
> > Does anyone see a problem with the above code. It has been in production
> > for 3 weeks now and has been working fine until yesterday. Any help would be
> > greatly appreciated!
> >
Monday, March 26, 2012
Error output logic
Hello,
I have a simple SSIS package running under SQL 2005 SP2a.
In the data flow, I have several lookup transforms with error outputs. Each error output links to its own audit transform and then writes data to its own flat file destination.
After the data flow is complete, my control flow will then use a ForEach file container to mail the flat files to the source system data owners with a message about incomplete/inconsistent source data. I am effectively providing feedback to the source owners so that we may improve the quality of data that gets sent to us.
My problem is that the flat file (which contains the offending rows) seems to get created everytime even when there were no errors in the lookup in question. Thus my ForEach container will always send a mail to the data source teams even if there were no errors as the error flat file will always exist albeit empty.
How can I stop this happening? How can I only create flat files when there really were errors? How can I prevent the source teams from receiving feedback emails when there is no reason to?
Thanks in advance
MGale1
Error Output for SQL Server Destination
I'm in the process of running some tests to determine which method is faster...
I created a data flow task OleDB Source -> Data Conversion -> OleDb Destination. Error outputs from the OleDB destination is sent to a flat file destination. This works great.
I'm importing millons of rows and found that using SQL Server Destination (local) is much faster than the OleDB Destination. However, I have not figured out how to output errors to a flat file destination like I did when using the OleDB destination.
Is there any way to trap errors in a flat file when using a SQL Server Destination?
Thanks!
NLC
OK..I found the answer to my problem. Books online indicates that SQL Server destination does not support an error output. I guess I'll have to use OleDB destination instead.
NLC
Error opening table in Windows 2003
I can create tables, indexes, etc. in SQL Enterprise
Manager. But I'm unable to open a table to view the data
in SQL Enterprise Manager. It give me the following
error message: Provider cannot be found. It may not be
properly installed.
I've uninstalled SQL Server 2000 and re-installed it with
SP3 but still running into the same problem.
Anyone know what's going on or have any idea to correct
this error?
ThanksDid you try using Query Analyzer? How are you connecting to SQL Server
service (windows auth, sql auth)?
<tchen@.ceira.com> wrote in message
news:03a901c399be$c3fb7b20$a601280a@.phx.gbl...
> I'm running SQL Server 2000 SP3 on Windows 2003 Server.
> I can create tables, indexes, etc. in SQL Enterprise
> Manager. But I'm unable to open a table to view the data
> in SQL Enterprise Manager. It give me the following
> error message: Provider cannot be found. It may not be
> properly installed.
> I've uninstalled SQL Server 2000 and re-installed it with
> SP3 but still running into the same problem.
> Anyone know what's going on or have any idea to correct
> this error?
> Thanks
Error opening Management Studio (Express)
Hello all,
I'm having an error opening the SSMS Express on a machine. This is a new install on this machine, so i've never had this running. However, i've install SSMSE many times and this is the first error that I've come across. I have the minimum requirements on the machine (Framework, XML, Windows Installer)
The error is:
Header: "Microsoft .Net Framework"
"Unhandled exception has occured in a component in your application. If you click Continue, the application will igonore this error and attempt to continue.
Attempted to read or write protected memory. This is often an indication that the other memory is corrupt"
(Details at end of post)
Now what this machine is running is:
OS: SBS 2003 SP1
Memory: 1.5 GB (over 1 GB is free)
Hard Disk: 7 GB of free space
Windows Updates are done up to just before SP2
SQL Server Express (SP2) is installed on this machine.
SSMSE Version: 3042
What I've done trying to resolve this issue:
1) reboot the machine
2) apply remaining windows updates (save for W2K3 SP2)
3) Re-install of SSMSE
4) Re-download of SSMSE install package and an uninstall & reinstall
5) Repair of .Net Framework 2.0
6) Repair of SQL Native Client
I'm not sure what to attempt next, if anyone can give me any insite at all, that would be great. All I did was install the requirements, install SQL Server Express SP2, then install SSMSE. This has worked in the past for me.
Any and all help greatly appreciated!!
Thanks,
Ryan
Note: here is the stack track that the application generates:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Drawing.SafeNativeMethods.Gdip.GdipGetLogFontW(HandleRef font, HandleRef graphics, Object lf)
at System.Drawing.Font.ToLogFont(Object logFont, Graphics graphics)
at System.Drawing.Font.ToLogFont(Object logFont)
at System.Drawing.Font.ToHfont()
at System.Windows.Forms.Control.FontHandleWrapper..ctor(Font font)
at System.Windows.Forms.Control.get_FontHandle()
at System.Windows.Forms.Control.SetWindowFont()
at System.Windows.Forms.Control.OnHandleCreated(EventArgs e)
at System.Windows.Forms.TreeView.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LazyTreeView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
-
Microsoft.SqlServer.Express.AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.AppIDPackage.DLL
-
Microsoft.SqlServer.Express.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.VSIntegration.DLL
-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
-
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
-
Microsoft.SqlServer.Express.SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlWorkbench.Interfaces.DLL
-
Microsoft.SqlServer.Express.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlTDiagM.DLL
-
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
-
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
-
Microsoft.SqlServer.Express.ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ObjectExplorer.DLL
-
Microsoft.SqlServer.Express.SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlMgmt.DLL
-
Microsoft.SqlServer.Express.ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ConnectionDlg.DLL
-
Microsoft.VisualStudio
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 built by: RTM
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.dll
-
Microsoft.VisualStudio.Shell
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.dll
-
Microsoft.VisualStudio.Shell.Interop.8.0
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop.8.0/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.8.0.dll
-
System.Drawing.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
-
Microsoft.VisualStudio.Designer.Interfaces
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Designer.Interfaces/1.0.5000.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Designer.Interfaces.dll
-
Microsoft.SqlServer.Express.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.RegSvrEnum.DLL
-
Microsoft.SqlServer.Express.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.CustomControls.DLL
-
Microsoft.SqlServer.Express.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.Smo.DLL
-
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
-
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
--
**********************************************************************************************
--
To me that looks like a problem with the .NET framework. Try doing a full reinstall of the framework.
You might want to ask in one of the .NET forums and see if they can shead any light.
|||That's what I thought too, so I ended up uninstalling the framework, rebooting, and reinstalling. No issues on the reinstall.
Still the error exists. However, I have found that I get errors in the SQL Surface Area Configuration Wizard as well. I'm assuming this runs off the ".NET Framework" as well. I've read some issues with this happening with some .NET controls, but I'm assuming that these are working fine as this seems to be the only machine with these issues. What concerns me is that if SQL Server uses any of hte .NET framework (besides the CLR) then I'm not sure if I want to continue on this machine.
Any ideas on what do look for?
|||Ok, i'm convinced that this is an issue with .NET framework on this machine. It seems to be related to the System.Drawing DLL. I can get into the program but, it'll throw another error if I right click, however, this error comes from System.Drawing.Font
I'm going to move this thread to under a .NET Thread.
Thanks,
|||Moved to:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1
|||
Ryan Slimmon wrote:
Moved to:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1
Any update on this issue - I am getting same message when trying to import SQL 2000 Server registration details
Error opening Management Studio (Express)
Hello all,
I'm having an error opening the SSMS Express on a machine. This is a new install on this machine, so i've never had this running. However, i've install SSMSE many times and this is the first error that I've come across. I have the minimum requirements on the machine (Framework, XML, Windows Installer)
The error is:
Header: "Microsoft .Net Framework"
"Unhandled exception has occured in a component in your application. If you click Continue, the application will igonore this error and attempt to continue.
Attempted to read or write protected memory. This is often an indication that the other memory is corrupt"
(Details at end of post)
Now what this machine is running is:
OS: SBS 2003 SP1
Memory: 1.5 GB (over 1 GB is free)
Hard Disk: 7 GB of free space
Windows Updates are done up to just before SP2
SQL Server Express (SP2) is installed on this machine.
SSMSE Version: 3042
What I've done trying to resolve this issue:
1) reboot the machine
2) apply remaining windows updates (save for W2K3 SP2)
3) Re-install of SSMSE
4) Re-download of SSMSE install package and an uninstall & reinstall
5) Repair of .Net Framework 2.0
6) Repair of SQL Native Client
I'm not sure what to attempt next, if anyone can give me any insite at all, that would be great. All I did was install the requirements, install SQL Server Express SP2, then install SSMSE. This has worked in the past for me.
Any and all help greatly appreciated!!
Thanks,
Ryan
Note: here is the stack track that the application generates:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
at System.Drawing.SafeNativeMethods.Gdip.GdipGetLogFontW(HandleRef font, HandleRef graphics, Object lf)
at System.Drawing.Font.ToLogFont(Object logFont, Graphics graphics)
at System.Drawing.Font.ToLogFont(Object logFont)
at System.Drawing.Font.ToHfont()
at System.Windows.Forms.Control.FontHandleWrapper..ctor(Font font)
at System.Windows.Forms.Control.get_FontHandle()
at System.Windows.Forms.Control.SetWindowFont()
at System.Windows.Forms.Control.OnHandleCreated(EventArgs e)
at System.Windows.Forms.TreeView.OnHandleCreated(EventArgs e)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.LazyTreeView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
-
Microsoft.SqlServer.Express.AppIDPackage
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.AppIDPackage.DLL
-
Microsoft.SqlServer.Express.VSIntegration
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.VSIntegration.DLL
-
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
-
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
-
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.0.4054
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
-
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
-
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
-
Microsoft.SqlServer.Express.SqlWorkbench.Interfaces
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlWorkbench.Interfaces.DLL
-
Microsoft.SqlServer.Express.SqlTDiagM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlTDiagM.DLL
-
Microsoft.DataWarehouse.SQM
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
-
Microsoft.SqlServer.Instapi
Assembly Version: 9.0.242.0
Win32 Version: 9.00.1399.00
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/9.0.242.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
-
Microsoft.SqlServer.Express.ObjectExplorer
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ObjectExplorer.DLL
-
Microsoft.SqlServer.Express.SqlMgmt
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.SqlMgmt.DLL
-
Microsoft.SqlServer.Express.ConnectionDlg
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.ConnectionDlg.DLL
-
Microsoft.VisualStudio
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 built by: RTM
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.dll
-
Microsoft.VisualStudio.Shell
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.dll
-
Microsoft.VisualStudio.Shell.Interop.8.0
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Shell.Interop.8.0/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.8.0.dll
-
System.Drawing.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
-
Microsoft.VisualStudio.Designer.Interfaces
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///C:/WINDOWS/assembly/GAC/Microsoft.VisualStudio.Designer.Interfaces/1.0.5000.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Designer.Interfaces.dll
-
Microsoft.SqlServer.Express.RegSvrEnum
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.RegSvrEnum.DLL
-
Microsoft.SqlServer.Express.CustomControls
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.CustomControls.DLL
-
Microsoft.SqlServer.Express.Smo
Assembly Version: 9.0.242.0
Win32 Version: 9.00.3042.00
CodeBase: file:///C:/Program%20Files/Microsoft%20SQL%20Server/90/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Express.Smo.DLL
-
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.42 (RTM.050727-4200)
CodeBase: file:///C:/WINDOWS/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
-
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
--
**********************************************************************************************
--
To me that looks like a problem with the .NET framework. Try doing a full reinstall of the framework.
You might want to ask in one of the .NET forums and see if they can shead any light.
|||That's what I thought too, so I ended up uninstalling the framework, rebooting, and reinstalling. No issues on the reinstall.
Still the error exists. However, I have found that I get errors in the SQL Surface Area Configuration Wizard as well. I'm assuming this runs off the ".NET Framework" as well. I've read some issues with this happening with some .NET controls, but I'm assuming that these are working fine as this seems to be the only machine with these issues. What concerns me is that if SQL Server uses any of hte .NET framework (besides the CLR) then I'm not sure if I want to continue on this machine.
Any ideas on what do look for?
|||Ok, i'm convinced that this is an issue with .NET framework on this machine. It seems to be related to the System.Drawing DLL. I can get into the program but, it'll throw another error if I right click, however, this error comes from System.Drawing.Font
I'm going to move this thread to under a .NET Thread.
Thanks,
|||Moved to:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1
|||
Ryan Slimmon wrote:
Moved to:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1679733&SiteID=1&mode=1
Any update on this issue - I am getting same message when trying to import SQL 2000 Server registration details
sqlFriday, March 23, 2012
error on sp3a URGENT HELP !
This script performs quite a bit of modifications to the system tables including dropping and recreating of sysprocesses table.
Wednesday, March 21, 2012
Error on one of SQL Reporting Services Samples
I am running the reports that comes with the samples one and I'm getting
this error when I run this code;
="SELECT c.firstname, c.lastname, e.title, d.departmentID " &
"From HumanResources.EmployeeDepartmentHistory D " &
"INNER JOIN HumanResources.Employee E " &
"ON D.EmployeeID = E.EmployeeID " &
"INNER JOIN Person.Contact C " &
"ON E.ContactID = C.ContactID " &
Iif(Parameters!Department.Value = 0, "", "WHERE D.DepartmentID = " &
Parameters!Department.Value) &
"ORDER BY C.LastName"
The error is saying that all those columns can not be bounded. can anybody
tells me where the error is this piece of code?
Thanks very much in advance.
Midway.The IIF in there is for internal RS expressions and not T-SQL. This appears
to have been modified ('). Which report and dataset is this from?
SalesEmps within the Employee Sales Summary report looks similiar:
SELECT E.EmployeeID, C.FirstName + N' ' + C.LastName AS Employee
FROM HumanResources.Employee E INNER JOIN
Sales.SalesPerson SP ON E.EmployeeID = SP.SalesPersonID INNER JOIN
Person.Contact C ON E.ContactID = C.ContactID
ORDER BY C.LastName, C.FirstName
RDA Corp
Business Intelligence Evangelist Leader
www.rdacorp.com
"Midway" wrote:
> Hi there,
> I am running the reports that comes with the samples one and I'm getting
> this error when I run this code;
> ="SELECT c.firstname, c.lastname, e.title, d.departmentID " &
> "From HumanResources.EmployeeDepartmentHistory D " &
> "INNER JOIN HumanResources.Employee E " &
> "ON D.EmployeeID = E.EmployeeID " &
> "INNER JOIN Person.Contact C " &
> "ON E.ContactID = C.ContactID " &
> Iif(Parameters!Department.Value = 0, "", "WHERE D.DepartmentID = " &
> Parameters!Department.Value) &
> "ORDER BY C.LastName"
> The error is saying that all those columns can not be bounded. can anybody
> tells me where the error is this piece of code?
> Thanks very much in advance.
> Midway.
Error on MSDTC on win2k3 to win2k
I have two servers, one running win2k3 server and the other running win2k
advanced server. Both are also running MSSQL2k.
I have a script that runs on the win2k3 server, that updates one of it's
tables, based on information accessed through a linked server to the win2k
machine. No updating is done to the win2k machine, only selection. All
updates occur to the data on the win2k3 machine, which is were the script is
running.
When I execute this script, I get the following error.
"New transaction cannot enlist in the specified transaction coordinator"
When both machines are win2k, this works without any problem.
Both servers have a linked server connection to each other. All other
scripts that work across this link work fine, as long as they are not in a
transaction.
I am running out of ideas on how to get this working, does anyone have any
ideas. Any assistance would be greatly appreciated.
Thank you
Clint Colefax
I would say it is pretty likely DTC is turned off on the Win2003 machine but
here are some things that come up in the KB search:
http://support.microsoft.com/default...&Product=sql2k
http://support.microsoft.com/default...&Product=sql2k
http://support.microsoft.com/default...&Product=sql2k
http://support.microsoft.com/default...&Product=sql2k
Andrew J. Kelly SQL MVP
"Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
news:4E379DAB-38A2-4034-9196-8C5B605A2193@.microsoft.com...
> I am currently having issue with MSDTC.
> I have two servers, one running win2k3 server and the other running win2k
> advanced server. Both are also running MSSQL2k.
> I have a script that runs on the win2k3 server, that updates one of it's
> tables, based on information accessed through a linked server to the win2k
> machine. No updating is done to the win2k machine, only selection. All
> updates occur to the data on the win2k3 machine, which is were the script
is
> running.
> When I execute this script, I get the following error.
> "New transaction cannot enlist in the specified transaction coordinator"
> When both machines are win2k, this works without any problem.
> Both servers have a linked server connection to each other. All other
> scripts that work across this link work fine, as long as they are not in a
> transaction.
> I am running out of ideas on how to get this working, does anyone have any
> ideas. Any assistance would be greatly appreciated.
> Thank you
> Clint Colefax
|||Thank you for your response.
DTC is running on both servers, that was the first thing I checked. The 3
three knowledge base article below I have tried, most of these settings were
already set, or in the case of the win2k machine, do not exist. Many of the
security settings for DTC were added Win2k3. But I have read article stating
that this security is ignored if one of the machines is detected as Win2k.
I will look into the 3rd article.
If you have any other idea, they would be greatly appreciated.
Thank you
Clint Colefax
"Andrew J. Kelly" wrote:
> I would say it is pretty likely DTC is turned off on the Win2003 machine but
> here are some things that come up in the KB search:
> http://support.microsoft.com/default...&Product=sql2k
> http://support.microsoft.com/default...&Product=sql2k
> http://support.microsoft.com/default...&Product=sql2k
> http://support.microsoft.com/default...&Product=sql2k
>
> --
> Andrew J. Kelly SQL MVP
>
> "Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
> news:4E379DAB-38A2-4034-9196-8C5B605A2193@.microsoft.com...
> is
>
>
|||Sorry those would have been my guess. If no one else pipes up you might
want to give MS PSS a call. Even if it isn't a bug it might be worth the
$250.00 or so to get the systems up as soon as possible.
http://support.microsoft.com/default...d=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
news:0AEBF2EC-9455-47B1-BB30-56F41CB100D0@.microsoft.com...
> Thank you for your response.
> DTC is running on both servers, that was the first thing I checked. The 3
> three knowledge base article below I have tried, most of these settings
were
> already set, or in the case of the win2k machine, do not exist. Many of
the
> security settings for DTC were added Win2k3. But I have read article
stating[vbcol=seagreen]
> that this security is ignored if one of the machines is detected as Win2k.
> I will look into the 3rd article.
> If you have any other idea, they would be greatly appreciated.
> Thank you
> Clint Colefax
>
> "Andrew J. Kelly" wrote:
but[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/default...&Product=sql2k[vbcol=seagreen]
message[vbcol=seagreen]
win2k[vbcol=seagreen]
it's[vbcol=seagreen]
win2k[vbcol=seagreen]
script[vbcol=seagreen]
coordinator"[vbcol=seagreen]
in a[vbcol=seagreen]
any[vbcol=seagreen]
Error on MSDTC on win2k3 to win2k
I have two servers, one running win2k3 server and the other running win2k
advanced server. Both are also running MSSQL2k.
I have a script that runs on the win2k3 server, that updates one of it's
tables, based on information accessed through a linked server to the win2k
machine. No updating is done to the win2k machine, only selection. All
updates occur to the data on the win2k3 machine, which is were the script is
running.
When I execute this script, I get the following error.
"New transaction cannot enlist in the specified transaction coordinator"
When both machines are win2k, this works without any problem.
Both servers have a linked server connection to each other. All other
scripts that work across this link work fine, as long as they are not in a
transaction.
I am running out of ideas on how to get this working, does anyone have any
ideas. Any assistance would be greatly appreciated.
Thank you
Clint ColefaxI would say it is pretty likely DTC is turned off on the Win2003 machine but
here are some things that come up in the KB search:
http://support.microsoft.com/default.aspx?scid=kb;en-us;816701&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k
http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&Product=sql2k
Andrew J. Kelly SQL MVP
"Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
news:4E379DAB-38A2-4034-9196-8C5B605A2193@.microsoft.com...
> I am currently having issue with MSDTC.
> I have two servers, one running win2k3 server and the other running win2k
> advanced server. Both are also running MSSQL2k.
> I have a script that runs on the win2k3 server, that updates one of it's
> tables, based on information accessed through a linked server to the win2k
> machine. No updating is done to the win2k machine, only selection. All
> updates occur to the data on the win2k3 machine, which is were the script
is
> running.
> When I execute this script, I get the following error.
> "New transaction cannot enlist in the specified transaction coordinator"
> When both machines are win2k, this works without any problem.
> Both servers have a linked server connection to each other. All other
> scripts that work across this link work fine, as long as they are not in a
> transaction.
> I am running out of ideas on how to get this working, does anyone have any
> ideas. Any assistance would be greatly appreciated.
> Thank you
> Clint Colefax|||Thank you for your response.
DTC is running on both servers, that was the first thing I checked. The 3
three knowledge base article below I have tried, most of these settings were
already set, or in the case of the win2k machine, do not exist. Many of the
security settings for DTC were added Win2k3. But I have read article stating
that this security is ignored if one of the machines is detected as Win2k.
I will look into the 3rd article.
If you have any other idea, they would be greatly appreciated.
Thank you
Clint Colefax
"Andrew J. Kelly" wrote:
> I would say it is pretty likely DTC is turned off on the Win2003 machine but
> here are some things that come up in the KB search:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;816701&Product=sql2k
> http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k
> http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k
> http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&Product=sql2k
>
> --
> Andrew J. Kelly SQL MVP
>
> "Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
> news:4E379DAB-38A2-4034-9196-8C5B605A2193@.microsoft.com...
> > I am currently having issue with MSDTC.
> >
> > I have two servers, one running win2k3 server and the other running win2k
> > advanced server. Both are also running MSSQL2k.
> > I have a script that runs on the win2k3 server, that updates one of it's
> > tables, based on information accessed through a linked server to the win2k
> > machine. No updating is done to the win2k machine, only selection. All
> > updates occur to the data on the win2k3 machine, which is were the script
> is
> > running.
> > When I execute this script, I get the following error.
> >
> > "New transaction cannot enlist in the specified transaction coordinator"
> >
> > When both machines are win2k, this works without any problem.
> >
> > Both servers have a linked server connection to each other. All other
> > scripts that work across this link work fine, as long as they are not in a
> > transaction.
> >
> > I am running out of ideas on how to get this working, does anyone have any
> > ideas. Any assistance would be greatly appreciated.
> >
> > Thank you
> > Clint Colefax
>
>|||Sorry those would have been my guess. If no one else pipes up you might
want to give MS PSS a call. Even if it isn't a bug it might be worth the
$250.00 or so to get the systems up as soon as possible.
http://support.microsoft.com/default.aspx?scid=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
--
Andrew J. Kelly SQL MVP
"Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
news:0AEBF2EC-9455-47B1-BB30-56F41CB100D0@.microsoft.com...
> Thank you for your response.
> DTC is running on both servers, that was the first thing I checked. The 3
> three knowledge base article below I have tried, most of these settings
were
> already set, or in the case of the win2k machine, do not exist. Many of
the
> security settings for DTC were added Win2k3. But I have read article
stating
> that this security is ignored if one of the machines is detected as Win2k.
> I will look into the 3rd article.
> If you have any other idea, they would be greatly appreciated.
> Thank you
> Clint Colefax
>
> "Andrew J. Kelly" wrote:
> > I would say it is pretty likely DTC is turned off on the Win2003 machine
but
> > here are some things that come up in the KB search:
> >
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;816701&Product=sql2k
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k
> >
> >
http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&Product=sql2k
> >
> >
> >
> > --
> > Andrew J. Kelly SQL MVP
> >
> >
> > "Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in
message
> > news:4E379DAB-38A2-4034-9196-8C5B605A2193@.microsoft.com...
> > > I am currently having issue with MSDTC.
> > >
> > > I have two servers, one running win2k3 server and the other running
win2k
> > > advanced server. Both are also running MSSQL2k.
> > > I have a script that runs on the win2k3 server, that updates one of
it's
> > > tables, based on information accessed through a linked server to the
win2k
> > > machine. No updating is done to the win2k machine, only selection. All
> > > updates occur to the data on the win2k3 machine, which is were the
script
> > is
> > > running.
> > > When I execute this script, I get the following error.
> > >
> > > "New transaction cannot enlist in the specified transaction
coordinator"
> > >
> > > When both machines are win2k, this works without any problem.
> > >
> > > Both servers have a linked server connection to each other. All other
> > > scripts that work across this link work fine, as long as they are not
in a
> > > transaction.
> > >
> > > I am running out of ideas on how to get this working, does anyone have
any
> > > ideas. Any assistance would be greatly appreciated.
> > >
> > > Thank you
> > > Clint Colefax
> >
> >
> >
Error on MSDTC on win2k3 to win2k
I have two servers, one running win2k3 server and the other running win2k
advanced server. Both are also running MSSQL2k.
I have a script that runs on the win2k3 server, that updates one of it's
tables, based on information accessed through a linked server to the win2k
machine. No updating is done to the win2k machine, only selection. All
updates occur to the data on the win2k3 machine, which is were the script is
running.
When I execute this script, I get the following error.
"New transaction cannot enlist in the specified transaction coordinator"
When both machines are win2k, this works without any problem.
Both servers have a linked server connection to each other. All other
scripts that work across this link work fine, as long as they are not in a
transaction.
I am running out of ideas on how to get this working, does anyone have any
ideas. Any assistance would be greatly appreciated.
Thank you
Clint ColefaxI would say it is pretty likely DTC is turned off on the Win2003 machine but
here are some things that come up in the KB search:
http://support.microsoft.com/defaul...1&Product=sql2k
http://support.microsoft.com/defaul...5&Product=sql2k
http://support.microsoft.com/defaul...2&Product=sql2k
http://support.microsoft.com/defaul...7&Product=sql2k
Andrew J. Kelly SQL MVP
"Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
news:4E379DAB-38A2-4034-9196-8C5B605A2193@.microsoft.com...
> I am currently having issue with MSDTC.
> I have two servers, one running win2k3 server and the other running win2k
> advanced server. Both are also running MSSQL2k.
> I have a script that runs on the win2k3 server, that updates one of it's
> tables, based on information accessed through a linked server to the win2k
> machine. No updating is done to the win2k machine, only selection. All
> updates occur to the data on the win2k3 machine, which is were the script
is
> running.
> When I execute this script, I get the following error.
> "New transaction cannot enlist in the specified transaction coordinator"
> When both machines are win2k, this works without any problem.
> Both servers have a linked server connection to each other. All other
> scripts that work across this link work fine, as long as they are not in a
> transaction.
> I am running out of ideas on how to get this working, does anyone have any
> ideas. Any assistance would be greatly appreciated.
> Thank you
> Clint Colefax|||Thank you for your response.
DTC is running on both servers, that was the first thing I checked. The 3
three knowledge base article below I have tried, most of these settings were
already set, or in the case of the win2k machine, do not exist. Many of the
security settings for DTC were added Win2k3. But I have read article stating
that this security is ignored if one of the machines is detected as Win2k.
I will look into the 3rd article.
If you have any other idea, they would be greatly appreciated.
Thank you
Clint Colefax
"Andrew J. Kelly" wrote:
> I would say it is pretty likely DTC is turned off on the Win2003 machine b
ut
> here are some things that come up in the KB search:
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;816701&Product=sql2k[/ur
l]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;831425&Product=sql2k[/ur
l]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;329332&Product=sql2k[/ur
l]
> [url]http://support.microsoft.com/default.aspx?scid=kb;en-us;555017&Product=sql2k[/ur
l]
>
> --
> Andrew J. Kelly SQL MVP
>
> "Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
> news:4E379DAB-38A2-4034-9196-8C5B605A2193@.microsoft.com...
> is
>
>|||Sorry those would have been my guess. If no one else pipes up you might
want to give MS PSS a call. Even if it isn't a bug it might be worth the
$250.00 or so to get the systems up as soon as possible.
http://support.microsoft.com/defaul...id=fh;EN-US;sql SQL Support
http://www.mssqlserver.com/faq/general-pss.asp MS PSS
Andrew J. Kelly SQL MVP
"Clint Colefax" <ClintColefax@.discussions.microsoft.com> wrote in message
news:0AEBF2EC-9455-47B1-BB30-56F41CB100D0@.microsoft.com...
> Thank you for your response.
> DTC is running on both servers, that was the first thing I checked. The 3
> three knowledge base article below I have tried, most of these settings
were
> already set, or in the case of the win2k machine, do not exist. Many of
the
> security settings for DTC were added Win2k3. But I have read article
stating[vbcol=seagreen]
> that this security is ignored if one of the machines is detected as Win2k.
> I will look into the 3rd article.
> If you have any other idea, they would be greatly appreciated.
> Thank you
> Clint Colefax
>
> "Andrew J. Kelly" wrote:
>
but[vbcol=seagreen]
http://support.microsoft.com/defaul...1&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/defaul...5&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/defaul...2&Product=sql2k[vbcol=seagreen]
http://support.microsoft.com/defaul...7&Product=sql2k[vbcol=seagreen]
message[vbcol=seagreen]
win2k[vbcol=seagreen]
it's[vbcol=seagreen]
win2k[vbcol=seagreen]
script[vbcol=seagreen]
coordinator"[vbcol=seagreen]
in a[vbcol=seagreen]
any[vbcol=seagreen]
Error on MSDTC after a SQL Server fail-over
I have a SQL Server 2000 64 bits running on an two node cluster (NODE1 and
NODE2) with two SQL Server instances (SQL1 and SQL1\2).
Instance SQL1 is running on NODE1 and instance SQL1\2 is running on NODE2.
MSDTC is configured on a exclusive group and it is running on NODE1.
The Cluster Group also is running on NODE1.
I use a lot of distributed transactions between SQL1\2 and SQL1 and it works
just fine.
I had a problem last night with NODE1, and all the resources (Cluster, SQL1
and MSDTC) failed to NODE2.
After the failover I started getting the error below when trying to execute
a distributed transaction from SQL1\2 to SQL1.
Error: 8510, Severity: 20, State: 2
Enlist of MSDTC transaction failed: XACT_E_CONNECTION_DOWN.
The error happened during the failover and also after the finish of the
failver.
On SQL1 error log I notice that there was no error messages when it
initialize the MSDTC. Below is the message from the ErrorLog.
"Attempting to initialize Distributed Transaction Coordinator."
To solve the Error I brought up NODE1 back on-line (it failed because of a
network problem). I move the MSDTC back to NODE1, move SQL1 back to NODE1 and
also re-started SQL1\2 on NODE2 (brought offline, bring on-line). After that
procedure I was able to use distributed transactions between SQL1 and SQL1\2.
I would like to know why that problem happened?
I suposed that MSDTC was able to work on cluster and that the MSDTC should
work after a failover.
I would like your help to understand the problem. If you need more
information just let me know.
Regards.
Carlos Eduardo Selonke de Souza
http://carlos.geekbunker.org
Hi Carlos
MSDTC has to be running when SQL is starting. So it's a timing problem. To
be certain, check the log in SQL, and look for messages about finding the
Transaction "Server". It probably states that is was down. SQL will not retry
it afterwards.
If the MSDTC resource was in the same group as the SQL Virtual Server, you
could make SQL dependant of MSDTC, but unfortunately this is not the case.
Chau chau,
Pascalos
"Carlos Selonke" wrote:
> Hello
> I have a SQL Server 2000 64 bits running on an two node cluster (NODE1 and
> NODE2) with two SQL Server instances (SQL1 and SQL1\2).
> Instance SQL1 is running on NODE1 and instance SQL1\2 is running on NODE2.
> MSDTC is configured on a exclusive group and it is running on NODE1.
> The Cluster Group also is running on NODE1.
> I use a lot of distributed transactions between SQL1\2 and SQL1 and it works
> just fine.
> I had a problem last night with NODE1, and all the resources (Cluster, SQL1
> and MSDTC) failed to NODE2.
> After the failover I started getting the error below when trying to execute
> a distributed transaction from SQL1\2 to SQL1.
> Error: 8510, Severity: 20, State: 2
> Enlist of MSDTC transaction failed: XACT_E_CONNECTION_DOWN.
> The error happened during the failover and also after the finish of the
> failver.
> On SQL1 error log I notice that there was no error messages when it
> initialize the MSDTC. Below is the message from the ErrorLog.
> "Attempting to initialize Distributed Transaction Coordinator."
> To solve the Error I brought up NODE1 back on-line (it failed because of a
> network problem). I move the MSDTC back to NODE1, move SQL1 back to NODE1 and
> also re-started SQL1\2 on NODE2 (brought offline, bring on-line). After that
> procedure I was able to use distributed transactions between SQL1 and SQL1\2.
> I would like to know why that problem happened?
> I suposed that MSDTC was able to work on cluster and that the MSDTC should
> work after a failover.
> I would like your help to understand the problem. If you need more
> information just let me know.
> Regards.
> --
> Carlos Eduardo Selonke de Souza
> http://carlos.geekbunker.org
Error on Export to Excel with Bookmarks and Navigation Jumps
We're running RS 2005. I have a problem in a report using two
main sections. There's a top level report, made up from 4 tables
within a rectangle. The second section of the report contains the
detail of the calculations making the top level figures.
The second section of the report contains bookmarks and jump links to
drill to different levels of the reporting structure. This works
fine.
The top level of the report also has jump to bookmark links to drop
into the relevant section of section two, and display the detail.
The problem I'm having is that although the jump links work fine within
report manager, the report will not export to excel from report
manager. It errors with the error at the bottom of this post.
Removing the bookmark links from the top level of the report solves the
export issue (but obviously without the functionality I require).
The strangest thing is that the export works fine from the development
environment in VS .NET 2005, although the bookmarks do not work and
claim an "invalid link" (or something similar).
Any ideas, anybody?
Thanks in advance.
Jon
Error message below:
w3wp!reportrendering!1!06/22/2006-16:51:19:: e ERROR: Throwing
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
An error occurred during rendering of the report., ;
Info:
Microsoft.ReportingServices.ReportProcessing.WrapperReportRenderingException:
An error occurred during rendering of the report. >
Microsoft.ReportingServices.ReportRendering.ReportRenderingException:
An error occurred during rendering of the report. >
System.ArgumentException: Item has already been added. Key in
dictionary: ' 2' Key being added: ' 2'
at System.Collections.Hashtable.Insert(Object key, Object nvalue, Boolean add)
at System.Collections.Hashtable.Add(Object key, Object value)
at
Microsoft.ReportingServices.Rendering.BIFFUtility.WorkBook.AddBookmarkLink(String
name, String uniqueName, Boolean keepName)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderTextBox(TextBox
textBox, PageReportItemInfo reportItemInfo, PageCell pageCell,
PageTableGrid pageTableGrid, ReportItem dataRegionParent,
Hashtable& duplicateItemsTable, Hashtable riReferenceTable, Int32
row, Int32 col, Boolean addHeaderRows)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderGridCell(PageLayout
pageLayout, Int32 row, Int32 col, Hashtable& duplicateItemsTable,
Boolean addHeaderRows, ReportItem parentItem, Hashtable
riReferenceTable)
at
Microsoft.ReportingServices.Rendering.BIFFUtility.WorkSheet.WriteRowBlocksAndCells(ExcelRenderer
excelRenderer, Stream stream, UInt32 indexBeginOffsetPosition, Int32
minCol, Int32 maxCol)
at
Microsoft.ReportingServices.Rendering.BIFFUtility.BaseWorkSheet.WriteWorkSheet(ExcelRenderer
excelRenderer, Stream stream, Int32 offset)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderPageLayout(PageLayout
pageLayout, Int32& currentPageNumber, Stack& stack)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderPageCollection(PageCollection
pageCollection, Int32& currentPageNumber, Stack& stack,
PageLayout& lastPageLayout)
at Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GenerateWorkSheets()
at Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.GenerateMainSheet()
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.RenderExcelWorkBook(CreateAndRegisterStream
createAndRegisterStream)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.ProcessReport(CreateAndRegisterStream
createAndRegisterStream)
at
Microsoft.ReportingServices.Rendering.ExcelRenderer.ExcelRenderer.Render(Report
report, NameValueCollection reportServerParameters, NameValueCollection
deviceInfo, NameValueCollection clientCapabilities,
EvaluateHeaderFooterExpressions evaluateHeaderFooterExpressions,
CreateAndRegisterStream createAndRegisterStream)A little more on this issue.
I've two extra tables to the top level of the report to represent other
views on the same data. I've found that the top level figure -
which is a single table, with only a detail row, and only a single row
of data feeding into it - works fine, whilst another new table (with
again, a single table, only a detail row, but a different dataset with
the same fields) does not work.
Confused |||Again... some more on this issue!
A colleague of mine has a similar problem. Making a couple of
assumptions, the common issue seems to be when you have bookmark/jump
IDs that are generated from the dataset. If you have two
different jump points that jump to the SAME bookmark, there appears to
be an issue.
As mentioned previously, I can export through the development environment but the bookmark links show up as being invalid.
I'm sure this is a feature supported by Excel. Is this possibly a bug with the excel renderer?
Cheers,
Jon|||
It definately seems like a bug, although I haven't been able to duplicate it yet. I don't have an idea for a workaround at this time.
The fact that you can run it successfully from Visual Studio is puzzling. Do you have different versions of Reporting Services installed on your server vs. where you are developing?
- Geoff
|||Hi Geoff,Thanks for looking at this post too.
I do run both RS 2000 and 2005, but they're hosted on seperate servers,
and I develop using the appropriate version of VS .NET (2k3 for RS 2k,
and 2k5 for RS 2k5). In this case it's VS 2k5 with RS 2k5.
It will export from VS, but the bookmark links on the Excel version do
not work and come up with a "Reference Not Valid" error when
clicked. It simply won't export from the report manager and
errors (as above). Would you like me to mail you spreadsheet with
the export from the development environment? With the error
message posted above, you can see what happens from both VS and report
manager.
Regards,
Jon|||
Hi Jon,
This looks like a bug to me. The best way to continue here is to submit it via Microsoft Connect, at https://connect.microsoft.com/SQLServer. This will get the issue into our bug pipeline so that it can be properly addressed and tracked for a fix.
Thanks, Geoff
|||OK Geoff, thanks for your help.I've now logged this bug, so we'll see if something comes back from
it. Unfortunately, connect isn't particularly compatible with
Firefox so I ended up submitting it 4 times!
Shall I submit this bug too
Thanks again,
Jon