Database standby configuration using Intel and Risk processors

Hi
We are planning to configure a standby database, but we want to use a DELL 2950 server with processors Intel. Our primary database version is Oracle RAC 10gR2 10.2.0.3 64 bits (the standby server has the same oracle version) with two nodes using IBM P550 boxes with processors P6 (RISK) server. Both databases (primary and standby databases) have Linux Red Hat 4 – 64 Bits. But I don’t know if is possible to make this configuration, could you tell me about it.
Thanks

Thanks a lot for your help.
I’ll start with the configuration. Our client decided to use that server (Intel proccesor) as standby server, he knows the possible performance degradation

Similar Messages

IDS Signature configuration - Using masks and Flags

Hi all,
It is not clear to me on how to use "mask" and "flags" while editing a signature on IDM. In the wizad, I have the option to select the TCP flags to either fire (TRUE)or NOT to fire (FALSE) the alarm or ignore (Don't Care)the flag. Can someone explain how the mask is used? My understanding about them is;
Mask tells the sensor what flags to monitor. Other flags are ignored.
TcpFlag tells the sensor to fire the alarm, if that particular flag is set.
Say for example; I select SYN and ACK in the mask and only SYN in the TcpFlag. This means, the signature will fire only if SYN is set in the packet. If ACK is also set in addition to SYN, then the sig will not fire. This is equal to setting the SYN to TRUE; ACK to False and all other flags to DON'T Care. Am I correct?
Thanks in advance,
Mohan

You are correct.
By setting Mask to SYN and ACK it will ignore the other flags.
By setting TcpFlag to SYN the signature will trigger if the packet has a SYN, but will not fire if it also has an ACK.
So a SYN packet will trigger it.
A SYN ACK packet will Not.
An ACK packet will Not.
A RST packet will Not.
etc..
However, be aware that a SYN with a combination of any other flag besides ACK WILL trigger it.
So a SYN RST will trigger it.
A SYN FIN will trigger it.
A SYN RST FIN PSH will trigger it.
etc...
This is because the signature will only look to ensure the SYN is present and the ACK is not present.
So the signature will trigger on a traditional SYN to open a connection, but will also trigger on these other weird combinations that are not part of a normal TCP connection.
So if you want to limit it to firing only on real SYN packets, then go ahead and list all the flags in the Mask and only SYN in the TcpFlags. This will ensure the signature triggers on only packets with the single SYN flag.

Using Forms and Form Processors

I am an Adjunct, teaching "Doing Business on the Internet" Thought I'd give an exam using a form since the server I use Ipage has a form processor capability.
the test can be seen at http://www.grampslist.biz/Prof/ole2.html. When the form is filled out and submitted, answers are all over the place and any HTML that is entered does not show up. Can anyone help, Thanks.
Joepd

Thank you, yes I tried )) and ok but really not as literal as < >. The
work around I used was to require all HTML answers to be preceded by . Its still a mess. Too bad..
Joe
In a message dated 4/12/2011 4:24:56 P.M. Eastern Daylight Time,
[email protected] writes:
html code can be used to hack a database, so the form is cleaning out the
tags. It is possible to submit html tags to the database by converting the
tags to entity equivalents, but you may not be able to do that using a form
builder as you are.

Hp 15-r033tx laptop does not show the Nvidia chipset information and only uses Intel HD graphics

My Hp 15 r033tx laptop has windows 8 64 bit installed in it and as it comes with NVidia Ge Force 820 M 2GB graphics card , I have also installed Nvidia and Intel HD Graphic Drivers but in the dxdiag selection it does not list the Nvidia Chipset and information but only lists Intel HD Graphics with 1786 MB.
Also it does not show any Dedicated Video Ram that is normally showing in my other friends desktop with Nvidia Graphics properly installed
Any solutions?

