Project "Installer Build Product version" vs exe version

Hi,
Can someone help me understand why the "Installer Build" in a project has a "product version", which later shows up in the Windows add/remove programs?
I must be missing something because to me it seems very strange that what they call "product version" in the installer is not automatically linked to the compiled exe version that the installer is built for?
Now I have to try and remember to manually keep these two versions synchronized, and the build 'product version' doesn't even have the same number of fields as the exe version information?!
It's strange when my program splash screen shows "V1.2.0.8" (read by the app by inspecting its own exe) but in the windows add/remove programs, it could say something totally different, such as 1.0.6...
Why is it like this?? How do other people use/handle these various version numbers? -is there a way for my app exe to find what the installed "product version" is?
---Confused...
-QFang
QFang
CLD LabVIEW 7.1 to 2013

QFang wrote:
I suppose it helps explain.. Perhaps I just need to think differently about how to name our installers.. Divorce the installer name from the (main) application name, then the difference in version numbers wouldn't be confusing.
Ideally the NI builder would be flexible enough that you could have a "Company Name" as the "installer name" and you could add/remove/maintain the whole company's product list with that same installer, similar to the NI installer.. sounds like a lot of work though.
Thanks for replying!
It does sound like a ton of work! I have to belive it is feasable with TKs like VIPM and Deploy on the market. (A few others I am less familliar with come to mind as well) Niether is exactly what you seem to want but demo that the tech is there!
Jeff

Similar Messages

Labview 8.5 installer build *.exe wrong date code

In Labview 8.5 application installer build *.exe has a date code of 7/17/2007 even though it was built today. It will not update even after deleting it. Is this a known bug? SS

