Showing posts with label previous. Show all posts
Showing posts with label previous. Show all posts

Friday, March 23, 2012

excel data mining add-in for categorical data

Thank you very much for your previous answers conserning clustering algorithm.

I change a bit my data and now I can get two and three clusters as I wish.

But now I have a different question. I wish to keep my Structure and Model for further trials with different algorithm values, like cardinality. I tried the following

I selected in excel Data Mining and then the option cluster button.

Then in the cluster wizard I chose analysis service data source and I reform the query as I need adding only at the end

where "STAFF_YES" = 1. Then I choose the needed columns and target value. Finally I select browse model, enable drill through only and I finish the wizard and get some results, rather good. But i need to try again with different parameters.

I tried Business intelligent Studio to check my Analysis service. The structure were here but when I changed any parameter and I tried to reprocess I got the following messages

Processing Mining Structure 'try Structure_1' completed successfully.
Start time: 5/8/2007 4:55:08 μμ; End time: 5/8/2007 4:55:08 μμ; Duration: 0:00:00
Processing Dimension 'try Structure_1 ~MC-__RowIndex' completed successfully.
Start time: 5/8/2007 4:55:08 μμ; End time: 5/8/2007 4:55:08 μμ; Duration: 0:00:00
Processing Dimension Attribute '(All)' completed successfully.
Start time: 5/8/2007 4:55:08 μμ; End time: 5/8/2007 4:55:08 μμ; Duration: 0:00:00
Processing Dimension Attribute 'EPI_CELL_SINO_GOOD' completed successfully.
Start time: 5/8/2007 4:55:08 μμ; End time: 5/8/2007 4:55:08 μμ; Duration: 0:00:00
Processing Dimension Attribute 'EPI_CELL_SINO_LOOSE' completed successfully.
Start time: 5/8/2007 4:55:08 μμ; End time: 5/8/2007 4:55:08 μμ; Duration: 0:00:00
Errors and Warnings from Response
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: An unexpected error occurred (file 'pcprocbinding.cpp', line 6645, function 'PCDBProcBinding:Tongue TiedelectOrChangeCartridge').
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'try Structure_1 ~MC-__RowIndex', Name of 'try Structure_1 ~MC-__RowIndex' was being processed.
Errors in the OLAP storage engine: An error occurred while the 'EPI_CELL_SINO_LOOSE' attribute of the 'try Structure_1 ~MC-__RowIndex' dimension from the 'DMAddinsDB2' database was being processed.
Internal error: The operation terminated unsuccessfully.
Internal error: The operation terminated unsuccessfully.
Internal error: An unexpected error occurred (file 'pcprocbinding.cpp', line 6645, function 'PCDBProcBinding:Tongue TiedelectOrChangeCartridge').
Errors in the OLAP storage engine: An error occurred while the dimension, with the ID of 'try Structure_1 ~MC-__RowIndex', Name of 'try Structure_1 ~MC-__RowIndex' was being processed.
Errors in the OLAP storage engine: An error occurred while the 'EPI_CELL_SINO_GOOD' attribute of the 'try Structure_1 ~MC-__RowIndex' dimension from the 'DMAddinsDB2' database was being processed.

And no change to the structure take place.

Please help me if you can

Thank you in advnce

Best regards.

Manolis

We discovered this issue and it will be addressed in a future release but currently there is no workaround for this problem using BI Dev Studio.

Here is an alternate way of doing the same thing:

- in Excel, under the Data mining tab, select the "Advanced\Add model to mining structure" option

- create a new model using whatever algorithm (Clustering, I assume) and setting any parameters you might want.

The wizard will create a new model inside the same structure and process it.

If having multiple models does not bother your, you can leave them all inside the structure. Otherwise, you can delete the old models using the Manage Models option in the Data Mining tab.

Also, after executing the steps you mentioned in the BI Dev Studio, chances are that your mining structure is in an incosistent state. You can restore its original (processed) state by invoking, under Manage Models, Process structure with new data then point to the data source you used in creating the structure the first time

Hope this helps

sql

Wednesday, March 7, 2012

Event_id 6008 - Unexpected Reboot