Hi @Suraj2410 ,
Thank you for your inquiry, I will do my best to help.
I see that you have Windows 8 installed and are not seeing your switchable graphics.
When I checked the specification page I see it came with Free Dos. When I checked for support drivers they are listed for Windows 7 and Windows 8.1.
HP 15-r033tx Notebook PC specifications
HP 15-r033tx Notebook PC Drivers
Here are three document to assist you with overcoming this difficulty.
Resolving Video and Graphics Issues
Overview of Switchable Graphics or Dual GPUs
Switchable Graphics on Notebooks Configured with Intel and ATI GPUs
If you are still having difficulties, with it being a recent purchase, I suggest contacting HP support for assistance.
Please call our technical support at 800-474-6836. If you live outside of the US/Canada Region, please click the link below to get the support number for your region. Phone Assist Worldwide
Sparkles1
I work on behalf of HP
Please click “Accept as Solution ” if you feel my post solved your issue, it will help others find the solution.
Click the “Kudos, Thumbs Up" on the bottom right to say “Thanks” for helping!

Shortcuts for Batch and Image Processor in Bridge CS6

I use Batch and Image Processor all the time, and I'd like to use a shortcut.
Can you tell me if there is a shortcut or how I can program one?
I set up shortcuts for those two commands in Photoshop, but they don't work in Bridge.
I remember from the time I started with Photoshop and had Deke McClelland's book with his set of shortcuts. There was a shortcut that worked with image processor, but it was just a set you did install and no explanation. When I moved to a different computer and a newer version of Photoshop, these keys got lost.
Is there any way to automate Batch and Image Processor?

There is no way to economically batch process in Bridge without having to go thorough sub-menus.
I'm sorry you can't get it to work, but on my system it works flawless.
Testing a bit more it seems you don't need to use a unique shortcut at all. I also tried to use the shortcut for Batch I created in PS itself to get the Batch window to front for running actions on open files. For me that is [control + Cmd + B] but feel free to find an other one.
When I discovered you don't need the unique shortcut at all I used the same shortcut for Bridge CC. . Also created [Control + Cmd + i] for the Image processor.
Both started without problems.
To extend I also created both same shortcuts for Bridge CS6. This also was working correctly, off course, having only PS CC open using the shortcut in Bridge CS6 it auto started PS CS6.
So can you specify a bit more about what OS you are using on what computer (I have OSX 10.8.4 on a MacPro 2012)
Some screenshots to show the shortcuts in System prefs and how the show in the Bridge Submenus:

9i to 11g migration using export and import

Hi,
I got a requirement to migrate 9i database to 11g using export and import.
Please let me know what are all the parameters required in 11g, so that database will run with better performance.
thanks,

You can start with the current parameters, except for COMPATIBLE (which must be 10.0.0 or higher in the 11g environment). However, you will have to remove parameters deprecated in 11g.
See http://download.oracle.com/docs/cd/E11882_01/server.112/e17222/changes.htm#BABHACIE
Then you can test performance and identify what you need to change.
Hemant K Chitale

Using Coherence and Oracle Database as the CacheStore

We are working on implementing a solution using Coherence and Oracle Database as the CacheStore. We initially implemented the Cache as a distributed-scheme which in turn uses the backing-map-scheme. We are trying to introduce transaction management and I used a scheme-ref in a transactional-scheme to point to an already existing distributed-scheme. However when I bring up the server, my custom coherence-cache-config.xml file is not recognized and Coherence comes up with the default setting. Given below is the snippet of my configuration file.
1)     I would like to understand why the below configuration doesn’t work and am I doing it the right way? If not, what is the correct way of doing it?
2)     There are a multiple transaction management options given in the documentation. Which are the ones that will work with a distributed-scheme and read-write-backing-map-scheme?
3)     If transactional-schemes cannot work with distributed-scheme, what is the best way to have a distributed cache with a oracle database as a cache store?
<caching-scheme-mapping>
<cache-mapping>
<cache-name>id<cache-name>
<scheme-name>example-transactional<scheme-name>
</cache-mapping>
</caching-scheme-mapping>
<caching-schemes>
<transactional-scheme>
<scheme-name>example-transactional</scheme-name>
<scheme-ref>distributedcustomcache</scheme-ref>
<thread-count>10</thread-count>
</transactional-scheme>
<distributed-scheme>
<scheme-name>distributedcustomcache</scheme-name>
<service-name>DistributedCache</service-name>
<backing-map-scheme>
<read-write-backing-map-scheme>
<internal-cache-scheme>
<local-scheme>