Hi SS,
The Date Modified property of setup.exe shows the date the MetaInstaller was built. This was true in earlier versions of LabVIEW as well. It was reported to R&D (# 3T87DAP4) but was determined to be expected behavior. The actual date and time the installer was built can be determined by looking at the properties of \bin\dp\install.msi. Feedback is always appreciated, so please feel free to create a product suggestion if you think this should be changed.
Jennifer R.
National Instruments
Applications Engineer

How to Launch an Integration Builder under two different java versions

How to Launch an Integration Builder under two different java versions     1
1. Situation     2
2. How To Do     2
2.1 jre preparation     2
2.2 Put them into the system     2
2.3 Execute a Java Web Start under jre 1.4.x version     3
2.4 Change Java Runtime Versions     3
2.5 Launch an Integration Builder     6
1. Situation
OS: windows 2000 pro English
Java version: jdk 1.5.x was already installed. (Its not permitted to change.)
I dont have any authorization to install any software on the PC.
But I need to use an Integration Builder.
I already knew URLs of an Integration Builder (http://<hostname>:50000/rep/start/repository.jnlp).
2. How To Do
At this moment, an Integration Builder (XI 3.0) can be launch under jre 1.4.x environment (on windows).
2.1 jre preparation
I download j2re-1_4_2_10-windows-i586-p.exe from http://java.sun.com/j2se/1.4.2/download.html
I installed it on my home PC and copied all files from C:\Program Files\Java\ j2re1.4.2_10\ into my USB.
2.2 Put them into the system
I pasted j2re1.4.2_10 folder from my USB into the windows 2000 pro system.
Finally, I could list up all of javaws.exe under this system.
c:\j2re1.4.2_10\javaws\javaws.exe
c:\Program Files\Java\jdk1.5.0_05\bin\javaws.exe
c:\Program Files\Java\jdk1.5.0_05\jre\bin\javaws.exe
c:\Program Files\Java\jre1.5.0_05\bin\javaws.exe
2.3 Execute a Java Web Start under jre 1.4.x version
I executed c:\j2re1.4.2_10\javaws\javaws.exe .
2.4 Change Java Runtime Versions
Go to File-> Preferences -> Java
As you can see, it indicates 1.5 version.
Click [FIND] button.
Click [NEXT] button.
Click the j2re1.4.2_10 folder.
Click [NEXT] button.
A JRE Finder is able to find javaw.exe automatically. Or you can indicate C:\j2re1.4.2_10\bin\javaw.exe directly.
Click [NEXT] button.
Finally, there are two Java Runtime Versions. Now you need to uncheck the Enabled column of 1.5 version and check 1.4 version.
Click [OK] button.
Well, in the General tab, I selected None for Proxies.
2.5 Launch an Integration Builder
In the Location field, I typed the URL of an Integration Builder jnlp.
http://<hostname>:50000/rep/start/repository.jnlp
SAP Integration Builder comes up inside Applications area.
Select it and click [Start] button.
If you click Environment-> Integration Builder (Configuration), you can launch Integration Builder: Configuration.
[PDF file location] with screenshots
http://SDN.mobilian.org/SDN/How2LaunchIB.rar
===================Advertisement==========================
How do you search SDN?
What about [<b>SDN Search Widget</b>]?
SDN Search Widget
=========================================================

I am not getting anywhere with deploying my application or
applet.
I have set up my bc4j project. It contains all my VO info,
links, application module. (proj a)
I then have another project with DbInfo in it(has all my rowset
info), Multiple Frames, and my Applet.java file.
Actually I have an Applet.java file and a Application.java file
because I was seeing if both/either worked. Anyway they seem the
same, except for that extra window that comes up when you run the
applet.
I follow the steps in the oracle directions (from earlier post).
And all seems ok. But at ---->
[*] Select the subdirectory under myhtml where your applet's HTML
file
is located, and enter the directory path of the 'staging'
directory you
created in step 3 above, if different from the default.</li>
[*]Select the HTML files that JDeveloper created to run your
applet.</li>
[*]Select all of the Java source files in your project that make
up the
applet.</li>
I have no HTML file associated with my applet, at least that I
know of.
So do I need to create one, or should it of been done
automatically.
Also, I trying to figure out what will be the best way to deploy
my project. Applet or stand alone application is what my first
choices have been so far. I have read that there is some issues
with applets being served from a different server than the
database. So a stand alone application was my front runner, but
I haven't gotten either way to work yet.

An error occurred during the installation of assembly 'Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information. HRESULT: 0x80070003.

I received the above error reinstalling SQL Server 2008. I have tried all suggestions. This error also appears when I install any version of SQL Server.
I have also installed;
Microsoft® .NET Framework Version 2.0.50727.4927
Microsoft® .NET Framework Version 4.0.31106.0
Microsoft® .NET Framework Version 3.0.6920.50
Microsoft Visual C++ 2005 Redistributable (x64) 8.0.59192
Microsoft Visual C++ 2008 ATL Update kb973924 - x86 9.0.30729.4148
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
Microsoft Visual C++ 2010 x64 Redistributable 10.0.40219
Microsoft Visual C++ 2010 x86 Redistributable 10.0.40219
Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.60610
Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.61030
Overall summary:
Final result:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Exit code (Decimal):           -2068052081
Exit facility code:            1212
Exit error code:               1935
Exit message:                  SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then
rerun SQL Server Setup.
Start time:                    2014-02-23 19:17:20
End time:                      2014-02-23 19:21:35
Requested action:              Install
Log with failure:              C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\SqlSupport_KatmaiRTM_Cpu64_1.log
Exception help link:           http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1
Machine Properties:
Machine name:                  OHPC
Machine processor count:       2
OS version:                    Windows 7
OS service pack:               Service Pack 1
OS region:                     United States
OS language:                   English (United States)
OS architecture:               x64
Process architecture:          64 Bit
OS clustered:                  No
Product features discovered:
Product              Instance             Instance ID
Feature                                  Language
Edition              Version         Clustered
Package properties:
Description:                   SQL Server Database Services 2008 R2
ProductName:                   SQL Server 2008 R2
Type:                          RTM
Version:                       10
SPLevel:                       0
Installation location:         H:\SQLServer2008R2_SP1\x64\setup\
Installation edition:          DEVELOPER
User Input Settings:
ACTION:                        Install
ADDCURRENTUSERASSQLADMIN:      False
AGTSVCACCOUNT:                 NT AUTHORITY\SYSTEM
AGTSVCPASSWORD:                *****
AGTSVCSTARTUPTYPE:             Manual
ASBACKUPDIR:                   Backup
ASCOLLATION:                   Latin1_General_CI_AS
ASCONFIGDIR:                   Config
ASDATADIR:                     Data
ASDOMAINGROUP:                 <empty>
ASLOGDIR:                      Log
ASPROVIDERMSOLAP:              1
ASSVCACCOUNT:                  <empty>
ASSVCPASSWORD:                 *****
ASSVCSTARTUPTYPE:              Automatic
ASSYSADMINACCOUNTS:            <empty>
ASTEMPDIR:                     Temp
BROWSERSVCSTARTUPTYPE:         Disabled
CONFIGURATIONFILE:             C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\ConfigurationFile.ini
CUSOURCE:
ENABLERANU:                    False
ENU:                           True
ERRORREPORTING:                False
FARMACCOUNT:                   <empty>
FARMADMINPORT:                 0
FARMPASSWORD:                  *****
FEATURES:                      SQLENGINE
FILESTREAMLEVEL:               0
FILESTREAMSHARENAME:           <empty>
FTSVCACCOUNT:                  <empty>
FTSVCPASSWORD:                 *****
HELP:                          False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS:              False
INSTALLSHAREDDIR:              C:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR:           C:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR:             <empty>
INSTANCEDIR:                   C:\Program Files\Microsoft SQL Server\
INSTANCEID:                    MSSQLSERVER
INSTANCENAME:                  MSSQLSERVER
ISSVCACCOUNT:                  NT AUTHORITY\NetworkService
ISSVCPASSWORD:                 *****
ISSVCSTARTUPTYPE:              Automatic
NPENABLED:                     0
PASSPHRASE:                    *****
PCUSOURCE:
PID:                           *****
QUIET:                         False
QUIETSIMPLE:                   False
ROLE:                          <empty>
RSINSTALLMODE:                 FilesOnlyMode
RSSVCACCOUNT:                  <empty>
RSSVCPASSWORD:                 *****
RSSVCSTARTUPTYPE:              Automatic
SAPWD:                         *****
SECURITYMODE:                  <empty>
SQLBACKUPDIR:                  <empty>
SQLCOLLATION:                  SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT:                 NT AUTHORITY\SYSTEM
SQLSVCPASSWORD:                *****
SQLSVCSTARTUPTYPE:             Automatic
SQLSYSADMINACCOUNTS:           OHPC\Robert
SQLTEMPDBDIR:                  <empty>
SQLTEMPDBLOGDIR:               <empty>
SQLUSERDBDIR:                  <empty>
SQLUSERDBLOGDIR:               <empty>
SQMREPORTING:                  True
TCPENABLED:                    0
UIMODE:                        Normal
X86:                           False
Configuration file:            C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\ConfigurationFile.ini
Detailed results:
Feature:                       Database Engine Services
Status:                        Failed: see logs for details
MSI status:                    Passed
Configuration status:          Passed
Rules with failures:
Global rules:
Scenario specific rules:
Rules report file:               C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140223_191513\SystemConfigurationCheck_Report.htm
SFC/ Scannow
2014-02-23 19:08:22, Info                  CSI    0000016f [SR] Verifying 100 (0x0000000000000064) components
2014-02-23 19:08:22, Info                  CSI    00000170 [SR] Beginning Verify and Repair transaction
2014-02-23 19:08:23, Info                  CSI    00000172 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:08:23, Info                  CSI    00000174 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:08:26, Info                  CSI    00000176 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:08:26, Info                  CSI    00000177 [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2014-02-23 19:08:26, Info                  CSI    00000179 [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"wscsvc.dll";
source file in store is also corrupted
2014-02-23 19:08:27, Info                  CSI    0000017c [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:08:27, Info                  CSI    0000017d [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-4_neutral_GDR"
2014-02-23 19:08:27, Info                  CSI    00000180 [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:30{15}]"amd64_installed";
source file in store is also corrupted
2014-02-23 19:08:27, Info                  CSI    00000182 [SR] Verify complete
2014-02-23 19:12:33, Info                  CSI    00000326 [SR] Verifying 100 (0x0000000000000064) components
2014-02-23 19:12:33, Info                  CSI    00000327 [SR] Beginning Verify and Repair transaction
2014-02-23 19:12:33, Info                  CSI    00000329 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:12:35, Info                  CSI    0000032b [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:12:35, Info                  CSI    0000032c [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-3_neutral_GDR"
2014-02-23 19:12:35, Info                  CSI    0000032f [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:26{13}]"x86_installed";
source file in store is also corrupted
2014-02-23 19:12:36, Info                  CSI    00000331 [SR] Verify complete
2014-02-23 19:13:14, Info                  CSI    0000035d [SR] Repairing 3 components
2014-02-23 19:13:14, Info                  CSI    0000035e [SR] Beginning Verify and Repair transaction
2014-02-23 19:13:14, Info                  CSI    00000360 [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:14, Info                  CSI    00000362 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:14, Info                  CSI    00000364 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:14, Info                  CSI    00000366 [SR] Cannot repair member file [l:26{13}]"x86_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_INTEL (0), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:14, Info                  CSI    00000367 [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-3_neutral_GDR"
2014-02-23 19:13:15, Info                  CSI    0000036a [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:26{13}]"x86_installed";
source file in store is also corrupted
2014-02-23 19:13:15, Info                  CSI    0000036c [SR] Cannot repair member file [l:20{10}]"wscsvc.dll" of Microsoft-Windows-SecurityCenter-Core,
Version = 6.1.7601.17514, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:15, Info                  CSI    0000036d [SR] This component was referenced by [l:242{121}]"Microsoft-Windows-Client-Features-Package~31bf3856ad364e35~amd64~~6.1.7601.17514.Microsoft-Windows-Client-Features-Update"
2014-02-23 19:13:15, Info                  CSI    0000036f [SR] Could not reproject corrupted file [ml:520{260},l:46{23}]"\??\C:\Windows\System32"\[l:20{10}]"wscsvc.dll";
source file in store is also corrupted
2014-02-23 19:13:15, Info                  CSI    00000371 [SR] Cannot repair member file [l:30{15}]"amd64_installed" of Microsoft-Windows-ServicingStack,
Version = 6.1.7601.17592, pA = PROCESSOR_ARCHITECTURE_AMD64 (9), Culture neutral, VersionScope = 1 nonSxS, PublicKeyToken = {l:8 b:31bf3856ad364e35}, Type neutral, TypeName neutral, PublicKey neutral in the store, hash mismatch
2014-02-23 19:13:15, Info                  CSI    00000372 [SR] This component was referenced by [l:154{77}]"Package_2_for_KB2533552~31bf3856ad364e35~amd64~~6.1.1.1.2533552-4_neutral_GDR"
2014-02-23 19:13:15, Info                  CSI    00000375 [SR] Could not reproject corrupted file [ml:520{260},l:94{47}]"\??\C:\Windows\Servicing\Version\6.1.7601.17592"\[l:30{15}]"amd64_installed";
source file in store is also corrupted
2014-02-23 19:13:15, Info                  CSI    00000377 [SR] Repair complete
2014-02-23 19:13:15, Info                  CSI    00000378 [SR] Committing transaction
2014-02-23 19:13:15, Info                  CSI    0000037c [SR] Verify and Repair Transaction completed. All files and registry keys listed in this transaction
have been successfully repaired

Summary:
Attempted proposed solution. Error still appears.
This is installed:
Microsoft Visual C++ 2005 ATL Update kb973923 - x86 8.0.50727.4053
Microsoft Visual C++ 2005 Redistributable               8.0.56336
Microsoft Visual C++ 2005 Redistributable (x64)         8.0.59192
Microsoft Visual C++ 2008 ATL Update kb973924 - x86 9.0.30729.4148
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.4148
Microsoft Visual C++ 2010 x64 Redistributable - 10.0.40219
Microsoft Visual C++ 2010 x86 Redistributable - 10.0.40219
Microsoft Visual C++ 2012 Redistributable (x64) - 11.0.60610
Microsoft Visual C++ 2012 Redistributable (x86) - 11.0.61030
I reinstalled:
vcredist_x64 Microsoft Visual C++ 2005 SP1 Redistributable Package (x64) .exe
vcredist_x86 Microsoft Visual C++ 2005 SP1 Redistributable Package (x86).exe
Results:
Windows Installer reconfigured the product. Product Name: Microsoft Visual C++ 2005 Redistributable (x64). Product Version: 8.0.56336. Product Language: 0. Manufacturer: Microsoft
Corporation. Reconfiguration success or error status: 0.
Windows Installer reconfigured the product. Product Name: Microsoft Visual C++ 2005 Redistributable. Product Version: 8.0.56336. Product Language: 0. Manufacturer: Microsoft Corporation.
Reconfiguration success or error status: 0.
I installed SQLServer2008R2_SP1
Same error message came up;
SqlSupport_KatmaiRTM_Cpu64_1.log
MSI (s) (64:94) [23:03:43:910]: Source for file 'pfbafgaq.dll' is uncompressed, at 'H:\SQLServer2008R2_SP1\1033_ENU_LP\x64\setup\sql2008support\PFiles\SqlServr\100\Setup\Release\x64\'.
MSI (s) (64:94) [23:03:43:926]: Executing op: SetTargetFolder(Folder=C:\Windows\winsxs\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.1833_none_8a17faaf2edd3e00\)
MSI (s) (64:94) [23:03:43:926]: Executing op: SetSourceFolder(Folder=1\Windows\winsxs\nvdlei3o.taa\)
MSI (s) (64:94) [23:03:43:926]: Executing op: RegisterSharedComponentProvider(,,File=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,Component={837BF1EB-D770-94EB-A01F-
C8B3B9A1E18E},ComponentVersion=8.0.50727.1833,ProductCode={B40EE88B-400A-4266-A17B-
E3DE64E94431},ProductVersion=10.1.2731,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
MSI (s) (64:94) [23:03:43:941]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\ATL80.dll,FileKey=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={071c9b48-7c32-4621-a0ac-
3f809523288f},ProductVersion=8.0.56336,Attributes=0,,,,CopierFlags=0,,,,,,)
MSI (s) (64:94) [23:03:43:957]: Executing op: RegisterSharedComponentProvider(,,File=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,Component={837BF1EB-D770-94EB-A01F-
C8B3B9A1E18E},ComponentVersion=8.0.50727.762,ProductCode={071c9b48-7c32-4621-a0ac-
3f809523288f},ProductVersion=8.0.56336,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
MSI (s) (64:94) [23:03:43:957]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
ww_f19a562a.cat,FileKey=ul_catalog.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={071c9b48-7c32-4621-a0ac-3f809523288f},ProductVersion=8.0.56336,Attributes=0,,,,CopierFlags=0,,,,,,)
MSI (s) (64:94) [23:03:43:957]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
ww_f19a562a.manifest,FileKey=ul_manifest.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={071c9b48-7c32-4621-a0ac-
3f809523288f},ProductVersion=8.0.56336,Attributes=0,,,,CopierFlags=0,,,,,,)
MSI (s) (64:94) [23:03:43:957]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\ATL80.dll,FileKey=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={D40172D6-CE2D-4B72-BF5F-
26A04A900B7B},ProductVersion=11.0.0,Attributes=0,,,,CopierFlags=0,,,,,,)
MSI (s) (64:94) [23:03:43:957]: Executing op: RegisterSharedComponentProvider(,,File=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,Component={837BF1EB-D770-94EB-A01F-
C8B3B9A1E18E},ComponentVersion=8.0.50727.762,ProductCode={D40172D6-CE2D-4B72-BF5F-
26A04A900B7B},ProductVersion=11.0.0,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
MSI (s) (64:94) [23:03:43:972]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
ww_f19a562a.cat,FileKey=ul_catalog.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={D40172D6-CE2D-4B72-BF5F-26A04A900B7B},ProductVersion=11.0.0,Attributes=0,,,,CopierFlags=0,,,,,,)
MSI (s) (64:94) [23:03:43:972]: Executing op: CacheRTMFile(SourceFilePath=C:\Windows\WinSxS
\amd64_microsoft.vc80.atl_1fc8b3b9a1e18e3b_8.0.50727.762_none_ca3f79d486b08636\amd64_Microsoft.VC80.ATL_1fc8b3b9a1e18e3b_8.0.50727.1833_x-
ww_f19a562a.manifest,FileKey=ul_manifest.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,,ProductCode={D40172D6-CE2D-4B72-BF5F-
26A04A900B7B},ProductVersion=11.0.0,Attributes=0,,,,CopierFlags=0,,,,,,)
MSI (s) (64:94) [23:03:43:972]: Executing op: AssemblyCopy(SourceName=uvdlei3o.taa|
ATL80.dll,SourceCabKey=ul_ATL80.dll.837BF1EB_D770_94EB_FF1F_C8B3B9A1E18E,DestName=ATL80.dll,Attributes=0,FileSize=113152,PerTick=65536,,VerifyMedia=1,ElevateFlags=4,,,,ComponentId=
{837BF1EB-D770-94EB-A01F-C8B3B9A1E18E},,,,AssemblyMode=0,)
MSI (s) (64:94) [23:03:43:972]: Assembly Error:The system cannot find the path specified.
MSI (s) (64:94) [23:03:43:972]: Note: 1: 1935 2: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E} 3: 0x80070003 4: IAssemblyCache 5: CreateAssemblyCacheItem 6:
Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"
MSI (s) (64:94) [23:03:43:972]: Assembly Error (sxs): Please look into Component Based Servicing Log located at -169675656ndir\logs\cbs\cbs.log to get more diagnostic information.
MSI (s) (64:94) [23:03:49:882]: Product: Microsoft SQL Server 2008 Setup Support Files -- Error 1935. An error occurred during the installation of assembly
'Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information.
HRESULT: 0x80070003. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, component: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}
Error 1935. An error occurred during the installation of assembly
'Microsoft.VC80.ATL,version="8.0.50727.1833",publicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="amd64",type="win32"'. Please refer to Help and Support for more information.
HRESULT: 0x80070003. assembly interface: IAssemblyCache, function: CreateAssemblyCacheItem, component: {837BF1EB-D770-94EB-A01F-C8B3B9A1E18E}
MSI (s) (64:94) [23:03:49:882]: User policy value 'DisableRollback' is 0
Thanks, Ted U

.exe version issues HELP

I've just finished projects with a bit of animation and some
branching that I facilitated with additional buttons and
duplication. Published for the web it works perfectly. My
instructor (I am a student with a co op in elearning) has asked for
an .exe version to present, and I'm having issues with that. Some
animation is freezing ( made with FLASHCS3 but just simple things
w/little AS3),in addition, the problem that some animation slides
with buttons are proceeding on their own. The navigation I added to
my "review" slides with buttons aren't pausing the animated slides
at all. Most difficult is that the issues vary ( so I can't just
alter certain slides)The branching elements are fussy,too...
sometimes the buttons stick, sometimes the branching is ignored and
a slide plays the next duplicate slide when it shouldn't (it should
branch to a designated slide). The other format works perfectly.
HELP I need a quick fix...I have a fast computer with enough
memory, good graphics card, updated drivers, and updated adobe and
microsoft everything...running vista sp1---So I know It must be
me...How can I get this in shape to run ASAP?
regards,
susanne

> I've just finished projects with a bit of animation and
some branching
> that I
> facilitated with additional buttons and duplication.
Published for the web
> it
> works perfectly. My instructor (I am a student with a co
op in elearning)
> has
> asked for an .exe version to present, and I'm having
issues with that.
> Some
> animation is freezing ( made with FLASHCS3 but just
simple things
> w/little
> AS3),in addition, the problem that some animation slides
with buttons are
> proceeding on their own. The navigation I added to my
"review" slides with
> buttons aren't pausing the animated slides at all. Most
difficult is that
> the
> issues vary ( so I can't just alter certain slides)The
branching elements
> are
> fussy,too... sometimes the buttons stick, sometimes the
branching is
> ignored
> and a slide plays the next duplicate slide when it
shouldn't (it should
> branch
> to a designated slide). The other format works
perfectly. HELP I need a
> quick
> fix...
First thing I'd do is take out anything that uses AS3.
Captivate 3 doesn't
understand it ... and who knows, maybe that's messing
everything up for you.
Typical troubleshooting here would be to strip out anything
remotely
'exotic' and publish. If that works, keep adding things back
in until
something breaks.
The easiest way you could approach this might be to
copy/paste your current
project into a new one, one slide at a time, publishing and
testing between
slides. Once you know what bits break your published file it
will be easier
to figure out what needs to be fixed.
HTH
Steve
http://twitter.com/Stevehoward999
Adobe Community Expert: eLearning, Mobile and Devices
European eLearning Summit - EeLS
Adobe-sponsored eLearning conference.
http://www.elearningsummit.eu

The product version and database version are not compatible

The following simple program gets an exception {The product version and database version are not compatible} its very hard to proceed from here. Does anybody know what cause this?
Best Regards
Jan Isacsson
using System.Collections.ObjectModel;
using Microsoft.MasterDataServices.Deployment;
using Microsoft.MasterDataServices.Services.DataContracts;
namespace MdsDeploy
    class Program
        static void Main(string[] args)
            try
                ModelReader reader = new ModelReader();
                Collection<Identifier> models = reader.GetModels();
                foreach (Identifier modelId in models)
                    Console.WriteLine(modelId.Name);
            catch (System.Exception ex)
                Console.WriteLine("Error: " + ex.Message);
            Console.ReadKey();

Hi Jan,
For the error "The product version and database version are not compatible", as Emma said, the version number of the Service does not match the database schema version.
In your scenario, which version of database are you using? Please note that MDS update required after SQL 2012 SP1 installation, please refer to the links below to see the details.
http://byobi.com/blog/2012/11/mds-update-required-after-sql-2012-sp1-installation/
http://msdn.microsoft.com/en-IN/library/gg488708.aspx
Regards,
Charlie Liao
TechNet Community Support

Transport products and software component version

Hi,
I created a Products and its Software Component Version in System Landscape Directory of XI development.
I imported this Software Component Version into Integration Builder and developed design and configuration objects.
The scenario is completed and now I want to transport the Products and Software Component Version to XI Production.
Could someone please explain the transport procedure.

Hi Shravan,
Thanks four your instructions. I would like to have more details on the export/import procedure. Please confirm the following steps are correct:
From SLD of XI development:
1/ Edit new product and its software component version.
2/ Click on icon Export: XI generates a zip file and downloads it in c drive.
From SLD of XI Production:
1/ Select Import utility under system catalog.
2/ Browse and select the zip file
In XI production there are existing third party products, and I do not want the transport of this new product causes any problem.
Design and configuration objects will be exported/import ed after the successful transport of product and software component version transport.
Regards,
Daniel

Faulting application SAP Business One.exe, version 8.80.233.0

Daily the following event id 1000, application error is logged in on my SAP server.
Faulting application SAP Business One.exe, version 8.80.233.0, time stamp 0x4c9ba79d, faulting module ole32.dll, version 6.0.6002.18277, time stamp 0x4c28d53e, exception code 0xc0000005, fault offset 0x00047336, process id 0x6184, application start time 0x01cbe5257b807570.
My server is unexpectedly restarts, i am not sure whether it is due to this error.
Can anyone explain me why this error message is logged, and what is the exact reason for this.
SAP version = SAP 8.8 with patch level 15
SQL Server = MS SQL Server 2005
OS = Windows Server 2008 Enterprise Edition

You may check this: Re: CustomerLibrary - Error during AddOn installation
Thanks,
Gordon

Faulting application crw32.exe,version 11.0.0.895, faulting module crqe.dll

Hello,
I am modifying an existing report to inlcude a stored procedure. The existing report access several tables, link and formulate the fields. I added the new stored procedure, link it with one of existing tables included in the report, and add a new group summation using the new field returned by stored procedure. When I run the report with the new changes, the Crystal Report seems processing data for a while (as the SQL profiler shows the stored procedure was executed successfully), then it suddenly crashed. The complete error message in the event log is "Faulting application crw32.exe, version 11.0.0.895, faulting module crqe.dll, version 11.0.0.1282, fault address 0x000a4d5c".
Platform informatin:
- Crystal Report XI version 11.0.0.895
- SQL 2005
- Windows 2003 Server
Any help to narrow down the issue would be highly appreciated.
Michael

Hi Michael,
You are running the base build of crysral report XIR1 would suggest you to apply the latest service pack for crystal reports XIR1.
Servcie pack can be downloaded from here.
[https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/bobj_download/main.htm]
You can also upgrade CR XI RI to R2.
See this thread for upgradation:
[Crystal Report XI Upgrade Question;
Regards,
Shweta

Faulting application name: explorer.exe, version: 6.3.9600.17039, time stamp: 0x53156588

Hi, I'm running Windows 8.1 Pro, and having problems where explorer will crash every couple of hours.
here's the event viewer log info:
Faulting application name: explorer.exe, version: 6.3.9600.17039, time stamp: 0x53156588
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000000
Faulting process id: 0x2dfc
Faulting application start time: 0x01cf7e970bd1516c
Faulting application path: C:\windows\explorer.exe
Faulting module path: unknown
Report Id: a2e8b887-ea95-11e3-8265-0050b66098e2
Faulting package full name:
Faulting package-relative application ID:
I opened up the dump file, and i'm having a hard time making out what the issue might be. Any assistance would be appreciated. Thank you!
************* Symbol Path validation summary **************
Response Time (ms) Location
Deferred SRV*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
Symbol search path is: SRV*C:\SYMBOLS*http://msdl.microsoft.com/download/symbols
Executable search path is:
Windows 8 Version 9600 MP (4 procs) Free x64
Product: WinNt, suite: SingleUserTS
Built by: 6.3.9600.17031 (winblue_gdr.140221-1952)
Machine Name:
Debug session time: Mon Jun 2 12:15:42.000 2014 (UTC - 7:00)
System Uptime: not available
Process Uptime: 0 days 0:07:27.000
Loading unloaded module list
This dump file has an exception of interest stored in it.
The stored exception information can be accessed via .ecxr.
(2230.9d4): Access violation - code c0000005 (first/second chance not available)
ntdll!NtWaitForMultipleObjects+0xa:
00007ffc`20b2b13a c3 ret
0:054> !analyze -v
* Exception Analysis *
*** ERROR: Symbol file could not be found. Defaulted to export symbols for sppc.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for dlumd11.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ClassicStartMenuDLL.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ClassicExplorer64.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for GROOVEEX.DLL -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for msvcr90.dll -
FAULTING_IP:
+50951de2c52b
00000000`00000000 ?? ???
EXCEPTION_RECORD: ffffffffffffffff -- (.exr 0xffffffffffffffff)
ExceptionAddress: 0000000000000000
ExceptionCode: c0000005 (Access violation)
ExceptionFlags: 00000000
NumberParameters: 2
Parameter[0]: 0000000000000008
Parameter[1]: 0000000000000000
Attempt to execute non-executable address 0000000000000000
CONTEXT: 0000000000000000 -- (.cxr 0x0;r)
rax=00000000066e0000 rbx=0000000000000003 rcx=00000000066e0000
rdx=0000000000000000 rsi=0000000000000000 rdi=0000000000000003
rip=00007ffc20b2b13a rsp=000000000980d428 rbp=000000000980dee0
r8=0000000000001000 r9=0000000000000000 r10=0000000000000040
r11=0000000000000286 r12=0000000000000010 r13=000000000980d840
r14=0000000000000000 r15=0000000000000000
iopl=0 nv up ei pl zr na po nc
cs=0033 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00000246
ntdll!NtWaitForMultipleObjects+0xa:
00007ffc`20b2b13a c3 ret
PROCESS_NAME: explorer.exe
ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%08lx referenced memory at 0x%08lx. The memory could not be %s.
EXCEPTION_PARAMETER1: 0000000000000008
EXCEPTION_PARAMETER2: 0000000000000000
WRITE_ADDRESS: 0000000000000000
FOLLOWUP_IP:
propsys!PSPropertyBag_WriteInt+3c
00007ffc`19a2945c 488b4c2438 mov rcx,qword ptr [rsp+38h]
FAILED_INSTRUCTION_ADDRESS:
+3c
00000000`00000000 ?? ???
NTGLOBALFLAG: 0
APPLICATION_VERIFIER_FLAGS: 0
APP: explorer.exe
ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre
FAULTING_THREAD: 00000000000009d4
BUGCHECK_STR: APPLICATION_FAULT_SOFTWARE_NX_FAULT_NULL
PRIMARY_PROBLEM_CLASS: SOFTWARE_NX_FAULT_NULL
DEFAULT_BUCKET_ID: SOFTWARE_NX_FAULT_NULL
LAST_CONTROL_TRANSFER: from 00007ffc19a2945c to 0000000000000000
STACK_TEXT:
00000000`0980ed68 00007ffc`19a2945c : 00000000`1edc55b0 00000000`1edc55b0 00000000`00000000 00007ffc`1c581762 : 0x0
00000000`0980ed70 00007ffc`08848361 : 00000000`183c3ad0 00000000`1edc55b0 00000000`1edc55b0 00000000`00000000 : propsys!PSPropertyBag_WriteInt+0x3c
00000000`0980edc0 00007ffc`088482c4 : 00000000`00000000 00000000`00000425 00007ffc`16461240 00000000`00000425 : explorerframe!CShellBrowser::_OnFrameStateChanged+0x81
00000000`0980ee10 00007ffc`087ef021 : 00000000`00000001 00000000`00000425 00000000`00000425 00000000`00000033 : explorerframe!CShellBrowser::WndProcBS+0x8aa
00000000`0980f0b0 00007ffc`1ff62434 : 00000000`00000001 00000000`0980f360 00000000`00000000 00000002`00000030 : explorerframe!IEFrameWndProc+0x7d
00000000`0980f100 00007ffc`1ff63fe2 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : user32!UserCallWinProcCheckWow+0x140
00000000`0980f1c0 00007ffc`1ff6409d : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : user32!DispatchClientMessage+0xa2
00000000`0980f220 00007ffc`20b2c99f : 00000000`18215570 00007ffc`087ffd50 00000000`18215570 00000000`0980f310 : user32!_fnDWORD+0x2d
00000000`0980f280 00007ffc`1ff61fea : 00007ffc`1ff6341d 00000000`00000064 00000000`00000000 00000000`0980f3a0 : ntdll!KiUserCallbackDispatcherContinue
00000000`0980f308 00007ffc`1ff6341d : 00000000`00000064 00000000`00000000 00000000`0980f3a0 00007ffc`087f0dab : user32!NtUserMessageCall+0xa
00000000`0980f310 00007ffc`1ff65191 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00abecc0 : user32!SendMessageWorker+0x118
00000000`0980f3a0 00007ffc`087f736c : 00000000`183111e0 00000000`17e90f80 00000000`00020732 00000000`00000000 : user32!SendMessageW+0x105
00000000`0980f400 00007ffc`088479bb : 00000000`0000000c 00000000`183111e0 00000000`00000000 00000000`00000000 : explorerframe!CBrowserHost::ForwardMessageToBrowser+0x1c
00000000`0980f430 00007ffc`088484e1 : 00000000`17e90ef8 00000000`00020732 00000000`00000000 00000000`17e90f80 : explorerframe!CExplorerFrame::OnBrowserCreated+0xcb
00000000`0980f480 00007ffc`08847dcb : 00000000`203caba8 00000000`1edc55b0 00000000`17e90ee0 00000000`16237630 : explorerframe!CBrowserHost::OnBrowserCreated+0xb5
00000000`0980f4c0 00007ffc`08843133 : 00000000`16237630 00000000`16237630 00000000`16237630 00000000`1edc55b0 : explorerframe!CShellBrowser::AfterWindowCreated+0xc7
00000000`0980f500 00007ffc`08842f80 : 00000000`16237630 00000000`0980f730 00000000`00000003 00000000`18311140 : explorerframe!CBrowserHost::Initialize+0xef
00000000`0980f530 00007ffc`087f9bc0 : 00000000`18311140 00000000`00200000 00000000`0980f730 00000000`00000003 : explorerframe!CExplorerFrame::Initialize+0x3c
00000000`0980f560 00007ffc`087fb3b6 : 00000000`18311140 00000000`16237630 00000000`00200000 00007ffc`1e102d9d : explorerframe!BrowserThreadProc+0x50
00000000`0980f5a0 00007ffc`087fb366 : 18bc0f9b`000047ae 00000000`15ff61e0 00000000`00000000 00007ffc`1ff62f2f : explorerframe!BrowserNewThreadProc+0x3a
00000000`0980f5d0 00007ffc`087f8549 : 00000000`00002230 00000000`000009d4 00000000`0000000f 00000000`0000000b : explorerframe!CExplorerTask::InternalResumeRT+0x12
00000000`0980f600 00007ffc`1ebde4fc : 00000000`00000000 00000000`00000000 ffffffff`fffffffe 00000000`00200000 : explorerframe!CRunnableTask::Run+0xc9
00000000`0980f630 00007ffc`1ebde6df : 00000000`10605f50 00000000`10605f50 00000000`00000000 00000000`00000010 : shell32!CShellTaskThread::ThreadProc+0x284
00000000`0980f780 00007ffc`1c588023 : 00000000`00000001 00000000`00000001 00000000`00000000 00000000`00000000 : shell32!CShellTaskThread::s_ThreadProc+0x2f
00000000`0980f7b0 00007ffc`200e16ad : 00000000`0040e300 00000000`00000000 00000000`80004005 00000000`00000000 : SHCore!Microsoft::WRL::FtmBase::MarshalInterface+0x17b
00000000`0980f8d0 00007ffc`20b04629 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : kernel32!BaseThreadInitThunk+0xd
00000000`0980f900 00000000`00000000 : 00000000`00000000 00000000`00000000 00000000`00000000 00000000`00000000 : ntdll!RtlUserThreadStart+0x1d
SYMBOL_STACK_INDEX: 1
SYMBOL_NAME: propsys!PSPropertyBag_WriteInt+3c
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: propsys
IMAGE_NAME: propsys.dll
DEBUG_FLR_IMAGE_TIMESTAMP: 53511853
STACK_COMMAND: ~54s; .ecxr ; kb
FAILURE_BUCKET_ID: SOFTWARE_NX_FAULT_NULL_c0000005_propsys.dll!PSPropertyBag_WriteInt
BUCKET_ID: APPLICATION_FAULT_SOFTWARE_NX_FAULT_NULL_NULL_IP_propsys!PSPropertyBag_WriteInt+3c
ANALYSIS_SOURCE: UM
FAILURE_ID_HASH_STRING: um:software_nx_fault_null_c0000005_propsys.dll!pspropertybag_writeint
FAILURE_ID_HASH: {a6c58e48-fd4e-59a9-7e83-f1b082937554}
Followup: MachineOwner

Hi，
Please upload the dump file to a public folder such as OneDrive, then paste the download link here for further analyzing.
Have you installed any third party tool which might be related with Explorer in your system? if you have, please uninstalled it as a test.
Windows Explorer crashes are mostly caused by an incompatible Shell Extension.
You can run tool ShellExView to find the culprit, in the pane sort the entries with manufacturers. Disable all non-Microsoft *.dll files, and check the result. If the issue does not occur, one of the files can be the culprit. We could narrow down it one by
one.
For download link and user guide, please see this link (ShellExView is included in it)
http://technet.microsoft.com/en-us/magazine/2009.06.toolbox.aspx
Yolanda Zhu
TechNet Community Support

While installing latest version of iTunes error "This iTunes installer is intended for 32-bit versions of Windows. Please download and install the 64-bit iTunes installer instead" how to deal with it ?

While installing latest version of iTunes error "This iTunes installer is intended for 32-bit versions of Windows. Please download and install the 64-bit iTunes installer instead" how to deal with it ?

Doublechecking. What's the filename of the installer you've been downloading? (The 32-bit installer is called iTunesSetup.exe, and the 64-bit installer is called iTunes64Setup.exe.)

Akamai keeps downloading the Windows .exe version of Photoshop Elements 11

Hi,
I've just bought Photoshop 11 and I'm trying to install it on my iMac. However, the Akamai installer keeps downloading the .exe version for Windows. Not helpful...
Am I missing something here?
Stuart.

Hi Stuart_goble,
You might want to download from the direct download links available at : http://prodesigntools.com/photoshop-elements-11-direct-download-links-pse-premiere-pre.htm l
But make sure you follow the imporatant instructions mentioned on the page before initiating the download.

Where can i find the installation's files for photoshop element version 7

Where can I find the installation's files for Phtoshop element version 7 ?

This should help:
Download Photoshop Elements products | 9, 8, 7
Be sure to follow the instructions carefully.

Installation of Master Collection CS3 (disc version for Windows) on a laptop without optical drive

Installation of Master Collection CS3 (disc version for Windows) - is there any possibility of installing my legitimately purchased MC-CS3 on a new laptop without optical drive? Perhaps through a download link or will tranfering all Adobe files from my old to my new computer do the trick as well? Or do I necessarily have to buy an external optical drive? Thank you for answering.

No need to buy an optical drive and don't try transferring, it rarely works.
Download the installer from Download CS3 products
Install then enter your serial number to license it.

32-bit version odbcad32.exe (C:\windows\syswow64)

1.     By default on any 64 bit machine, 64-bit version of odbcad32.exe (C:\windows\system32) is used.
2.     It is also correct that one can use 32-bit version odbcad32.exe (C:\windows\syswow64) and add DB entries in System DSN .
3.     But, even following Step 2, given above, Alter audit report is failing out.
4.     It would be great help, if you let us know what additional step she used to run Alter audit report in WINDOWS 2008 R2 server.

PeopleSoft client tools such as application designer, datamover, etc run on 32 bit, where as PeopleTools is installed on 64 bit servers.
You need to add a system DNS for both 32 bits as 64 bits.
The 32-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\SysWoW64 folder.
The 64-bit version of the Odbcad32.exe file is located in the %systemdrive%\Windows\System32 folder.
This is also stated in the installation manual of PeopleTools, Appendix B Installing a database manually
Snipet from the installation manual:
Task B-2: Configuring an ODBC Data Source
Now that you have established your database name and location, you can set up an ODBC data source on the database client.
Note. With Microsoft SQL Server 2005 and above a new connectivity driver was delivered for Microsoft SQL Server databases named “Sql Native Client” or SNAC. Ensure that you use this driver during installation.
If you are running on a 64-bit machine, confirm that you are using the correct connectivity drivers. PeopleSoft PeopleTools executables are 32-bit, but can be run on a 64-bit machine. If you are running on a 64-bit
operating system you still need to utilize the 32-bit connectivity drivers for PeopleSoft PeopleTools. Use this information to verify that the ODBC Data Administrator odbcad32.exe is running from the correct
location. The ODBC Data Administrator resides in the following two locations on a 64-bit Microsoft Windows machine:
• The 32-bit version odbcad32.exe is found in C:\windows\syswow64: This is for 32-bit applications running on a 64-bit operating system. This is the correct version for PeopleSoft PeopleTools.
• The 64-bit version odbcad32.exe is found in C:\windows\system32: This is for 64-bit applications running on a 64-bit operating system.
When you run odbcad32 on a 64-bit Microsoft Windows machine (Start, Programs, Control Panel, Administrative Tools, ODBC Data Administrator), the 64-bit version of odbcad32.exe (C:\windows\system32)
is used by default. In order to run 32-bit PeopleSoft PeopleTools, be sure to include a System DSN entry for the 32-bit version odbcad32.exe (C:\windows\syswow64).

Project "Installer Build Product version" vs exe version

Similar Messages

Maybe you are looking for