When using VS2003 and Reporting Services 2005, I am met with the following
compilation error after creating a dataset then trying to design it:
"Version 2.0 Is Not A Compatible Version"
I cant drag any tools to the design surface, or add any fields. I have both
SQL Server 2000 Reporting Services as well as 2005.
Anyone have a hint on how I can remedy this?
Here is the stack:
************** Exception Text **************
System.BadImageFormatException: Version 2.0 is not a compatible version.
at System.Reflection.CustomAttribute.CreateCAObject(Int32& propNum,
Assembly& assembly)
at System.Reflection.CustomAttribute.GetObject()
at
System.Reflection.CustomAttribute.CheckConsistencyAndCreateArray(CustomAttribute
caItem, Type caType)
at System.Reflection.CustomAttribute.GetCustomAttributes(MemberInfo
member, Type caType, Boolean inherit)
at System.Reflection.RuntimeFieldInfo.GetCustomAttributes(Type
attributeType, Boolean inherit)
at System.Xml.Serialization.XmlAttributes..ctor(ICustomAttributeProvider
provider)
at
Microsoft.ReportDesigner.Serialization.XmlAttributes..ctor(ICustomAttributeProvider
provider)
at
Microsoft.ReportDesigner.Serialization.TypeMapper.ImportMemberField(StructMapping
mapping, MemberInfo field)
at
Microsoft.ReportDesigner.Serialization.TypeMapper.ImportTypeMembers(StructMapping
mapping, Object obj)
at
Microsoft.ReportDesigner.Serialization.TypeMapper.ImportStructMapping(Type
objBaseType, Object obj)
at Microsoft.ReportDesigner.Serialization.TypeMapper.GetTypeModel(Type
baseType, Object obj)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteObject(Type
objType, Object obj, String name, String ns)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteArrayContent(Object
array, ArrayMapping mapping, String ns)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteArray(Object
array, String name, String ns, ArrayMapping mapping)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteMember(Object
component, Object obj, MemberMapping memberMapping, String name, String ns)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteStructureContent(Object
obj, StructMapping mapping, String ns)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteStructure(Object
obj, String name, String ns, StructMapping mapping)
at
Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteObject(Type
objType, Object obj, String name, String ns)
at
Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.SerializeComponent(IDesignerSerializationManager
manager, Object component, Object serializationStream)
at
Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.Serialize(IDesignerSerializationManager
manager, Object value)
at
Microsoft.ReportDesigner.Serialization.UndoManager.Serialize(CodeDomSerializer
serializer, Object component)
at
Microsoft.ReportDesigner.Serialization.UndoManager.TakeSnapshot(ICollection
undoEntries, UndoSnapshot snapshot)
at
Microsoft.ReportDesigner.Serialization.UndoUnit.ComponentChanging(Object
comp, MemberDescriptor member)
at
Microsoft.ReportDesigner.Serialization.UndoManager.OnComponentChanging(Object
sender, ComponentChangingEventArgs e)
at
System.ComponentModel.Design.ComponentChangingEventHandler.Invoke(Object
sender, ComponentChangingEventArgs e)
at
Microsoft.VisualStudio.Designer.Host.DesignerHost.OnComponentChanging(Object
component, MemberDescriptor member)
at
Microsoft.ReportDesigner.Design.FieldChooserControl.Transaction(Command
command, String sUndo, Field field, Field oldfield)
at Microsoft.ReportDesigner.Design.FieldChooserControl.OnAddClick()
at Microsoft.ReportDesigner.Design.FieldChooserControl.ShowContextMenu()
at
Microsoft.ReportDesigner.Design.FieldChooserControl.listView1_MouseUp(Object
sender, MouseEventArgs e)
at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
at System.Windows.Forms.ListView.WmReflectNotify(Message& m)
at System.Windows.Forms.ListView.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
IntPtr wparam, IntPtr lparam)Its an issue with VS 2003 and the 2000 Report Designer. Is there any way I
can specify 2000's Report Designer rather than have it default to 2005?
Right now I cant put the projects in the same solution, and the conversion
wizard tries to convert my web project as well as my report project, which I
do not want.
"Elliot Rodriguez" <elliotrodriguezatgeemaildotcom> wrote in message
news:eolheyESGHA.5656@.TK2MSFTNGP11.phx.gbl...
> When using VS2003 and Reporting Services 2005, I am met with the following
> compilation error after creating a dataset then trying to design it:
> "Version 2.0 Is Not A Compatible Version"
> I cant drag any tools to the design surface, or add any fields. I have
> both SQL Server 2000 Reporting Services as well as 2005.
> Anyone have a hint on how I can remedy this?
> Here is the stack:
> ************** Exception Text **************
> System.BadImageFormatException: Version 2.0 is not a compatible version.
> at System.Reflection.CustomAttribute.CreateCAObject(Int32& propNum,
> Assembly& assembly)
> at System.Reflection.CustomAttribute.GetObject()
> at
> System.Reflection.CustomAttribute.CheckConsistencyAndCreateArray(CustomAttribute
> caItem, Type caType)
> at System.Reflection.CustomAttribute.GetCustomAttributes(MemberInfo
> member, Type caType, Boolean inherit)
> at System.Reflection.RuntimeFieldInfo.GetCustomAttributes(Type
> attributeType, Boolean inherit)
> at System.Xml.Serialization.XmlAttributes..ctor(ICustomAttributeProvider
> provider)
> at
> Microsoft.ReportDesigner.Serialization.XmlAttributes..ctor(ICustomAttributeProvider
> provider)
> at
> Microsoft.ReportDesigner.Serialization.TypeMapper.ImportMemberField(StructMapping
> mapping, MemberInfo field)
> at
> Microsoft.ReportDesigner.Serialization.TypeMapper.ImportTypeMembers(StructMapping
> mapping, Object obj)
> at
> Microsoft.ReportDesigner.Serialization.TypeMapper.ImportStructMapping(Type
> objBaseType, Object obj)
> at Microsoft.ReportDesigner.Serialization.TypeMapper.GetTypeModel(Type
> baseType, Object obj)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteObject(Type
> objType, Object obj, String name, String ns)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteArrayContent(Object
> array, ArrayMapping mapping, String ns)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteArray(Object
> array, String name, String ns, ArrayMapping mapping)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteMember(Object
> component, Object obj, MemberMapping memberMapping, String name, String
> ns)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteStructureContent(Object
> obj, StructMapping mapping, String ns)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteStructure(Object
> obj, String name, String ns, StructMapping mapping)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlWriter.WriteObject(Type
> objType, Object obj, String name, String ns)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.SerializeComponent(IDesignerSerializationManager
> manager, Object component, Object serializationStream)
> at
> Microsoft.ReportDesigner.Serialization.DesignXmlSerializer.Serialize(IDesignerSerializationManager
> manager, Object value)
> at
> Microsoft.ReportDesigner.Serialization.UndoManager.Serialize(CodeDomSerializer
> serializer, Object component)
> at
> Microsoft.ReportDesigner.Serialization.UndoManager.TakeSnapshot(ICollection
> undoEntries, UndoSnapshot snapshot)
> at
> Microsoft.ReportDesigner.Serialization.UndoUnit.ComponentChanging(Object
> comp, MemberDescriptor member)
> at
> Microsoft.ReportDesigner.Serialization.UndoManager.OnComponentChanging(Object
> sender, ComponentChangingEventArgs e)
> at
> System.ComponentModel.Design.ComponentChangingEventHandler.Invoke(Object
> sender, ComponentChangingEventArgs e)
> at
> Microsoft.VisualStudio.Designer.Host.DesignerHost.OnComponentChanging(Object
> component, MemberDescriptor member)
> at
> Microsoft.ReportDesigner.Design.FieldChooserControl.Transaction(Command
> command, String sUndo, Field field, Field oldfield)
> at Microsoft.ReportDesigner.Design.FieldChooserControl.OnAddClick()
> at Microsoft.ReportDesigner.Design.FieldChooserControl.ShowContextMenu()
> at
> Microsoft.ReportDesigner.Design.FieldChooserControl.listView1_MouseUp(Object
> sender, MouseEventArgs e)
> at System.Windows.Forms.Control.OnMouseUp(MouseEventArgs e)
> at System.Windows.Forms.ListView.WmReflectNotify(Message& m)
> at System.Windows.Forms.ListView.WndProc(Message& m)
> at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
> at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
> at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg,
> IntPtr wparam, IntPtr lparam)
>
Showing posts with label version. Show all posts
Showing posts with label version. Show all posts
Monday, March 19, 2012
Thursday, March 8, 2012
"replace value of" and enum
I've created XML SCHEMA COLLECTION AS
<?xml version="1.0" encoding="utf-8"?>
<xs:schema elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Order" nillable="true" type="Order" />
<xs:complexType name="Order">
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="1" name="Status"
type="OrderStatus" />
</xs:sequence>
</xs:complexType>
<xs:simpleType name="OrderStatus">
<xs:restriction base="xs:string">
<xs:enumeration value="New" />
<xs:enumeration value="Pending" />
<xs:enumeration value="Complete" />
</xs:restriction>
</xs:simpleType>
</xs:schema>
Now I'd like to update OrderStatus:
UPDATE Orders
SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with "Expired"')
I get:
Msg 2247, Level 16, State 1, Procedure Orders_Select
XQuery [dbo.Orders.OrderXml.modify()]: The value is of type "xs:string",
which is not a subtype of the expected type "OrderStatus".
The below does not work either:
UPDATE Orders
SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
OrderStatus("Expired")')
How do I make this work?
ThanksNever mind, ("Expired" cast as OrderStatus) does the trick.
"Chris Carter" <anonymous@.discussions.microsoft.com> wrote in message
news:%23AHmjrHKGHA.2392@.TK2MSFTNGP09.phx.gbl...
> I've created XML SCHEMA COLLECTION AS
> <?xml version="1.0" encoding="utf-8"?>
> <xs:schema elementFormDefault="qualified"
> xmlns:xs="http://www.w3.org/2001/XMLSchema">
> <xs:element name="Order" nillable="true" type="Order" />
> <xs:complexType name="Order">
> <xs:sequence>
> <xs:element minOccurs="1" maxOccurs="1" name="Status"
> type="OrderStatus" />
> </xs:sequence>
> </xs:complexType>
> <xs:simpleType name="OrderStatus">
> <xs:restriction base="xs:string">
> <xs:enumeration value="New" />
> <xs:enumeration value="Pending" />
> <xs:enumeration value="Complete" />
> </xs:restriction>
> </xs:simpleType>
> </xs:schema>
>
> Now I'd like to update OrderStatus:
> UPDATE Orders
> SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
> "Expired"')
> I get:
> Msg 2247, Level 16, State 1, Procedure Orders_Select
> XQuery [dbo.Orders.OrderXml.modify()]: The value is of type "xs:string",
> which is not a subtype of the expected type "OrderStatus".
> The below does not work either:
> UPDATE Orders
> SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
> OrderStatus("Expired")')
>
> How do I make this work?
>
> Thanks
>
>
>
<?xml version="1.0" encoding="utf-8"?>
<xs:schema elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Order" nillable="true" type="Order" />
<xs:complexType name="Order">
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="1" name="Status"
type="OrderStatus" />
</xs:sequence>
</xs:complexType>
<xs:simpleType name="OrderStatus">
<xs:restriction base="xs:string">
<xs:enumeration value="New" />
<xs:enumeration value="Pending" />
<xs:enumeration value="Complete" />
</xs:restriction>
</xs:simpleType>
</xs:schema>
Now I'd like to update OrderStatus:
UPDATE Orders
SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with "Expired"')
I get:
Msg 2247, Level 16, State 1, Procedure Orders_Select
XQuery [dbo.Orders.OrderXml.modify()]: The value is of type "xs:string",
which is not a subtype of the expected type "OrderStatus".
The below does not work either:
UPDATE Orders
SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
OrderStatus("Expired")')
How do I make this work?
ThanksNever mind, ("Expired" cast as OrderStatus) does the trick.
"Chris Carter" <anonymous@.discussions.microsoft.com> wrote in message
news:%23AHmjrHKGHA.2392@.TK2MSFTNGP09.phx.gbl...
> I've created XML SCHEMA COLLECTION AS
> <?xml version="1.0" encoding="utf-8"?>
> <xs:schema elementFormDefault="qualified"
> xmlns:xs="http://www.w3.org/2001/XMLSchema">
> <xs:element name="Order" nillable="true" type="Order" />
> <xs:complexType name="Order">
> <xs:sequence>
> <xs:element minOccurs="1" maxOccurs="1" name="Status"
> type="OrderStatus" />
> </xs:sequence>
> </xs:complexType>
> <xs:simpleType name="OrderStatus">
> <xs:restriction base="xs:string">
> <xs:enumeration value="New" />
> <xs:enumeration value="Pending" />
> <xs:enumeration value="Complete" />
> </xs:restriction>
> </xs:simpleType>
> </xs:schema>
>
> Now I'd like to update OrderStatus:
> UPDATE Orders
> SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
> "Expired"')
> I get:
> Msg 2247, Level 16, State 1, Procedure Orders_Select
> XQuery [dbo.Orders.OrderXml.modify()]: The value is of type "xs:string",
> which is not a subtype of the expected type "OrderStatus".
> The below does not work either:
> UPDATE Orders
> SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
> OrderStatus("Expired")')
>
> How do I make this work?
>
> Thanks
>
>
>
"replace value of" and enum
I've created XML SCHEMA COLLECTION AS
<?xml version="1.0" encoding="utf-8"?>
<xs:schema elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Order" nillable="true" type="Order" />
<xs:complexType name="Order">
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="1" name="Status"
type="OrderStatus" />
</xs:sequence>
</xs:complexType>
<xs:simpleType name="OrderStatus">
<xs:restriction base="xs:string">
<xs:enumeration value="New" />
<xs:enumeration value="Pending" />
<xs:enumeration value="Complete" />
</xs:restriction>
</xs:simpleType>
</xs:schema>
Now I'd like to update OrderStatus:
UPDATE Orders
SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with "Expired"')
I get:
Msg 2247, Level 16, State 1, Procedure Orders_Select
XQuery [dbo.Orders.OrderXml.modify()]: The value is of type "xs:string",
which is not a subtype of the expected type "OrderStatus".
The below does not work either:
UPDATE Orders
SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
OrderStatus("Expired")')
How do I make this work?
Thanks
Never mind, ("Expired" cast as OrderStatus) does the trick.
"Chris Carter" <anonymous@.discussions.microsoft.com> wrote in message
news:%23AHmjrHKGHA.2392@.TK2MSFTNGP09.phx.gbl...
> I've created XML SCHEMA COLLECTION AS
> <?xml version="1.0" encoding="utf-8"?>
> <xs:schema elementFormDefault="qualified"
> xmlns:xs="http://www.w3.org/2001/XMLSchema">
> <xs:element name="Order" nillable="true" type="Order" />
> <xs:complexType name="Order">
> <xs:sequence>
> <xs:element minOccurs="1" maxOccurs="1" name="Status"
> type="OrderStatus" />
> </xs:sequence>
> </xs:complexType>
> <xs:simpleType name="OrderStatus">
> <xs:restriction base="xs:string">
> <xs:enumeration value="New" />
> <xs:enumeration value="Pending" />
> <xs:enumeration value="Complete" />
> </xs:restriction>
> </xs:simpleType>
> </xs:schema>
>
> Now I'd like to update OrderStatus:
> UPDATE Orders
> SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
> "Expired"')
> I get:
> Msg 2247, Level 16, State 1, Procedure Orders_Select
> XQuery [dbo.Orders.OrderXml.modify()]: The value is of type "xs:string",
> which is not a subtype of the expected type "OrderStatus".
> The below does not work either:
> UPDATE Orders
> SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
> OrderStatus("Expired")')
>
> How do I make this work?
>
> Thanks
>
>
>
<?xml version="1.0" encoding="utf-8"?>
<xs:schema elementFormDefault="qualified"
xmlns:xs="http://www.w3.org/2001/XMLSchema">
<xs:element name="Order" nillable="true" type="Order" />
<xs:complexType name="Order">
<xs:sequence>
<xs:element minOccurs="1" maxOccurs="1" name="Status"
type="OrderStatus" />
</xs:sequence>
</xs:complexType>
<xs:simpleType name="OrderStatus">
<xs:restriction base="xs:string">
<xs:enumeration value="New" />
<xs:enumeration value="Pending" />
<xs:enumeration value="Complete" />
</xs:restriction>
</xs:simpleType>
</xs:schema>
Now I'd like to update OrderStatus:
UPDATE Orders
SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with "Expired"')
I get:
Msg 2247, Level 16, State 1, Procedure Orders_Select
XQuery [dbo.Orders.OrderXml.modify()]: The value is of type "xs:string",
which is not a subtype of the expected type "OrderStatus".
The below does not work either:
UPDATE Orders
SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
OrderStatus("Expired")')
How do I make this work?
Thanks
Never mind, ("Expired" cast as OrderStatus) does the trick.
"Chris Carter" <anonymous@.discussions.microsoft.com> wrote in message
news:%23AHmjrHKGHA.2392@.TK2MSFTNGP09.phx.gbl...
> I've created XML SCHEMA COLLECTION AS
> <?xml version="1.0" encoding="utf-8"?>
> <xs:schema elementFormDefault="qualified"
> xmlns:xs="http://www.w3.org/2001/XMLSchema">
> <xs:element name="Order" nillable="true" type="Order" />
> <xs:complexType name="Order">
> <xs:sequence>
> <xs:element minOccurs="1" maxOccurs="1" name="Status"
> type="OrderStatus" />
> </xs:sequence>
> </xs:complexType>
> <xs:simpleType name="OrderStatus">
> <xs:restriction base="xs:string">
> <xs:enumeration value="New" />
> <xs:enumeration value="Pending" />
> <xs:enumeration value="Complete" />
> </xs:restriction>
> </xs:simpleType>
> </xs:schema>
>
> Now I'd like to update OrderStatus:
> UPDATE Orders
> SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
> "Expired"')
> I get:
> Msg 2247, Level 16, State 1, Procedure Orders_Select
> XQuery [dbo.Orders.OrderXml.modify()]: The value is of type "xs:string",
> which is not a subtype of the expected type "OrderStatus".
> The below does not work either:
> UPDATE Orders
> SET OrderXml.modify('replace value of (/Order[1]/Status[1]) with
> OrderStatus("Expired")')
>
> How do I make this work?
>
> Thanks
>
>
>
Tuesday, March 6, 2012
"Orphaned" maintenance plan
Warning ahead of time - I'm a total idiot about this stuff.
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
Julie
Hi Julie
"Kaidi" wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, you
will see a node for management under which is SQL Server Agent and then Jobs.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should be
deleted.
John
|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenance plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
|||Hi Julie
"Kaidi" wrote:
> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!
> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.
> :P
> Julie
>
John
|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!
> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
Julie
Hi Julie
"Kaidi" wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, you
will see a node for management under which is SQL Server Agent and then Jobs.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should be
deleted.
John
|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenance plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
|||Hi Julie
"Kaidi" wrote:
> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!
> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.
> :P
> Julie
>
John
|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!
> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie
"Orphaned" maintenance plan
Warning ahead of time - I'm a total idiot about this stuff.
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
JulieHi Julie
"Kaidi" wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, yo
u
will see a node for management under which is SQL Server Agent and then Jobs
.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should b
e
deleted.
John|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenan
ce plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie|||Hi Julie
"Kaidi" wrote:
> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!
> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.
> :P
> Julie
>
John|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!
> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
JulieHi Julie
"Kaidi" wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, yo
u
will see a node for management under which is SQL Server Agent and then Jobs
.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should b
e
deleted.
John|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenan
ce plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie|||Hi Julie
"Kaidi" wrote:
> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!
> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.
> :P
> Julie
>
John|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!
> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie
"Orphaned" maintenance plan
Warning ahead of time - I'm a total idiot about this stuff.
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
JulieHi Julie
"Kaidi" wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, you
will see a node for management under which is SQL Server Agent and then Jobs.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should be
deleted.
John|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenance plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie|||Hi Julie
"Kaidi" wrote:
> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!
> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.
> :P
> Julie
>
John|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> > Followup, for anyone who happens to hit this post on a usenet search.
> > (I hate finding my problem with no solution.
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!
> > Do *not* simply delete the job rows that are causing the problem from
> > the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> > taken me a couple of hours to track down all of the pieces/references
> > to the job in other tables. I'm just hoping to heck I got them all...I
> > went manually through all of the delete commands in the sp_delete_job
> > procedure, and praying that it worked!
> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie
Server is Windows Server 2003
SQL Enterprise Manager version is 8.0
I had been having a problem getting backups to auto delete and so
followed the instructions in a Microsoft KB article and set the
recovery mode to Full for all of the DBs. That solved the problem for
almost every database in the system.
However, apparently at some point several of the databases used a
maintenance plan called "DB Maintenance Plan2" which no longer exists
on the system. (There is currently only a single maintenance plan on
the system.) How can I find out where this is coming from and delete
it?
This was the error in the Events log:
SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
The Job was invoked by Schedule 5 (Schedule 1). The last step to run
was step 1 (Step 1).
Please talk in baby steps - thanks.
JulieHi Julie
"Kaidi" wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used a
> maintenance plan called "DB Maintenance Plan2" which no longer exists
> on the system. (There is currently only a single maintenance plan on
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DB Maintenance Plan 'DB
> Maintenance Plan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie
>
I am not sure if it is the job you are looking for or not! But if you start
SQL Enterprise Manager, and open up the Node for the SQL Server Instance, you
will see a node for management under which is SQL Server Agent and then Jobs.
There should be a job called "DB Backup Job for DB Maintenance Plan 'DB
Maintenance Plan2' " which will have a red cross next to it because it has
failed. Right click the job and choose delete from the menu to remove the
job. Usually when a maintenance plan is deleted the associated jobs should be
deleted.
John|||Followup, for anyone who happens to hit this post on a usenet search.
(I hate finding my problem with no solution.
There's an SP called sp_delete_job that you can use with either a job
name or a job id and it takes care of the cleanup required to remove
the maintenance plan completely from your system.
Do *not* simply delete the job rows that are causing the problem from
the msdb.sysjobs table. Unfortunately, that is what I did, and it's
taken me a couple of hours to track down all of the pieces/references
to the job in other tables. I'm just hoping to heck I got them all...I
went manually through all of the delete commands in the sp_delete_job
procedure, and praying that it worked!
:P
Julie
On Apr 4, 12:04 pm, "Kaidi" <julie.sie...@.gmail.com> wrote:
> Warning ahead of time - I'm a total idiot about this stuff.
> Server is Windows Server 2003
> SQL Enterprise Manager version is 8.0
> I had been having a problem getting backups to auto delete and so
> followed the instructions in a Microsoft KB article and set the
> recovery mode to Full for all of the DBs. That solved the problem for
> almost every database in the system.
> However, apparently at some point several of the databases used amaintenance plancalled "DB MaintenancePlan2" which no longer exists
> on the system. (There is currently only a singlemaintenance planon
> the system.) How can I find out where this is coming from and delete
> it?
> This was the error in the Events log:
> SQL Server Scheduled Job 'DB Backup Job for DBMaintenance Plan'DB
> MaintenancePlan2'' (0x8AB900BBC4CB7E409DCF47CACB85233E) - Status:
> Failed - Invoked on: 2007-04-04 03:00:00 - Message: The job failed.
> The Job was invoked by Schedule 5 (Schedule 1). The last step to run
> was step 1 (Step 1).
> Please talk in baby steps - thanks.
> Julie|||Hi Julie
"Kaidi" wrote:
> Followup, for anyone who happens to hit this post on a usenet search.
> (I hate finding my problem with no solution.
I had replied to this!
> There's an SP called sp_delete_job that you can use with either a job
> name or a job id and it takes care of the cleanup required to remove
> the maintenance plan completely from your system.
> Do *not* simply delete the job rows that are causing the problem from
> the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> taken me a couple of hours to track down all of the pieces/references
> to the job in other tables. I'm just hoping to heck I got them all...I
> went manually through all of the delete commands in the sp_delete_job
> procedure, and praying that it worked!
You did not mention this in your original post. It is never recommended to
hack the system tables.
> :P
> Julie
>
John|||On Apr 7, 6:56 am, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi Julie
> "Kaidi" wrote:
> > Followup, for anyone who happens to hit this post on a usenet search.
> > (I hate finding my problem with no solution.
> I had replied to this!
>
No replies came up in this thread at Google, John - sorry!
> > Do *not* simply delete the job rows that are causing the problem from
> > the msdb.sysjobs table. Unfortunately, that is what I did, and it's
> > taken me a couple of hours to track down all of the pieces/references
> > to the job in other tables. I'm just hoping to heck I got them all...I
> > went manually through all of the delete commands in the sp_delete_job
> > procedure, and praying that it worked!
> You did not mention this in your original post. It is never recommended to
> hack the system tables.
> John
When I posted originally, I hadn't DONE that yet, but didn't see any
replies.
There are 3 dbs that are backing up through the orphan, at 1gb each
when squished as small as they can go - the HD fills up and if I miss
deleting them, it shuts my client's biz down entirely. I'm gonna be
gone for a month, and they clueless with regards to the server and
have no IT person, so I had to do SOMETHING. Obviously, that something
wasn't a great choice! (Wish I'd seen whatever your post was - lol)
While the orphan is still generating a couple of "Unable to retrieve
steps" errors in the event log, it's at least no longer creating
backups. I think the job order or whatever that'd be called (hey, I'm
a graphic designer and a hack vbscript/javascript programmer - lol)
must be cached somewhere. I'll track it down eventually.
You have *no idea* how sorry I am that I haven't seen your reply! :D
Thanks again,
Julie
Sunday, February 19, 2012
"insert into" with text type - newbie
Hello,
When I try "Insert Into" with a text column value that's very long, I
only get a cropped version inserted (I know because when I
programmatically access the field, it's cropped-- I'm not just
assuming this from query manager). The text column has a default size
of small, however I don't understand why it is only inserting the
default amoutn instead of the whole string. I am using "Insert Into
table (blah, blah) values (blah, 'loooooooooooooooooooooooooooong
entry')", and programmatically running that command.
I'm stumped. Why is it inserting only part of the long entry value?"vavavoomy2" <vavavoomy2@.yahoo.com> wrote in message
news:c5e42899.0310280942.177d251c@.posting.google.c om...
> Hello,
> When I try "Insert Into" with a text column value that's very long, I
> only get a cropped version inserted (I know because when I
> programmatically access the field, it's cropped-- I'm not just
> assuming this from query manager). The text column has a default size
> of small, however I don't understand why it is only inserting the
> default amoutn instead of the whole string. I am using "Insert Into
> table (blah, blah) values (blah, 'loooooooooooooooooooooooooooong
> entry')", and programmatically running that command.
> I'm stumped. Why is it inserting only part of the long entry value?
What does a "default size of small" mean? Text columns in MSSQL don't have a
variable width, are you talking about a char/varchar column?
In any case, you should probably check if you have ANSI_WARNINGS set OFF in
the connection properties for your client. By default this is on (for OLE
DB/ODBC at least), and inserting data which would be truncated gives an
error. Setting it to off suppresses the error and allows the insert to
happen.
If that isn't the case, can you post your CREATE TABLE statement, and an
INSERT statement which reproduces the problem? Also, does the error happen
when you execute the INSERT manually in Query Analyzer or only
programmatically?
Simon|||"vavavoomy2" <vavavoomy2@.yahoo.com> wrote in message
news:c5e42899.0310280942.177d251c@.posting.google.c om...
> Hello,
> When I try "Insert Into" with a text column value that's very long, I
> only get a cropped version inserted (I know because when I
> programmatically access the field, it's cropped-- I'm not just
> assuming this from query manager). The text column has a default size
> of small, however I don't understand why it is only inserting the
> default amoutn instead of the whole string. I am using "Insert Into
> table (blah, blah) values (blah, 'loooooooooooooooooooooooooooong
> entry')", and programmatically running that command.
> I'm stumped. Why is it inserting only part of the long entry value?
What does a "default size of small" mean? Text columns in MSSQL don't have a
variable width, are you talking about a char/varchar column?
In any case, you should probably check if you have ANSI_WARNINGS set OFF in
the connection properties for your client. By default this is on (for OLE
DB/ODBC at least), and inserting data which would be truncated gives an
error. Setting it to off suppresses the error and allows the insert to
happen.
If that isn't the case, can you post your CREATE TABLE statement, and an
INSERT statement which reproduces the problem? Also, does the error happen
when you execute the INSERT manually in Query Analyzer or only
programmatically?
Simon
Monday, February 13, 2012
"Detach Database" in SQL Server 2005 apparently dropped the database instead
Hello,
I am still trying to get my head around this one. I have been working
on a new version of a website and decided I wanted to make a backup of
the old database file before I tried running any scripts against it.
Since the production website is currently down, I decided to detach
the database, copy the file, and then reattach it. Instead of using
scripts, I used MS SQL Server Management Studio to handle the task.
After I ran the detach command on the database (with the default
options selected), I went to the directory where all of the database
files are stored on the server and the file doesn't exist!!
So, I tried to back up the database file because I didn't have a copy,
and now I don't even have the original. I did a complete Windows file
search on my entire network to try to locate the file, but it is
gone. Well, it isn't the end of the world in my case because I can go
to a prior backup and just move forward, but I really would like to
know what happened so it doesn't happen again.
For starters, is there any way I can query a system table to determine
what the file location was of the database I detached? Second, is
there some "memory only" mode that a database can be put in so when it
is detached it will disappear completely?
TIAHi
It is really strange . I did just at least ten testes to detach the database
via SSMS and it worked just fine
I have SQL Server Dev 2005 (SP2) Edition. Can you reproduce the problem for
another non-produiction database?
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188456828.420852.301950@.m37g2000prh.googlegroups.com...
> Hello,
> I am still trying to get my head around this one. I have been working
> on a new version of a website and decided I wanted to make a backup of
> the old database file before I tried running any scripts against it.
> Since the production website is currently down, I decided to detach
> the database, copy the file, and then reattach it. Instead of using
> scripts, I used MS SQL Server Management Studio to handle the task.
> After I ran the detach command on the database (with the default
> options selected), I went to the directory where all of the database
> files are stored on the server and the file doesn't exist!!
> So, I tried to back up the database file because I didn't have a copy,
> and now I don't even have the original. I did a complete Windows file
> search on my entire network to try to locate the file, but it is
> gone. Well, it isn't the end of the world in my case because I can go
> to a prior backup and just move forward, but I really would like to
> know what happened so it doesn't happen again.
> For starters, is there any way I can query a system table to determine
> what the file location was of the database I detached? Second, is
> there some "memory only" mode that a database can be put in so when it
> is detached it will disappear completely?
> TIA
>|||Sounds weird. No chance SSMS to drop a database when you detach it. There is
only "drop connection" option which contains "drop" action and it doesn't
drop the database.
You said you did a complete seach on your HDD(s) but I guess it must be
around somewhere on your HDD. Maybe you forgot it's name or something?
--
Ekrem Önsoy
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188456828.420852.301950@.m37g2000prh.googlegroups.com...
> Hello,
> I am still trying to get my head around this one. I have been working
> on a new version of a website and decided I wanted to make a backup of
> the old database file before I tried running any scripts against it.
> Since the production website is currently down, I decided to detach
> the database, copy the file, and then reattach it. Instead of using
> scripts, I used MS SQL Server Management Studio to handle the task.
> After I ran the detach command on the database (with the default
> options selected), I went to the directory where all of the database
> files are stored on the server and the file doesn't exist!!
> So, I tried to back up the database file because I didn't have a copy,
> and now I don't even have the original. I did a complete Windows file
> search on my entire network to try to locate the file, but it is
> gone. Well, it isn't the end of the world in my case because I can go
> to a prior backup and just move forward, but I really would like to
> know what happened so it doesn't happen again.
> For starters, is there any way I can query a system table to determine
> what the file location was of the database I detached? Second, is
> there some "memory only" mode that a database can be put in so when it
> is detached it will disappear completely?
> TIA
>|||On Aug 30, 12:12 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Hi
> It is really strange . I did just at least ten testes to detach the database
> via SSMS and it worked just fine
> I have SQL Server Dev 2005 (SP2) Edition. Can you reproduce the problem for
> another non-produiction database?
>
I tried creating a new sample database on the same server and
detaching it, but the files remained. So to your answer your
question, no I cannot repeat the problem.
I also know for sure I used the detach and not the delete command on
the previous database because the dialogs are different.
Is there any SQL command you know of that I can use to determine what
exact file location was detached?|||On Aug 30, 12:24 am, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> Sounds weird. No chance SSMS to drop a database when you detach it. There= is
> only "drop connection" option which contains "drop" action and it doesn't
> drop the database.
> You said you did a complete seach on your HDD(s) but I guess it must be
> around somewhere on your HDD. Maybe you forgot it's name or something?
> --
> Ekrem =D6nsoy
>
Believe me, I didn't forget the name. And I scanned every server (and
even every workstation) using "*.mdf". No dice. Since I set the
server up myself, I am pretty certain that I put the file on the local
server. I have never lost a database before and I have been working
with them for about 10 years.
About a week ago, I shut down the MSSQL service and copied all of the
database files from the server to another location. However, this one
database file wasn't included. This makes me wonder if there was just
a "ghost" database object with no actual file behind it or something.
That is why I would like to try to see what it was referencing if
possible.|||> Is there any SQL command you know of that I can use to determine what
> exact file location was detached?
Its probably where all your user databases are located isn't it?
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188458888.053113.228460@.x35g2000prf.googlegroups.com...
>
> On Aug 30, 12:12 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> Hi
>> It is really strange . I did just at least ten testes to detach the
>> database
>> via SSMS and it worked just fine
>> I have SQL Server Dev 2005 (SP2) Edition. Can you reproduce the problem
>> for
>> another non-produiction database?
> I tried creating a new sample database on the same server and
> detaching it, but the files remained. So to your answer your
> question, no I cannot repeat the problem.
> I also know for sure I used the detach and not the delete command on
> the previous database because the dialogs are different.
> Is there any SQL command you know of that I can use to determine what
> exact file location was detached?
>|||Do you have any old SQL Server backup of the database? If so you can use RESTORE FILELISTONLY to
check the file location.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188459431.752325.247190@.x35g2000prf.googlegroups.com...
On Aug 30, 12:24 am, Ekrem Önsoy <ek...@.btegitim.com> wrote:
> Sounds weird. No chance SSMS to drop a database when you detach it. There is
> only "drop connection" option which contains "drop" action and it doesn't
> drop the database.
> You said you did a complete seach on your HDD(s) but I guess it must be
> around somewhere on your HDD. Maybe you forgot it's name or something?
> --
> Ekrem Önsoy
>
Believe me, I didn't forget the name. And I scanned every server (and
even every workstation) using "*.mdf". No dice. Since I set the
server up myself, I am pretty certain that I put the file on the local
server. I have never lost a database before and I have been working
with them for about 10 years.
About a week ago, I shut down the MSSQL service and copied all of the
database files from the server to another location. However, this one
database file wasn't included. This makes me wonder if there was just
a "ghost" database object with no actual file behind it or something.
That is why I would like to try to see what it was referencing if
possible.|||On Aug 30, 1:19 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Do you have any old SQL Server backup of the database? If so you can use RESTORE FILELISTONLY to
> check the file location.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
Actually all I have is a database that I created on another computer
and then used DTS to copy tables with data over to it. This was done
before I upgraded to SQL 2005. I don't technically have a "backup" in
the SQL Server sense of the word.|||Do you have an old backup of the master database on the computer where the database existed? If so,
you could restore that backup somewhere and check the sysaltfiles table. Will only give you the mdf
file, but that might be good enough...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188467622.686367.250240@.e9g2000prf.googlegroups.com...
> On Aug 30, 1:19 am, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> Do you have any old SQL Server backup of the database? If so you can use RESTORE FILELISTONLY to
>> check the file location.
>> --
>> Tibor Karaszi, SQL Server
>> MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> Actually all I have is a database that I created on another computer
> and then used DTS to copy tables with data over to it. This was done
> before I upgraded to SQL 2005. I don't technically have a "backup" in
> the SQL Server sense of the word.
>|||No, I don't have any backups of the master database. This server has
been offline for almost a year. I was just in the process of backing
up the data in the primary database on the server by making a copy of
the file. I plan to set up backups going forward but I didn't have
any before (which is why I decided to detach the database in the first
place).
The file either disappeared when I ran the command to detach it or it
didn't exist before that. If it didn't exist that is another
inexplicable problem - I know I left it in place. Not to mention, I
didn't get any sql errors that the file was missing or anything like
that.
On Aug 30, 3:08 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Do you have an old backup of the master database on the computer where the database existed? If so,
> you could restore that backup somewhere and check the sysaltfiles table. Will only give you the mdf
> file, but that might be good enough...
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "NightOwl888" <sstorh...@.webuniverse.net> wrote in message
> news:1188467622.686367.250240@.e9g2000prf.googlegroups.com...|||I figured out the problem. The production database file was prefixed
by the word "Test", the same as the test database. They were in 2
different directories, but they were all on the same server. I
thought that the production database was gone, but it was just named
"Test".
At some point I must have copied the Test database and attached it as
production. This makes sense because still now I am having issues
moving tables from one database to another.
Well, I am glad that I don't have to revert to an older copy and lose
some data. I will definitely back up master and set up some backup
jobs now, too.|||backup...backup..backup...;-)
Make it a best practice to always backup the master database anytime you do
something on the server even if the server is an old one. You'll never know
when it will become handy
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188520731.793321.109640@.q3g2000prf.googlegroups.com...
>I figured out the problem. The production database file was prefixed
> by the word "Test", the same as the test database. They were in 2
> different directories, but they were all on the same server. I
> thought that the production database was gone, but it was just named
> "Test".
> At some point I must have copied the Test database and attached it as
> production. This makes sense because still now I am having issues
> moving tables from one database to another.
> Well, I am glad that I don't have to revert to an older copy and lose
> some data. I will definitely back up master and set up some backup
> jobs now, too.
>
I am still trying to get my head around this one. I have been working
on a new version of a website and decided I wanted to make a backup of
the old database file before I tried running any scripts against it.
Since the production website is currently down, I decided to detach
the database, copy the file, and then reattach it. Instead of using
scripts, I used MS SQL Server Management Studio to handle the task.
After I ran the detach command on the database (with the default
options selected), I went to the directory where all of the database
files are stored on the server and the file doesn't exist!!
So, I tried to back up the database file because I didn't have a copy,
and now I don't even have the original. I did a complete Windows file
search on my entire network to try to locate the file, but it is
gone. Well, it isn't the end of the world in my case because I can go
to a prior backup and just move forward, but I really would like to
know what happened so it doesn't happen again.
For starters, is there any way I can query a system table to determine
what the file location was of the database I detached? Second, is
there some "memory only" mode that a database can be put in so when it
is detached it will disappear completely?
TIAHi
It is really strange . I did just at least ten testes to detach the database
via SSMS and it worked just fine
I have SQL Server Dev 2005 (SP2) Edition. Can you reproduce the problem for
another non-produiction database?
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188456828.420852.301950@.m37g2000prh.googlegroups.com...
> Hello,
> I am still trying to get my head around this one. I have been working
> on a new version of a website and decided I wanted to make a backup of
> the old database file before I tried running any scripts against it.
> Since the production website is currently down, I decided to detach
> the database, copy the file, and then reattach it. Instead of using
> scripts, I used MS SQL Server Management Studio to handle the task.
> After I ran the detach command on the database (with the default
> options selected), I went to the directory where all of the database
> files are stored on the server and the file doesn't exist!!
> So, I tried to back up the database file because I didn't have a copy,
> and now I don't even have the original. I did a complete Windows file
> search on my entire network to try to locate the file, but it is
> gone. Well, it isn't the end of the world in my case because I can go
> to a prior backup and just move forward, but I really would like to
> know what happened so it doesn't happen again.
> For starters, is there any way I can query a system table to determine
> what the file location was of the database I detached? Second, is
> there some "memory only" mode that a database can be put in so when it
> is detached it will disappear completely?
> TIA
>|||Sounds weird. No chance SSMS to drop a database when you detach it. There is
only "drop connection" option which contains "drop" action and it doesn't
drop the database.
You said you did a complete seach on your HDD(s) but I guess it must be
around somewhere on your HDD. Maybe you forgot it's name or something?
--
Ekrem Önsoy
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188456828.420852.301950@.m37g2000prh.googlegroups.com...
> Hello,
> I am still trying to get my head around this one. I have been working
> on a new version of a website and decided I wanted to make a backup of
> the old database file before I tried running any scripts against it.
> Since the production website is currently down, I decided to detach
> the database, copy the file, and then reattach it. Instead of using
> scripts, I used MS SQL Server Management Studio to handle the task.
> After I ran the detach command on the database (with the default
> options selected), I went to the directory where all of the database
> files are stored on the server and the file doesn't exist!!
> So, I tried to back up the database file because I didn't have a copy,
> and now I don't even have the original. I did a complete Windows file
> search on my entire network to try to locate the file, but it is
> gone. Well, it isn't the end of the world in my case because I can go
> to a prior backup and just move forward, but I really would like to
> know what happened so it doesn't happen again.
> For starters, is there any way I can query a system table to determine
> what the file location was of the database I detached? Second, is
> there some "memory only" mode that a database can be put in so when it
> is detached it will disappear completely?
> TIA
>|||On Aug 30, 12:12 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
> Hi
> It is really strange . I did just at least ten testes to detach the database
> via SSMS and it worked just fine
> I have SQL Server Dev 2005 (SP2) Edition. Can you reproduce the problem for
> another non-produiction database?
>
I tried creating a new sample database on the same server and
detaching it, but the files remained. So to your answer your
question, no I cannot repeat the problem.
I also know for sure I used the detach and not the delete command on
the previous database because the dialogs are different.
Is there any SQL command you know of that I can use to determine what
exact file location was detached?|||On Aug 30, 12:24 am, Ekrem =D6nsoy <ek...@.btegitim.com> wrote:
> Sounds weird. No chance SSMS to drop a database when you detach it. There= is
> only "drop connection" option which contains "drop" action and it doesn't
> drop the database.
> You said you did a complete seach on your HDD(s) but I guess it must be
> around somewhere on your HDD. Maybe you forgot it's name or something?
> --
> Ekrem =D6nsoy
>
Believe me, I didn't forget the name. And I scanned every server (and
even every workstation) using "*.mdf". No dice. Since I set the
server up myself, I am pretty certain that I put the file on the local
server. I have never lost a database before and I have been working
with them for about 10 years.
About a week ago, I shut down the MSSQL service and copied all of the
database files from the server to another location. However, this one
database file wasn't included. This makes me wonder if there was just
a "ghost" database object with no actual file behind it or something.
That is why I would like to try to see what it was referencing if
possible.|||> Is there any SQL command you know of that I can use to determine what
> exact file location was detached?
Its probably where all your user databases are located isn't it?
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188458888.053113.228460@.x35g2000prf.googlegroups.com...
>
> On Aug 30, 12:12 am, "Uri Dimant" <u...@.iscar.co.il> wrote:
>> Hi
>> It is really strange . I did just at least ten testes to detach the
>> database
>> via SSMS and it worked just fine
>> I have SQL Server Dev 2005 (SP2) Edition. Can you reproduce the problem
>> for
>> another non-produiction database?
> I tried creating a new sample database on the same server and
> detaching it, but the files remained. So to your answer your
> question, no I cannot repeat the problem.
> I also know for sure I used the detach and not the delete command on
> the previous database because the dialogs are different.
> Is there any SQL command you know of that I can use to determine what
> exact file location was detached?
>|||Do you have any old SQL Server backup of the database? If so you can use RESTORE FILELISTONLY to
check the file location.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188459431.752325.247190@.x35g2000prf.googlegroups.com...
On Aug 30, 12:24 am, Ekrem Önsoy <ek...@.btegitim.com> wrote:
> Sounds weird. No chance SSMS to drop a database when you detach it. There is
> only "drop connection" option which contains "drop" action and it doesn't
> drop the database.
> You said you did a complete seach on your HDD(s) but I guess it must be
> around somewhere on your HDD. Maybe you forgot it's name or something?
> --
> Ekrem Önsoy
>
Believe me, I didn't forget the name. And I scanned every server (and
even every workstation) using "*.mdf". No dice. Since I set the
server up myself, I am pretty certain that I put the file on the local
server. I have never lost a database before and I have been working
with them for about 10 years.
About a week ago, I shut down the MSSQL service and copied all of the
database files from the server to another location. However, this one
database file wasn't included. This makes me wonder if there was just
a "ghost" database object with no actual file behind it or something.
That is why I would like to try to see what it was referencing if
possible.|||On Aug 30, 1:19 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Do you have any old SQL Server backup of the database? If so you can use RESTORE FILELISTONLY to
> check the file location.
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
Actually all I have is a database that I created on another computer
and then used DTS to copy tables with data over to it. This was done
before I upgraded to SQL 2005. I don't technically have a "backup" in
the SQL Server sense of the word.|||Do you have an old backup of the master database on the computer where the database existed? If so,
you could restore that backup somewhere and check the sysaltfiles table. Will only give you the mdf
file, but that might be good enough...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188467622.686367.250240@.e9g2000prf.googlegroups.com...
> On Aug 30, 1:19 am, "Tibor Karaszi"
> <tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
>> Do you have any old SQL Server backup of the database? If so you can use RESTORE FILELISTONLY to
>> check the file location.
>> --
>> Tibor Karaszi, SQL Server
>> MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> Actually all I have is a database that I created on another computer
> and then used DTS to copy tables with data over to it. This was done
> before I upgraded to SQL 2005. I don't technically have a "backup" in
> the SQL Server sense of the word.
>|||No, I don't have any backups of the master database. This server has
been offline for almost a year. I was just in the process of backing
up the data in the primary database on the server by making a copy of
the file. I plan to set up backups going forward but I didn't have
any before (which is why I decided to detach the database in the first
place).
The file either disappeared when I ran the command to detach it or it
didn't exist before that. If it didn't exist that is another
inexplicable problem - I know I left it in place. Not to mention, I
didn't get any sql errors that the file was missing or anything like
that.
On Aug 30, 3:08 am, "Tibor Karaszi"
<tibor_please.no.email_kara...@.hotmail.nomail.com> wrote:
> Do you have an old backup of the master database on the computer where the database existed? If so,
> you could restore that backup somewhere and check the sysaltfiles table. Will only give you the mdf
> file, but that might be good enough...
> --
> Tibor Karaszi, SQL Server MVPhttp://www.karaszi.com/sqlserver/default.asphttp://sqlblog.com/blogs/tibor_karaszi
> "NightOwl888" <sstorh...@.webuniverse.net> wrote in message
> news:1188467622.686367.250240@.e9g2000prf.googlegroups.com...|||I figured out the problem. The production database file was prefixed
by the word "Test", the same as the test database. They were in 2
different directories, but they were all on the same server. I
thought that the production database was gone, but it was just named
"Test".
At some point I must have copied the Test database and attached it as
production. This makes sense because still now I am having issues
moving tables from one database to another.
Well, I am glad that I don't have to revert to an older copy and lose
some data. I will definitely back up master and set up some backup
jobs now, too.|||backup...backup..backup...;-)
Make it a best practice to always backup the master database anytime you do
something on the server even if the server is an old one. You'll never know
when it will become handy
"NightOwl888" <sstorhaug@.webuniverse.net> wrote in message
news:1188520731.793321.109640@.q3g2000prf.googlegroups.com...
>I figured out the problem. The production database file was prefixed
> by the word "Test", the same as the test database. They were in 2
> different directories, but they were all on the same server. I
> thought that the production database was gone, but it was just named
> "Test".
> At some point I must have copied the Test database and attached it as
> production. This makes sense because still now I am having issues
> moving tables from one database to another.
> Well, I am glad that I don't have to revert to an older copy and lose
> some data. I will definitely back up master and set up some backup
> jobs now, too.
>
Saturday, February 11, 2012
"craxdrt9.dll" version "9.2.3.1368" errors at runtime with multiple threads STA
"craxdrt9.dll" version "9.2.3.1368" errors at runtime with multiple threads with ApartmentState as STA or MTA
I would appreciate any help on the following:
Keep getting the the following error from "Crystal Reports":
- Using "C:\Program Files\Crystal Decisions\Report Designer Component\craxdrt9.dll" version "9.2.3.1368"
Error on using multiple threads with thread.ApartmentState = ApartmentState.STA:
Object reference not set to an instance of an object.
at CRAXDRT.DatabaseTableClass.SetPrivateData(Int32 dataTag, Object data)
at TestCrystalReports1.QCrystalReports.QCrystalReportObject.processReport(IReport& iReport, Hashtable collReportDataRs, Boolean& m_btnCancelPressed) in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\QCrystalReports\QCrystalReportObject.cs:line 127
at TestCrystalReports1.QCrystalReports.QCrystalReportObject.processSubReport(IReport& iReport, Hashtable collReportDataRs, Boolean& m_btnCancelPressed) in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\QCrystalReports\QCrystalReportObject.cs:line 179
at TestCrystalReports1.QCrystalReports.QCrystalReportObject.runPrintJob(String rptFilePathStr, Hashtable recordsetHashTable) in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\QCrystalReports\QCrystalReportObject.cs:line 81
at TestCrystalReports1.PrintRequest.runPrintRequest() in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\PrintRequest.cs:line 79
Error on using multiple threads with thread.ApartmentState = ApartmentState.STA or ApartmentState.MTA:
Invalid directory.
at CRAXDRT.ApplicationClass.OpenReport(String pFileName, Object OpenMethod)
at TestCrystalReports1.QCrystalReports.QCrystalReportObject.runPrintJob(String rptFilePathStr, Hashtable recordsetHashTable) in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\QCrystalReports\QCrystalReportObject.cs:line 77
at TestCrystalReports1.PrintRequest.runPrintRequest() in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\PrintRequest.cs:line 79
Code extract - C# / .net application:
References: Interop.CRAXDRT.dll
- Thread running the "processReport" method - ApartmentState - tried both STA & MTA
- Problem usually occurs in case of multiple threads or multiple calls within a thread
private static int DATA_INPUT_TYPE_ADO = 3;
private void processReport (
ref IReport iReport, // Report instance
System.Collections.Hashtable collReportDataRs, // Report data
ref bool m_btnCancelPressed // Cancel button
)
{
// Get the database
IDatabase iDatabase = (IDatabase) iReport.Database;
// Get the database tables
IDatabaseTables iDatabaseTables = (IDatabaseTables) iDatabase.Tables;
// Loop through the tables
int iTotalTables = iDatabaseTables.Count;
for ( int iTblCount = 1; iTblCount <= iTotalTables; ++iTblCount )
{
if ( m_btnCancelPressed == true )
return;
// Get table name
IDatabaseTable iDatabaseTable = (IDatabaseTable) iDatabaseTables[iTblCount];
// Get the relevant recordset from the collection passed
System.String bsTableName = iDatabaseTable.Name;
ADODB._Recordset rs = (ADODB._Recordset) collReportDataRs [ bsTableName ];
if ( rs == null )
{
throw new Exception( "Data not found: " + bsTableName );
}
// Set data for this table
iDatabaseTable.SetPrivateData( DATA_INPUT_TYPE_ADO, rs);
}
}Are any of Dlls missing?
See if you find asnwer here
http://support.businessobjects.com/
I would appreciate any help on the following:
Keep getting the the following error from "Crystal Reports":
- Using "C:\Program Files\Crystal Decisions\Report Designer Component\craxdrt9.dll" version "9.2.3.1368"
Error on using multiple threads with thread.ApartmentState = ApartmentState.STA:
Object reference not set to an instance of an object.
at CRAXDRT.DatabaseTableClass.SetPrivateData(Int32 dataTag, Object data)
at TestCrystalReports1.QCrystalReports.QCrystalReportObject.processReport(IReport& iReport, Hashtable collReportDataRs, Boolean& m_btnCancelPressed) in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\QCrystalReports\QCrystalReportObject.cs:line 127
at TestCrystalReports1.QCrystalReports.QCrystalReportObject.processSubReport(IReport& iReport, Hashtable collReportDataRs, Boolean& m_btnCancelPressed) in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\QCrystalReports\QCrystalReportObject.cs:line 179
at TestCrystalReports1.QCrystalReports.QCrystalReportObject.runPrintJob(String rptFilePathStr, Hashtable recordsetHashTable) in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\QCrystalReports\QCrystalReportObject.cs:line 81
at TestCrystalReports1.PrintRequest.runPrintRequest() in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\PrintRequest.cs:line 79
Error on using multiple threads with thread.ApartmentState = ApartmentState.STA or ApartmentState.MTA:
Invalid directory.
at CRAXDRT.ApplicationClass.OpenReport(String pFileName, Object OpenMethod)
at TestCrystalReports1.QCrystalReports.QCrystalReportObject.runPrintJob(String rptFilePathStr, Hashtable recordsetHashTable) in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\QCrystalReports\QCrystalReportObject.cs:line 77
at TestCrystalReports1.PrintRequest.runPrintRequest() in E:\QECM\Tools\ReportingTools\TestApps\TestCrystalReports1\PrintRequest.cs:line 79
Code extract - C# / .net application:
References: Interop.CRAXDRT.dll
- Thread running the "processReport" method - ApartmentState - tried both STA & MTA
- Problem usually occurs in case of multiple threads or multiple calls within a thread
private static int DATA_INPUT_TYPE_ADO = 3;
private void processReport (
ref IReport iReport, // Report instance
System.Collections.Hashtable collReportDataRs, // Report data
ref bool m_btnCancelPressed // Cancel button
)
{
// Get the database
IDatabase iDatabase = (IDatabase) iReport.Database;
// Get the database tables
IDatabaseTables iDatabaseTables = (IDatabaseTables) iDatabase.Tables;
// Loop through the tables
int iTotalTables = iDatabaseTables.Count;
for ( int iTblCount = 1; iTblCount <= iTotalTables; ++iTblCount )
{
if ( m_btnCancelPressed == true )
return;
// Get table name
IDatabaseTable iDatabaseTable = (IDatabaseTable) iDatabaseTables[iTblCount];
// Get the relevant recordset from the collection passed
System.String bsTableName = iDatabaseTable.Name;
ADODB._Recordset rs = (ADODB._Recordset) collReportDataRs [ bsTableName ];
if ( rs == null )
{
throw new Exception( "Data not found: " + bsTableName );
}
// Set data for this table
iDatabaseTable.SetPrivateData( DATA_INPUT_TYPE_ADO, rs);
}
}Are any of Dlls missing?
See if you find asnwer here
http://support.businessobjects.com/
Thursday, February 9, 2012
"Attempt to repair any minor problems." What is the point?
I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged=20
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on=20
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free=20
space)...
Rebuilding indexes for table 'AccessStatusMap'
......................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:=20
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating=20
point exception occurred in the user process. Current=20
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC=20
execution completed. If DBCC printed error messages,=20
contact your system administrator.
=BFDo Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
=20
>--Original Message--
>What is the point of having this checkbox on the Database=20
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to=20
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair=20
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be=20
running.
>For SqlAgent to be running, it requires NOT Single User=20
Mode.
>
>.
>
My guess is you have some invalid float data in the table/index. Turn on
trace flag 2570 and run DBCC CHECKTABLE on the table in question. 2570
switches on some extra data range value checking of things like floats and
dates. FYI: this functionality is controlled by documented T-SQL in SQL
Server 2005 rather than a trace flag.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ignacio" <anonymous@.discussions.microsoft.com> wrote in message
news:1bfe01c44737$1dc83550$3501280a@.phx.gbl...
I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free
space)...
Rebuilding indexes for table 'AccessStatusMap'
......................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating
point exception occurred in the user process. Current
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
execution completed. If DBCC printed error messages,
contact your system administrator.
Do Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
>--Original Message--
>What is the point of having this checkbox on the Database
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be
running.
>For SqlAgent to be running, it requires NOT Single User
Mode.
>
>.
>
Microsoft (R) SQLMaint Utility (Unicode), Version Logged=20
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on=20
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free=20
space)...
Rebuilding indexes for table 'AccessStatusMap'
......................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:=20
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating=20
point exception occurred in the user process. Current=20
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC=20
execution completed. If DBCC printed error messages,=20
contact your system administrator.
=BFDo Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
=20
>--Original Message--
>What is the point of having this checkbox on the Database=20
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to=20
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair=20
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be=20
running.
>For SqlAgent to be running, it requires NOT Single User=20
Mode.
>
>.
>
My guess is you have some invalid float data in the table/index. Turn on
trace flag 2570 and run DBCC CHECKTABLE on the table in question. 2570
switches on some extra data range value checking of things like floats and
dates. FYI: this functionality is controlled by documented T-SQL in SQL
Server 2005 rather than a trace flag.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ignacio" <anonymous@.discussions.microsoft.com> wrote in message
news:1bfe01c44737$1dc83550$3501280a@.phx.gbl...
I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free
space)...
Rebuilding indexes for table 'AccessStatusMap'
......................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating
point exception occurred in the user process. Current
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
execution completed. If DBCC printed error messages,
contact your system administrator.
Do Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
>--Original Message--
>What is the point of having this checkbox on the Database
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be
running.
>For SqlAgent to be running, it requires NOT Single User
Mode.
>
>.
>
"Attempt to repair any minor problems." What is the point?
I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged=20
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on=20
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free=20
space)...
Rebuilding indexes for table 'AccessStatusMap'
.....................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:=20
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating=20
point exception occurred in the user process. Current=20
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC=20
execution completed. If DBCC printed error messages,=20
contact your system administrator.
=BFDo Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
=20
>--Original Message--
>What is the point of having this checkbox on the Database=20
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to=20
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair=20
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be=20
running.
>For SqlAgent to be running, it requires NOT Single User=20
Mode.
>
>.
>My guess is you have some invalid float data in the table/index. Turn on
trace flag 2570 and run DBCC CHECKTABLE on the table in question. 2570
switches on some extra data range value checking of things like floats and
dates. FYI: this functionality is controlled by documented T-SQL in SQL
Server 2005 rather than a trace flag.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ignacio" <anonymous@.discussions.microsoft.com> wrote in message
news:1bfe01c44737$1dc83550$3501280a@.phx.gbl...
I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free
space)...
Rebuilding indexes for table 'AccessStatusMap'
.....................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating
point exception occurred in the user process. Current
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
execution completed. If DBCC printed error messages,
contact your system administrator.
Do Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
>--Original Message--
>What is the point of having this checkbox on the Database
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be
running.
>For SqlAgent to be running, it requires NOT Single User
Mode.
>
>.
>
Microsoft (R) SQLMaint Utility (Unicode), Version Logged=20
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on=20
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free=20
space)...
Rebuilding indexes for table 'AccessStatusMap'
.....................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:=20
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating=20
point exception occurred in the user process. Current=20
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC=20
execution completed. If DBCC printed error messages,=20
contact your system administrator.
=BFDo Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
=20
>--Original Message--
>What is the point of having this checkbox on the Database=20
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to=20
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair=20
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be=20
running.
>For SqlAgent to be running, it requires NOT Single User=20
Mode.
>
>.
>My guess is you have some invalid float data in the table/index. Turn on
trace flag 2570 and run DBCC CHECKTABLE on the table in question. 2570
switches on some extra data range value checking of things like floats and
dates. FYI: this functionality is controlled by documented T-SQL in SQL
Server 2005 rather than a trace flag.
Regards.
Paul Randal
Dev Lead, Microsoft SQL Server Storage Engine
This posting is provided "AS IS" with no warranties, and confers no rights.
"Ignacio" <anonymous@.discussions.microsoft.com> wrote in message
news:1bfe01c44737$1dc83550$3501280a@.phx.gbl...
I have done a maintenance plan and I have this error:
Microsoft (R) SQLMaint Utility (Unicode), Version Logged
on to SQL Server 'Cluster instance' as 'User' (trusted)
Starting maintenance plan 'DB Maintenance Plan5' on
31/05/2004 18:59:00
[1] Database xxxxxx: Index Rebuild (leaving 10%% free
space)...
Rebuilding indexes for table 'AccessStatusMap'
.....................
Rebuilding indexes for table 'TransactionPropertyMap'
[Microsoft SQL-DMO (ODBC SQLState: 42000)] Error 3628:
[Microsoft][ODBC SQL Server Driver][SQL Server]A floating
point exception occurred in the user process. Current
transaction is canceled.
[Microsoft][ODBC SQL Server Driver][SQL Server]DBCC
execution completed. If DBCC printed error messages,
contact your system administrator.
Do Anybody know, why is it the cause of this error?
Sincerely,
Ignacio
>--Original Message--
>What is the point of having this checkbox on the Database
Mainenance Plan
>properties (Integrity tab) window?
>
>For the plan to fix minor problems, it requires the db to
be in Single User
>Mode.
>"[Microsoft][ODBC SQL Server Driver][SQL Server]Repair
statement not
>processed. Database needs to be in single user mode."
>For the plan to execute it requires SQLAgent to be
running.
>For SqlAgent to be running, it requires NOT Single User
Mode.
>
>.
>
Friday, January 27, 2012
"...could not load DCOM"
Hello.
I have the same problem.
Version is
Microsoft SQL Server 2000 - 8.00.2039 - Service Pack 4 installed.
Before installation SP4 I had error "Unexpected NULL value returned for
column '[OpenXML].OutSourcedPartCount' from the OLE DB provider
'OpenXML'. This column cannot be NULL." when I didn't specified values
(no XML branches) for columns with default values.
Any ideas?
Zevakov Andrew
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message184753.htmlI can add that in event viewer I have such entries after calling my
stored proc :
Source: MSSQLSERVER
"Failed to Initialize COM (CoInitializeEx returned 80010119)"
"Heterogeneous Queries and Remote RPC will be disabled."
Zevakov Andrew
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message184753.html
I have the same problem.
Version is
Microsoft SQL Server 2000 - 8.00.2039 - Service Pack 4 installed.
Before installation SP4 I had error "Unexpected NULL value returned for
column '[OpenXML].OutSourcedPartCount' from the OLE DB provider
'OpenXML'. This column cannot be NULL." when I didn't specified values
(no XML branches) for columns with default values.
Any ideas?
Zevakov Andrew
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message184753.htmlI can add that in event viewer I have such entries after calling my
stored proc :
Source: MSSQLSERVER
"Failed to Initialize COM (CoInitializeEx returned 80010119)"
"Heterogeneous Queries and Remote RPC will be disabled."
Zevakov Andrew
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message184753.html
Subscribe to:
Posts (Atom)