<scheme-name>inMemory</scheme-name>
</local-scheme>
</internal-cache-scheme>
<cachestore-scheme>
<class-scheme>
<class-name>spring-bean:coherenceCacheStore</class-name>
<init-params>
<init-param>
<param-name>setEntityName</param-name>
<param-value>{cache-name}</param-value>
</init-param>
</init-params>
</class-scheme>
</cachestore-scheme>

</read-write-backing-map-scheme>
</backing-map-scheme>
<autostart>true</autostart>
</distributed-scheme>

Hi,
If you look at the documentation for transactional-scheme here: http://docs.oracle.com/cd/E24290_01/coh.371/e22837/appendix_cacheconfig.htm#BHCIABHA
you will see that it says The transactional-scheme element defines a transactional cache, which is a specialized distributed cache. That means that a transactional-scheme is already a distributed-scheme.
You will see from the same documentation above that there is no way in a transactional-scheme to configure things like cache-stores or listeners or even the backing-map-scheme as these are not supported on a transactional-scheme - so you cannot use a cache store.
Personally I would not use transactional-scheme unless you have some really big reason to do so - the restrictions far outweigh any perceived advantage of having a transaction. There are better ways to build applications so they do not require transactions, that is what we have been doing for years with Coherence so far, and there is no real reason to change that.
JK

I have moved from a G5 Powermac to an Intel Mac Pro and am porting over Items from a Backup HDD. How can I access and use drawings and documents created on the PC computer on the Intel computer ?

I have moved from a G5 Powermac to an Intel Mac Pro and selectively porting over items from a backup hard drive.
How can I access and use documents and drawings created on the PC based computer ?

Clarisworks, you need Appleworks, which will only work with Mac OS X10.6.8 or earlier. See this tip if you must go newer. Mac Pros with newer hardware configuration than July 20, 2011 can't use Mac OS X 10.6.8 or earlier without this tip and then it would be Mac OS X Server. I'm not sure if the new black Mac Pro supports that configuration or not.
iPhoto, there is an iPhoto for all versions of Mac OS X.
iTunes, there is an iTunes for all versions of Mac OS X. Note with iTunes versions 11 and later, which are needed for syncing with iOS 7 or or later, you will lose coverflow, if you liked that feature. Sadly you can't run an older version of iTunes from within Mac OS X 10.9 or later.
Sketchup: http://help.sketchup.com/en/article/60107 shows the versions that will work with intermediate Mac OS X versions, and this shows the latest version: http://help.sketchup.com/en/article/36208 be sure to click on the operating system you choose to use.
GIF - Viewing GIFs Apple's Preview can do that. Editing them, I like http://www.lemkesoft.com/ Graphicconverter.
DMG is able to be opened by all versions of Mac OS X. This are just "disk images" which store programs on a virtual disk that will open when double clicked. Frequently you'll find the installer of the said program inside. To find out if the program itself is compatible with 10.7 through 10.9, see http://www.roaringapps.com/
Otherwise see the resources on:
https://discussions.apple.com/docs/DOC-2455
If you end up deciding to stick with Snow Leopard.

Standby database not configure while keep database files in different place