I have a Windows 2000 SP4 server running SQL Server 2000
Enterprise Edition that continually gets an event 6008
(the previous shutdown was unexpected). I also get the
following bugcheck and memory error. Does anyone know
what these errors are and how to correct them? Thanks.
Event Type:Information
Event Source:Save Dump
Event Category:None
Event ID:1001
Date:9/24/2004
Time:11:38:37 AM
User:N/A
Computer:UHDSSAPPSERV
Description:
The computer has rebooted from a bugcheck. The bugcheck
was: 0x000000d1 (0x8d0ee101, 0x00000002, 0x00000000,
0x8d0ee101). Microsoft Windows 2000 [v15.2195]. A dump was
saved in: C:\WINNT\MEMORY.DMP.
Event Type:Information
Event Source:Application Popup
Event Category:None
Event ID:26
Date:9/24/2004
Time:11:23:47 AM
User:N/A
Computer:UHDSSAPPSERV
Description:
Application popup: Windows - Virtual Memory Minimum Too
Low : Your system is low on virtual memory. Windows is
increasing the size of your virtual memory paging file.
During this process, memory requests for some applications
may be denied. For more information, see Help.
The memory ran low first - you can monitor memory on the
server with System Monitor.
In terms of the reboot and dump, you can use the Windows
Debugging tools to analyzer the memory dump file to
determine was caused the server to crash. You can get more
information and download the debugging tools from:
http://www.microsoft.com/whdc/devtoo...g/default.mspx
-Sue
On Tue, 28 Sep 2004 11:09:31 -0700, "Chris"
<anonymous@.discussions.microsoft.com> wrote:

>I have a Windows 2000 SP4 server running SQL Server 2000
>Enterprise Edition that continually gets an event 6008
>(the previous shutdown was unexpected). I also get the
>following bugcheck and memory error. Does anyone know
>what these errors are and how to correct them? Thanks.
>Event Type:Information
>Event Source:Save Dump
>Event Category:None
>Event ID:1001
>Date:9/24/2004
>Time:11:38:37 AM
>User:N/A
>Computer:UHDSSAPPSERV
>Description:
>The computer has rebooted from a bugcheck. The bugcheck
>was: 0x000000d1 (0x8d0ee101, 0x00000002, 0x00000000,
>0x8d0ee101). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\MEMORY.DMP.
>Event Type:Information
>Event Source:Application Popup
>Event Category:None
>Event ID:26
>Date:9/24/2004
>Time:11:23:47 AM
>User:N/A
>Computer:UHDSSAPPSERV
>Description:
>Application popup: Windows - Virtual Memory Minimum Too
>Low : Your system is low on virtual memory. Windows is
>increasing the size of your virtual memory paging file.
>During this process, memory requests for some applications
>may be denied. For more information, see Help.
|||Thanks for the reply. I ran windbg and got the following
message:
BugCheck D1, {1060213, 2, 0, f64d1932}
Probably caused by : SCSIPORT.SYS ( SCSIPORT!
SpAllocateSrbExtension+156 )
After searching Microsoft, there seemed to be many
potential causes for scsiport.sys errors, but could not
find one that exactly matched this criteria.
Followup: MachineOwner
>--Original Message--
>The memory ran low first - you can monitor memory on the
>server with System Monitor.
>In terms of the reboot and dump, you can use the Windows
>Debugging tools to analyzer the memory dump file to
>determine was caused the server to crash. You can get more
>information and download the debugging tools from:
>http://www.microsoft.com/whdc/devtoo...ging/default.m
spx[vbcol=seagreen]
>-Sue
>On Tue, 28 Sep 2004 11:09:31 -0700, "Chris"
><anonymous@.discussions.microsoft.com> wrote:
was[vbcol=seagreen]
applications
>.
>

Sunday, February 26, 2012

Event_id 6008 - Unexpected Reboot

I have a Windows 2000 SP4 server running SQL Server 2000
Enterprise Edition that continually gets an event 6008
(the previous shutdown was unexpected). I also get the
following bugcheck and memory error. Does anyone know
what these errors are and how to correct them? Thanks.
Event Type: Information
Event Source: Save Dump
Event Category: None
Event ID: 1001
Date: 9/24/2004
Time: 11:38:37 AM
User: N/A
Computer: UHDSSAPPSERV
Description:
The computer has rebooted from a bugcheck. The bugcheck
was: 0x000000d1 (0x8d0ee101, 0x00000002, 0x00000000,
0x8d0ee101). Microsoft Windows 2000 [v15.2195]. A dump was
saved in: C:\WINNT\MEMORY.DMP.
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 9/24/2004
Time: 11:23:47 AM
User: N/A
Computer: UHDSSAPPSERV
Description:
Application popup: Windows - Virtual Memory Minimum Too
Low : Your system is low on virtual memory. Windows is
increasing the size of your virtual memory paging file.
During this process, memory requests for some applications
may be denied. For more information, see Help.The memory ran low first - you can monitor memory on the
server with System Monitor.
In terms of the reboot and dump, you can use the Windows
Debugging tools to analyzer the memory dump file to
determine was caused the server to crash. You can get more
information and download the debugging tools from:
http://www.microsoft.com/whdc/devtools/debugging/default.mspx
-Sue
On Tue, 28 Sep 2004 11:09:31 -0700, "Chris"
<anonymous@.discussions.microsoft.com> wrote:
>I have a Windows 2000 SP4 server running SQL Server 2000
>Enterprise Edition that continually gets an event 6008
>(the previous shutdown was unexpected). I also get the
>following bugcheck and memory error. Does anyone know
>what these errors are and how to correct them? Thanks.
>Event Type: Information
>Event Source: Save Dump
>Event Category: None
>Event ID: 1001
>Date: 9/24/2004
>Time: 11:38:37 AM
>User: N/A
>Computer: UHDSSAPPSERV
>Description:
>The computer has rebooted from a bugcheck. The bugcheck
>was: 0x000000d1 (0x8d0ee101, 0x00000002, 0x00000000,
>0x8d0ee101). Microsoft Windows 2000 [v15.2195]. A dump was
>saved in: C:\WINNT\MEMORY.DMP.
>Event Type: Information
>Event Source: Application Popup
>Event Category: None
>Event ID: 26
>Date: 9/24/2004
>Time: 11:23:47 AM
>User: N/A
>Computer: UHDSSAPPSERV
>Description:
>Application popup: Windows - Virtual Memory Minimum Too
>Low : Your system is low on virtual memory. Windows is
>increasing the size of your virtual memory paging file.
>During this process, memory requests for some applications
>may be denied. For more information, see Help.|||Thanks for the reply. I ran windbg and got the following
message:
BugCheck D1, {1060213, 2, 0, f64d1932}
Probably caused by : SCSIPORT.SYS ( SCSIPORT!
SpAllocateSrbExtension+156 )
After searching Microsoft, there seemed to be many
potential causes for scsiport.sys errors, but could not
find one that exactly matched this criteria.
Followup: MachineOwner
>--Original Message--
>The memory ran low first - you can monitor memory on the
>server with System Monitor.
>In terms of the reboot and dump, you can use the Windows
>Debugging tools to analyzer the memory dump file to
>determine was caused the server to crash. You can get more
>information and download the debugging tools from:
>http://www.microsoft.com/whdc/devtools/debugging/default.m
spx
>-Sue
>On Tue, 28 Sep 2004 11:09:31 -0700, "Chris"
><anonymous@.discussions.microsoft.com> wrote:
>>I have a Windows 2000 SP4 server running SQL Server 2000
>>Enterprise Edition that continually gets an event 6008
>>(the previous shutdown was unexpected). I also get the
>>following bugcheck and memory error. Does anyone know
>>what these errors are and how to correct them? Thanks.
>>Event Type: Information
>>Event Source: Save Dump
>>Event Category: None
>>Event ID: 1001
>>Date: 9/24/2004
>>Time: 11:38:37 AM
>>User: N/A
>>Computer: UHDSSAPPSERV
>>Description:
>>The computer has rebooted from a bugcheck. The bugcheck
>>was: 0x000000d1 (0x8d0ee101, 0x00000002, 0x00000000,
>>0x8d0ee101). Microsoft Windows 2000 [v15.2195]. A dump
was
>>saved in: C:\WINNT\MEMORY.DMP.
>>Event Type: Information
>>Event Source: Application Popup
>>Event Category: None
>>Event ID: 26
>>Date: 9/24/2004
>>Time: 11:23:47 AM
>>User: N/A
>>Computer: UHDSSAPPSERV
>>Description:
>>Application popup: Windows - Virtual Memory Minimum Too
>>Low : Your system is low on virtual memory. Windows is
>>increasing the size of your virtual memory paging file.
>>During this process, memory requests for some
applications
>>may be denied. For more information, see Help.
>.
>