Dear Friends ,
I have to successfully configured "PHYSICAL STANDBY DATABASE" within the TWO databases ("PRIM" and "STAN" Database) when I kept datafile, controlfile and redolog files in the same location (like, "/u01/app/oracle/oradata/prim" location .
In this successful configuration , I have to add the below two lines into the initprim.ora and initstan.ora both server respectively ...
initprim.ora:
========
DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/stan','/u01/app/oracle/oradata/prim'
LOG_FILE_NAME_CONVERT='/u01/app/oracle/flash_recovery_area/stan','/u01/app/oracle/flash_recovery_area/prim'
initstan.ora:
========
DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/prim','/u01/app/oracle/oradata/stan'
LOG_FILE_NAME_CONVERT='/u01/app/oracle/flash_recovery_area/prim','/u01/app/oracle/flash_recovery_area/stan'Now , in second scenario , I have to change Primary database server's datafile, controlfile and redolog file in the below folder :
controlfile --> "/u01/app/oracle/oradata/prim/ctrlfile"
redologfile --> "/u01/app/oracle/oradata/prim/redofile"
datafile --> "/u01/app/oracle/oradata/prim/datafile"
Similarly I have to create same folder in my STAN database server accordingly . and also add the above lines in same way :
initprim.ora:
========
DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/stan','/u01/app/oracle/oradata/prim'
LOG_FILE_NAME_CONVERT='/u01/app/oracle/flash_recovery_area/stan','/u01/app/oracle/flash_recovery_area/prim'
initstan.ora:
========
DB_FILE_NAME_CONVERT='/u01/app/oracle/oradata/prim','/u01/app/oracle/oradata/stan'
LOG_FILE_NAME_CONVERT='/u01/app/oracle/flash_recovery_area/prim','/u01/app/oracle/flash_recovery_area/stan'Keeping the above situation when I run the below command in STAN database server :
[oracle@test ~]$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Nov 15 23:15:43 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> conn / as sysdba
Connected to an idle instance.
SQL> startup mount
ORACLE instance started.
Total System Global Area 599785472 bytes
Fixed Size 1220772 bytes
Variable Size 163581788 bytes
Database Buffers 427819008 bytes
Redo Buffers 7163904 bytes
Database mounted.
SQL> alter database recover managed standby database disconnect from session;
Database altered.
The Command execute successfully but in the alert log of the STAN database server ,I get the below error :
Completed: alter database recover managed standby database disconnect from session
Mon Nov 15 22:46:52 2010
Clearing online redo logfile 1 complete
Mon Nov 15 22:46:52 2010
Errors in file /u01/app/oracle/admin/stan/bdump/stan_mrp0_3695.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/prim/redofile/redo02.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3
Mon Nov 15 22:46:52 2010
Errors in file /u01/app/oracle/admin/stan/bdump/stan_mrp0_3695.trc:
ORA-00313: open failed for members of log group 2 of thread 1
ORA-00312: online log 2 thread 1: '/u01/app/oracle/oradata/prim/redofile/redo02.log'
ORA-27037: unable to obtain file status
Linux Error: 2: No such file or directory
Additional information: 3But I already created the above mention folder "'/u01/app/oracle/oradata/prim/redofile" successfully and the redo log files are also created there successfully , but I cannot understand why this error is showed ? And also no archivelogs are shifted from PRIM database server to STAN database server .
Would u plz suggest me , why I cannot configure Physical Standby Database when I keep my database fles in the separate location ?
help me plz ... ...

Hi,
I'm missing the steps you took renaming/moving the files on the primary.
Since the location of datafiles is stored in the control file the controlfile of the standby might not know the new location yet.
I suggest you read this http://www.cs.bris.ac.uk/maintain/OracleDocs/server.816/a76995/standby.htm#23603 and see if that helps
Success,
FJFranken

Used MAILBFR and now my database is gone!!

OK, I've been having trouble with one of the mail accounts on the server today so I followed the guidance around here and ran mailbfr. I did a backup first, then a -f, and th databases of all users disappeared. Don't panic, I thought, I have a backup. I've run a -r and is appears to run but the Inboxes are still empty. The directory that mailbfr created is about the right size for four users, 90MB, but it does not appear to have restored.
There's nothing obviously wrong in the terminal output.
Any advice gratefully received, I am currently calm...
Gordon.

I was wrong to say that the
/private/var/spool/imap/user folder was empty, I just
couldn't see the folders using Snax
What is Snax?
You should be using the terminal and have root access. Using anything else (even the finder) can make matters only worse. And since you did use Snax (whatever that may be), I advise you use diskutil to chek permission on your server.
The account folders are there
(and full of files) but as stated if you run mailbfr
-f they disappear as far as the mail client is
concerned.
As I said before mailbfr did definitely not touch them. And there is no reason why it should.
Did you check with a different client or Wenmail. You probably have a client and not a server issue and risk "blowing" up your server for nothing
Copying over the folders must just be
having the effect of replacing an index file,
Of course.
presumably corrupt in the case of my account.
Doubt it at this point, because mailbfr would have sorted the corruption.
As stated above, try setting up a different client.
It may be significant that the accounts do not appear
in the Maintenance/Accounts window of Server Admin
which does suggest that something is 'not quite
right' with the system.
It's not significant. SA only shows accounts that got their quota file set. As I mentioned before you can safely ignore SA.
I don't recall messing round
with the settings, though.
You don't recall or you are sure you didn't?

Can SSD which is configured for intel rapid start be used to store data files as a normal drive

Can SSD which is configured for intel rapid start(No Smart Response) be used to store data files as a normal drive
Lenovo ideapad u310 with 24 GB SSD Partition , only 4GB has been configured as Hibernate partition for Intel rapid start, rest of the 18.36 GB has been labelled as Healthy(Primary partition).Can this 18.36 GB of SSD be configured to store data files on it without affecting Intel rapid start.

I think I have discovered the answer to my own question!
I have disabled Adobe Reader plug-in, and can now see PDFs in Chrome.
(Steps: Chrome Menu, Settings option, Click Advanced Settings link, then Content Settings button, then select Disable Individual Plug-Ins, and a list of plug-ins is offered to enable or disable).
I then get a different result depending on whether or not Chrome PDF viewer is enabled - with it enabled I see the PDF document in Chrome, or with it disabled then the option is offered to download it, but either way I can get it it via Chrome without having to run Internet explorer in another browser window.

Using "log_file_name_convert" and "db_file_name_convert" in asm for standby

Hi ,
Oracle 11R2 enterprise edition asm
We have cbsprod primary database on server and planning to create standby database .
I want to use "log_file_name_convert" and "db_file_name_convert" .
Plz let me know how the above parameters will be utilized by considering following info
Details on PRIMARY :
GROUP# STATUS MEMBER
1 +DATA1/cbsprod/onlinelog/group_1.262.813692221
1 +DATA1/cbsprod/onlinelog/group_1.263.813692221
2 +DATA1/cbsprod/onlinelog/group_2.264.813692221
2 +DATA1/cbsprod/onlinelog/group_2.265.813692221
3 +DATA1/cbsprod/onlinelog/group_3.266.813692221
3 +DATA1/cbsprod/onlinelog/group_3.267.813692221
4 +REDOCONTROL01/cbsprod/onlinelog/group_4.256.813773233
4 +REDOCONTROL02/cbsprod/onlinelog/group_4.256.813773235
5 +REDOCONTROL03/cbsprod/onlinelog/group_5.256.813773335
5 +REDOCONTROL01/cbsprod/onlinelog/group_5.257.813773335
6 +REDOCONTROL02/cbsprod/onlinelog/group_6.257.813773375
6 +REDOCONTROL03/cbsprod/onlinelog/group_6.257.813773375
7 +REDOCONTROL01/cbsprod/onlinelog/group_7.258.813773443
7 +REDOCONTROL02/cbsprod/onlinelog/group_7.258.813773443
8 +REDOCONTROL03/cbsprod/onlinelog/group_8.258.813773461
8 +REDOCONTROL01/cbsprod/onlinelog/group_8.259.813773461
9 +REDOCONTROL01/cbsprod/onlinelog/group_9.260.813773465
9 +REDOCONTROL02/cbsprod/onlinelog/group_9.259.813773465
Details on Standby database :
SQL> select GROUP#,STATUS,MEMBER from v$logfile order by GROUP#;
GROUP# STATUS MEMBER
1 +DATA1/cbsdr/onlinelog/group_1.262.813692221
1 +DATA1/cbsdr/onlinelog/group_1.263.813692221
2 +DATA1/cbsdr/onlinelog/group_2.264.813692221
2 +DATA1/cbsdr/onlinelog/group_2.265.813692221
3 +DATA1/cbsdr/onlinelog/group_3.266.813692221
3 +DATA1/cbsdr/onlinelog/group_3.267.813692221
4 +REDOCONTROL01/cbsdr/onlinelog/group_4.256.813773233
4 +REDOCONTROL02/cbsdr/onlinelog/group_4.256.813773235
5 +REDOCONTROL03/cbsdr/onlinelog/group_5.256.813773335
5 +REDOCONTROL01/cbsdr/onlinelog/group_5.257.813773335
6 +REDOCONTROL02/cbsdr/onlinelog/group_6.257.813773375
6 +REDOCONTROL03/cbsdr/onlinelog/group_6.257.813773375
7 +REDOCONTROL01/cbsdr/onlinelog/group_7.258.813773443
7 +REDOCONTROL02/cbsdr/onlinelog/group_7.258.813773443
8 +REDOCONTROL03/cbsdr/onlinelog/group_8.258.813773461
8 +REDOCONTROL01/cbsdr/onlinelog/group_8.259.813773461
9 +REDOCONTROL01/cbsdr/onlinelog/group_9.260.813773465
9 +REDOCONTROL02/cbsdr/onlinelog/group_9.259.813773465
18 rows selected.
The same situation for datafiles :
Datafiles on primary resides on +DATA1/cbsprod/datafiles/
+DATA2/cbsprod/datafiles/
+DATA3/cbsprod/datafiles/
+DATA4/cbsprod/datafiles/
+DATA5/cbsprod/datafiles/
+DATA6/cbsprod/datafiles/
+DATA7/cbsprod/datafiles/
+DATA8/cbsprod/datafiles/
+DATA9/cbsprod/datafiles/
Datafiles on standby resides on +DATA1/cbsdr/datafiles/
+DATA2/cbsdr/datafiles/
+DATA3/cbsdr/datafiles/
+DATA4/cbsdr/datafiles/
+DATA5/cbsdr/datafiles/
+DATA6/cbsdr/datafiles/
+DATA7/cbsdr/datafiles/
+DATA8/cbsdr/datafiles/
+DATA9/cbsdr/datafiles/

Enter below parameters in INIT<SID>.ORA file.
*.log_file_name_convert='<path of logfile in PR>','<path of logfile in DR>'
*.db_file_name_convert='<path of dbfile in PR>','<path of dbfile in DR>'
If there are multiple log and db destinations:
*.log_file_name_convert='<1st path of logfile in PR>','<1st path of logfile in DR>','<2nd path of logfile in PR>','<2nd path of logfile in DR>',...
*.db_file_name_convert='<1st path of dbfile in PR>','<2nd path of dbfile in DR>','<1st path of dbfile in PR>','<2nd path of dbfile in DR>',...
In your case:
*.log_file_name_convert='+DATA1/cbsprod/onlinelog/','+DATA1/cbsdr/onlinelog/','+REDOCONTROL01/cbsprod/onlinelog/','+REDOCONTROL01/cbsdr/onlinelog/','+REDOCONTROL02/cbsprod/onlinelog/','+REDOCONTROL02/cbsdr/onlinelog/',' REDOCONTROL03/cbsprod/onlinelog/','REDOCONTROL03/cbsdr/onlinelog/'
*.db_file_name_convert='+DATA2/cbsprod/datafiles/','+DATA2/cbsdr/datafiles/','+DATA3/cbsprod/datafiles/','+DATA3/cbsdr/datafiles/','+DATA4/cbsprod/datafiles/','+DATA4/cbsdr/datafiles/','+DATA5/cbsprod/datafiles/','+DATA5/cbsdr/datafiles/','+DATA6/cbsprod/datafiles/','+DATA6/cbsdr/datafiles/','+DATA7/cbsprod/datafiles/','+DATA7/cbsdr/datafiles/','+DATA8/cbsprod/datafiles/','+DATA8/cbsdr/datafiles/','+DATA9/cbsprod/datafiles/','+DATA9/cbsdr/datafiles/'
Note: Put "/" at the end of path.
Edited by: 1009303 on Jun 2, 2013 12:47 AM

SSIS 2008 package conversion to SSIS 2012 using SQL Data Tools generating warning There was a mismatch between the processor architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWra

I am seeing the following warning is a SSIS C# script and receive a SSIS abort when I attempt to run the package.
The SSIS log indicates the package is failing at about this same step in the process.
I have also included the file SSQLDUMPER_ERRORLOG.log that SSIS generates when it aborts below.
My SSIS package has been set to 64-bit and I only have 64-bit SQL Server 2012 installed on the box.
I migrated the package using the latest version of Data Tools that came out around mid July 2014.
I edited all connection manager strings to point to 64-bit SQL Server and I run using the following command
I edited the run string to point to the new 64 bit DTExec and attempted to run.
C:\Program Files\Microsoft SQL Server\110\DTS\Binn\DTExec.exe" /Rep V /F PkgMigration.dtsx .........................
A significant amount of work does occur as reflected by the log steps prior to DTEXEC aborting but the log does just quit in mid sentence so not sure if it might have actually got a bit further.
Any help on understanding what is happening here would be most appreciated.
Warning               1              There was a mismatch between the processor
architecture of the project being built "MSIL" and the processor architecture of the reference "Microsoft.SqlServer.DTSRuntimeWrap, Version=11.0.0.0, Culture=Neutral, PublicKeyToken=89845dcd8080cc91", "x86". This mismatch may
cause runtime failures. Please consider changing the targeted processor architecture of your project through the Configuration Manager so as to align the processor architectures between your project and references, or take a dependency on references with a
processor architecture that matches the targeted processor architecture of your project.                C:\Windows\Microsoft.NET\Framework\v4.0.30319\Microsoft.Common.targets
1605       5                sc_5756696d96034309a51afe69fed2eb44
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 6100
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00A8B770
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 6100
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00A8B770
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0007.mdmp
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(1CBC:1808) 08/14/14 10:36:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(1CBC:1808) 08/14/14 10:36:47, ACTION,                DTExec.exe, Watson Invoke: No
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 1: 10124
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 2: 0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 3: 0:0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 4: 0012B770
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 10124
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0012B770
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0008.mdmp
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(2724:2488) 08/14/14 10:43:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(2724:2488) 08/14/14 10:43:09, ACTION,                DTExec.exe, Watson Invoke: No
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 1: 8716
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 2: 0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 3: 0:0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 4: 0072B770
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8716
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0072B770
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0009.mdmp
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(2240:89C) 08/14/14 10:51:56, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(2240:89C) 08/14/14 10:51:56, ACTION,                DTExec.exe, Watson Invoke: No
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 1: 8856
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 2: 0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 3: 0:0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,        Parameter 4: 009AB770
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8856
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x009AB770
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0010.mdmp
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(7B8:1E68) 08/14/14 11:01:36, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(7B8:1E68) 08/14/14 11:01:36, ACTION,                DTExec.exe, Watson Invoke: No
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 1292
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00BFB770
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 1292
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00BFB770
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0011.mdmp
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(229C:1CD8) 08/14/14 11:45:45, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(229C:1CD8) 08/14/14 11:45:45, ACTION,                DTExec.exe, Watson Invoke: No
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 1: 4220
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 2: 0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 3: 0:0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,      Parameter 4: 0019B770
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 4220
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x0019B770
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x00000000
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x00000000
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files (x86)\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0012.mdmp
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(2520:2624) 08/14/14 12:05:47, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files (x86)\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(2520:2624) 08/14/14 12:05:47, ACTION,                DTExec.exe, Watson Invoke: No
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 1: 8408
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 2: 0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 3: 0:0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Parameter 4: 00000000003ECC18
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Parsed parameters:
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ProcessID = 8408
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ThreadId = 0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     Flags = 0x0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     MiniDumpFlags = 0x0
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     SqlInfoPtr = 0x00000000003ECC18
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     DumpDir = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExceptionRecordPtr = 0x0000000000000000
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ContextPtr = 0x0000000000000000
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ExtraFile = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     InstanceName = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE,     ServiceName = <NULL>
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
(1B5C:20C0) 08/18/14 14:21:48, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 15 not used
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Program Files\Microsoft SQL Server\110\Shared\ErrorDumps\SQLDmpr0001.mdmp
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'dbghelp.dll' : 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\dbghelp.dll' : '6.12:2.633'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Location of module 'sqldumper.exe' : 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, File version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '2011.110:5058.0'
(1B5C:20C0) 08/18/14 14:21:50, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Product version of module 'C:\Program Files\Microsoft SQL Server\110\Shared\SQLDUMPER.EXE' : '11.0:5058.0'
(1B5C:20C0) 08/18/14 14:21:50, ACTION,                DTExec.exe, Watson Invoke: No

Hi GaryAMiller,
It seesm this is a know ssue. Please take a look at the following simialr issue at Microsoft Connect site:
MSB3270: Mismatch between the processor architecture:
https://connect.microsoft.com/VisualStudio/feedback/details/804933/msb3270-mismatch-between-the-processor-architecture-fakes-framework
If this issue still persists, I would suggest
opening a case with Microsoft Customer Support Services (CSS)(http://support.microsoft.com), so that a dedicated Support Professional can assist you in a more efficient manner.
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

My early (white plastic) 2006 imac freezes. I'm running Snow Leopard and have formatted and reinstalled the software 3 or 4 times.   Model Name:     iMac   Model Identifier:     iMac4,1   Processor Name:     Intel Core Duo   Processor Speed:     2 GHz

My early (white plastic) 2006 imac freezes. I'm running Snow Leopard and have formatted and reinstalled the software 3 or 4 times.   Model Name:          iMac
Model Identifier:          iMac4,1
Processor Name:          Intel Core Duo
Processor Speed:          2 GHz
Until I installed the SMC FanControl application my screen would "break up" into strange patterns and then would eventually freeze. Please help.

If you are trying to upgrade using a gray-faced OS X disk from another system, that won't work, as those disks are locked to the system types they are delivered with. You'll need to drop the $29 on a retail copy of Snow Leopard, which is available from the Apple online store. Note Snow Leopard requires 1GB minimum, and you may want at least 2GB for better performance.

Hello !, can i install Mac OSX Lion to my PC (not mac) i have got Intel Core2 Quad processor and Gigabyte P35-DS3 and 3GB RAM and ATI Radeon HD4850 Sapphire graphics Card ?

Hello Guys
i want to install MacOSX to my pc
i heard something about that (like OSX86 project ?)
i have got Intel Core2 Quad processor and Gigabyte P35-DS3 and 3GB RAM and ATI Radeon HD4850 Sapphire graphics Card ?
please answer .......

Teknus... Here's the issue. For starters, I understand software licensing issues may not be interpreted the same in all countries (although they are still applicable). I also understand that everyone is not familiar with what software licensing is. It is technically possible to install OS X on a PC (as you have seen on your friends computer). However, Apple has designed OS X to only work on Macs. In order to get OS X to work on a PC, it must be modified ("hacked"). As these forums are owned by Apple, we are not permitted to provide you with instructions on how to hack their OS.
Having said that, I have used OS X on PCs. It is not a pleasant experience at all. The experience is actually poor enough on a PC that I would not even use it... opting for Windows or Linux instead. You're simply sacrificing too much of the true OS X experience when you try to run it on standard PC hardware. If you want to try a different operating system, give Linux a try. There are many free versions out there and they will run on just about any PC. The forums are also very helpful. Linux is much more similar to OS X than Windows.
I understand that Macs are expensive and that you would like to use OS X on a PC. The simple fact is that using it on a PC would not be the same as using it on a Mac.

Database standby configuration using Intel and Risk processors

Similar Messages

Maybe you are looking for