No Largepages by default on x86

Hi,
is there any reason why auto_lpg_disable is set to 1 by default on Solaris 11.1 x64? This makes the kernel not use larger pages (2M and IIRC 1G for newer CPUs) for heap (and anon?!) unless you tell it explicitly (i.e. via MPSS preloading, ppgsz etc.)

Thanks for the reply. Fortunately (or not ) I'm not using a CPU with 1 GB pages…
Anyway, I've put the following lines in /etc/system
set segkmem_lpsize = 0x200000
set auto_lpg_disable = 0
to make use of 2 MB pages (kernel and user land).
PS: Some programs like squid get auto-promoted to 2 MB pages (while others need some help via ppgsz -o heap=2M -p $pid)…
[email protected]:~# pmap -s $(pgrep squid) | grep heap
083DC000 144K 4K rw--- [ heap ]
08400000 100352K 2M rw--- [ heap ]
Not as easy as transparent huge pages on Linux, but still better than 4k pages only

Similar Messages

Problem Create ANE,ArgumentError: Error #3500: The extension context does not have a method with the name

I little confuse about build ANE, I already follow all the direction, but the error always #3500 when I try to call the ANE.
I create ANE using java android.
The tools I use : Flash Builder running on Win-64 win.7. I think I must straight to the point, here what i made it first step by step;
1. I create the JAVA application first, with package senigo.extension.android then I create 3 file, Sample.java, SampleContext.java, PassTextFunction.java
Sample.Java Source Code
package senigo.extension.android;
import android.util.Log;
import com.adobe.fre.FREContext;
import com.adobe.fre.FREExtension;
public class Sample implements FREExtension {
@Override
public FREContext createContext(String arg0) {
// TODO Auto-generated method stub
Log.i("Sample", "createContext");
return new SampleContext();
@Override
public void dispose() {
// TODO Auto-generated method stub
Log.i("Sample", "Dispose");
@Override
public void initialize() {
// TODO Auto-generated method stub
Log.i("Sample", "Initialize");
SampleContext.Java Source Code
package senigo.extension.android;
import java.util.HashMap;
import java.util.Map;
import android.util.Log;
import com.adobe.fre.FREContext;
import com.adobe.fre.FREFunction;
public class SampleContext extends FREContext {
public SampleContext()
Log.i("SampleContext", "constructor");
@Override
public void dispose() {
// TODO Auto-generated method stub
Log.i("SampleContext", "dispose");
@Override
public Map<String, FREFunction> getFunctions() {
// TODO Auto-generated method stub
Log.i("SampleContext", "getFunctions");
Map<String, FREFunction> functionMap = new HashMap<String, FREFunction>();
functionMap.put("passText", new PassTextFunction());
return functionMap;
PassTextFunction.Java Source Code
package senigo.extension.android;
import com.adobe.fre.FREContext;
import com.adobe.fre.FREExtension;
import com.adobe.fre.FREFunction;
import com.adobe.fre.FREObject;
public class PassTextFunction implements FREFunction {
@Override
public FREObject call(FREContext arg0, FREObject[] arg1) {
// TODO Auto-generated method stub
FREObject result = null;
try{
result = FREObject.newObject("Hello World");
}catch(Exception e)
return result;
after all the file I create the jar file using click right on the tree view >> Export >> Jar File >> Sample.Jar (i already create jar file that just contain the src folder and after i frustrated, i create .jar file contain all the whole project folder but still didn't work out).
Ok, After that I create project Flex Library Project, That's contain the actionscript to call the native and the extension.xml, here the code.
Test.as Source Code, FYI : i already create public function and the static function the error still same #3500.
package senigo.extension.android
import flash.external.ExtensionContext;
public class test
private static var extContext:ExtensionContext = null;
public function test()
trace ("Test Constructor");
if (!extContext)
initExtension();
public static function get passText():String
trace ("Test Pass Text");
if (!extContext)
initExtension();
return extContext.call("passText") as String;
private static function initExtension():void
trace ("Vibration Constructor: Create an extension context");
extContext = ExtensionContext.createExtensionContext("senigo.extension.android", null);
extension.xml source code
FYI: in Flex when i put the Native Extension, they said must have Windows-x86 so I already create 3 ANE, that just contain Android-ARM , Contain Android-ARM and Default, Contain Android-ARM,Default and Windows-x86 but the error still same. I didn't got it where is the error.
<extension xmlns="http://ns.adobe.com/air/extension/3.1">
<id>senigo.extension.android</id>
<versionNumber>1.0.0</versionNumber>
<platforms>
<platform name="Android-ARM">
<applicationDeployment>
<nativeLibrary>Sample.jar</nativeLibrary>
<initializer>senigo.extension.android.Sample</initializer>
<finalizer>senigo.extension.android.Sample</finalizer>
</applicationDeployment>
</platform>

<platform name="default">
<applicationDeployment/>
</platform>
</platforms>
</extension>
After I create it, I copy the .swc file and extension file sample with the Sample.jar file.
I extract the .swc file, copy the library.swf to folder Android-ARM,Default,Windows-86 and I create build.bat that contain the command like this
adt -package -storetype PKCS12 -keystore senigo.p12 -storepass l10nk1ng -target ane senigo.extension.android.ane extension.xml -swc AndroidLib.swc -platform Android-ARM -C ./Android-ARM/ . -platform default -C ./default/ .
the I put the ane to Flex mobile project that I created:
I run it but got error #3500, I really confuse?? what's wrong with my code? is there something I wrong or I Miss it?
Please any one help me.. and when is already ane file can I debug it in Flex Mobile Project? I wanna looks the log.i code that i wrote but i confuse how to looking up in flash builder.
at the end, I wanna said Sorry if my english not very goods, and thanks, because wanna see my problem and thank you very much if You can gave me a solution's

Alex Rekish wrote:
Why you comment Windows-x86 in your extension.xml ?
I think that is a problem. You launch your application on Windows but ANE haven't got Windows-x86 implementation (also you don't include it while packaging). So your application use default implementation. But default implementation don't use any native code and cannot use ExtensionContext. And you got error.
If you don't need Windows-x86 native implementation than you need implement default implementation that different than Android-ARM. You don't need to use ExtensionContext in default implementation.
Thanks for you answer Alex Rekish, Sorry I didn't screen shoot all about the extension.xml. I comment it because the latest ANE that I build is contain Android-ARM and default. so I commented. but I already try it using just ANE that's just contain Android-ARM, with Android-ARM and windows-x86,and Android-ARM, and default, and Android-ARM,default,Windows-x86 the error still the same.
here the screen shoot, I embeded the ane that's i contain Windows-x86
in action script test.as I didn't change it anythings, I just play it on extension.xml to build the ane. is there any mistake over there? I interact with your answer that "If you don't need Windows-x86 native implementation than you need implement default implementation that different than Android-ARM. You don't need to use ExtensionContext in default implementation." I didn't need to user ExtensionContext? is means? in the actionscript? or in extension.xml? can you explained

Oracle.DataAccess.dll on Windows 7 64 bit

Hi,
I am migrating a .Net 3.5 windows class library from WinXP 32 bit to Win7 64 bit. I use Oracle 11g 64 bit client to connect to database.
my code works in Debug build but not in Release build. here is the error message:
"An attempt was made to load an assembly with an incorrect format:"
I did not complete uninstall by Oracle Deinstall, and re-install it.
Debug build have a waring:
"Assembly generation -- Referenced assembly 'Oracle.DataAccess.dll' targets a different processor."
Release build still the same incorrect format error.
here is more information:
under C:\Windows\assembly
Oracle.DataAccess 2.112.1.0 89b483f429c47342 AMD64
Oracle.Web 2.112.1.0 89b483f429c47342 AMD64
How should I fix it? should I download and install "64-bit Oracle Data Access Components (ODAC)"? What's difference between ODP.net in Oracle client and in ODAC?
Thank you,
Wes
Windows 7 Pro, 64 bit, Visual Studio 2010, Oracle 11g 64 bit client

What do you have /32BIT flag set to in the assembly? Ie, was it compiled with AnyCPU, x86, etc? You can use corflags.exe with the .net sdk to find out.
Prior to VS2010, the default was AnyCPU which meant it ran as 64 bit on 64 bit OS, and 32 bit on 32 bit OS.
As of VS2010, the IDE defaults to x86, which means it runs as 32 bit no matter what.
32 bit apps need 32 bit odp/client. 64 bit apps need 64 bit odp/client.
The error you're getting usually means you have the wrong bits (32/64) of the Oracle client installed.
Assuming you have the wrong client bits installed, you could either
a) make the app run as the other bits by setting/clearing the 32BIT flag (also by using corflags.exe)
b) install the other bits of Oracle client software. a 32 bit home and a 64 bit home play rather nicely together for the most part, but you need to install them into separate homes.
Hope it helps,
Greg

ORA 12154 on OCIServerAttach

Hi!
I get an ORA 12154 when calling OCIServerAttach. The OCIEnvCreateand two OCIHandleAlloc calls are OK. This setup used to work with 32bit pcs. But on 64bit pcs the troubles arise.
If we do tnsping on the the same server name, it responds. So I can't quite see that anything should be wrong with the setup so far? Why can't my program find the same connection as tnsping? If there where syntax errors in sqlnames.ora, tnsnames.ora the tnsping wouldn't work, I guess?
Suggestions on where to look are very welcome!
Best regards,
Knut

Hi,
This forum is for "Oracle Developer Tools for Visual Studio", which is an actual product for a plugin for VS.
You're probably looking for the OCI forum.. Oracle Call Interface (OCI) .
Apart from TNSPing, does SQLPLUS connect without issue? And there's only a single home on this box so we're sure it's not a multiple home issue? If you have multiple homes, you need to create tnsnames.ora for each.
What version of client are you using? There is a known issue with older versions of Oracle client where a 32 bit app on a 64 bit box would get a 12154 if the app location was in a path that contained parenthesis (c:\program files (x86)) for example. It's not a 32 bit problem per se, just that 32 bit apps usually install by default to (x86) location. If that's the issue you're running into, current versions of client don't have that problem, or just install the app to a path without parens.
Hope it helps,
Greg

Installing DEB or RPM printer drivers on ArchLinux running on Pogoplug

I've managed to get Archlinux running on my ARM6 Pogoplug. I got the timemachine server up and running, and I'm moving on to a CUPS server. I can't find any linux drivers in the Gutenprint repository, but it appears that Lexmark has Linux driver downloads for my printer: http://support.lexmark.com/index?locale … age=null#1
That's great, except a) they only have Debian or RPM based packages, and b) from the CUPS web administration, it's asking for a "PPD" file. I've tried downloading both drivers to my Pogoplug and running the install scripts, but both fail, saying:
Operating system: linux
CPU Arch: armv6l
Warning: No installer for "armv6l" found, defaulting to x86...
./startupinstaller.sh: line 29: bin/linux/x86/libc.so.6/lzma-decode: cannot execute binary file
./startupinstaller.sh: line 29: bin/linux/x86/libc.so.6/lzma-decode: cannot execute binary file
./startupinstaller.sh: line 29: bin/linux/x86/libc.so.6/lzma-decode: cannot execute binary file
./startupinstaller.sh: line 29: bin/linux/x86/libc.so.6/lzma-decode: cannot execute binary file
Error: Couldn't find any suitable frontend for your system
Does anyone have any advice? I'm just struggling along trying not to break things

https://aur.archlinux.org/packages.php?ID=35866
http://www.archlinux.org/packages/extra/any/rpmextract/
Last edited by skunktrader (2012-01-13 03:21:49)

WDS - Capture and Install

Hi All,
Hopefully this is in the right place and someone can offer some assistance for me. I will try to lay this out correctly (newbie on this forum).
Have installed WDS on Server 2012 R2. Settings altered...
Setup my server as standard, nothing special. Created boot.wim from a copy of a Dell Win 7 disk, copied locally and imported. Created capture image. Imported numerous drivers (which were installed manually and worked on the client (testing client)). Settings
changed on the WDS server (it is called ntserver29 for reference).
- PXE Response - Respond to all clients...(require administrator approval not ticked)
- AD DS - Computer Account Location - Same Domain as WDS server
- Boot - as default, require user to press f12.
- Client - Joining a Domain - Do not join...ticked.
- DHCP - Neither 'do not listen' and 'configure dhcp options' ticked. (DHCP not installed on that server)
- TFTP - block size (as default) set to 1298 (have changed the registry file from 0 to 512 as previously instructed on an online guide). Enable the TFTP server to negotiate variable window size requests is ticked.
- Network - UDP port policy is set to 'obtain dynamic ports'
- Advanced - Domain Controller - Allow WDS to dynamically discover domain servers (ticked). DHCP Authorisation - Authorize this WDS server in DHCP
- Multicast - Multicast IP set to obtain IP from DHCP. Transfer Settings set to Keey all multicase clients in a session at the same speed.
From the top. Have had issues which seem resolved, will explain further down.
* With the above set. Have built Dell desktop machine with Dell windows 7 disc flat. Installed relevant drivers, some updates and google chrome.
* Using sysprep and the capture image got as far as saving the wim. Was unable to authenticate to the server as it did not even bring up the account login box, just failed to connect (ISSUE 1).
* Chose to test WDS seperate. Copied the image to an external drive. Copied to the RemoteInstall\Images path on the WDS server. This populate the image to the server without involvement from myself. Restarted the server.
* When rebooting the desktop, device only shows Windows 7 Setup and Windows 7 Setup Capture (my 2 original boot images) and nothing else (ISSUE 2).
Bit stuck from there. WDS didnt work prior to uninstalling a specific update and re-installing a fresh WDS.
Any advice would be GREATLY appreciated. I dont lay claim to being knowledgeable about the system, just looking to learn and get this working for the business. Happy to answer questions and will keep checking in.
Many Thanks, hopefully the above makes sense to someone.
Mark

If this will help any. Obtained the details from CMD.
Unattend file present: No
Status: Enabled
Boot Images for ia64
Image count: 0
Image Information:
There are no images that match the specified criteria.
Boot Images for arm
Image count: 0
Image Information:
There are no images that match the specified criteria.
===============================================================================
Summary:
Total number of boot image stores: 4
Total number of boot images: 3
INSTALL IMAGES
===============================================================================
Image Group DistributionGroup
Name: DistributionGroup
Security: O:BAG:DUD:(A;OICI;FA;;;BA)(A;OICI;FA;;;SY)(A;;FA;;;BA)(A;OICIIO;GA;;;C
O)(A;OICI;0x1200a9;;;BU)(A;CI;LC;;;BU)(A;CI;DC;;;BU)
Image format: WIM
Image count: 6
Image Information:
Dell Optiplex 3020 Test
File name: Dell Optiplex 3020.wim
Image name: Dell Optiplex 3020 Test
Description: Dell Optiplex 3020 Test Capture
ID: <Not Assigned>
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 12172102562 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 15 October 2014 19:58:39
Last modified: 15 October 2014 19:58:46
Default language: English (United States)
Other languages:
Dependent files:
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\Dell Optiplex 30
20.wim
OS version: Microsoft® Windows® Operating System, 6.1.7601
Service pack level: 1
User filter: O:S-1-5-21-1738485378-1525038498-1803697834-16854G:DUD:(A;;FA;;;BA)
(A;;FA;;;SY)(A;;FA;;;S-1-5-21-1738485378-1525038498-1803697834-16854)(A;;0x1200a
9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
<Error>
Windows 7 HOMEBASIC
File name: install-(2).wim
Image name: Windows 7 HOMEBASIC
Description: Windows 7 HOMEBASIC
ID: {587B12B6-D6D9-4F13-8B81-E962AC7078D7}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8306998658 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:18
Default language: English (United States)
Other languages:
Dependent files:
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(2).wim
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 HOMEPREMIUM
File name: install-(3).wim
Image name: Windows 7 HOMEPREMIUM
Description: Windows 7 HOMEPREMIUM
ID: {150666C9-B2D9-4BA0-873C-3A4B7BF986C3}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8747698450 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:21
Default language: English (United States)
Other languages:
Dependent files:
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(3).wim
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 PROFESSIONAL
File name: install-(4).wim
Image name: Windows 7 PROFESSIONAL
Description: Windows 7 PROFESSIONAL
ID: {1849C3AE-E2F6-4EC5-9DBD-AD0FD2223185}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8627895833 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:22
Default language: English (United States)
Other languages:
Dependent files:
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(4).wim
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 ULTIMATE
File name: install-(5).wim
Image name: Windows 7 ULTIMATE
Description: Windows 7 ULTIMATE
ID: {280A4685-155E-4565-B413-D60BB8F105E7}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8785899727 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:24
Default language: English (United States)
Other languages:
Dependent files:
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install-(5).wim
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
Windows 7 STARTER
File name: install.wim
Image name: Windows 7 STARTER
Description: Windows 7 STARTER
ID: {1C935F5A-1835-49A3-AE1A-B64910FFF925}
Priority: 500000 (Default)
Architecture: x86
Image type: Install
Image format: WIM
Image group: DistributionGroup
Size: 8250904871 bytes
Partition style: <Unknown>
HAL type: acpiapic
Creation time: 14 July 2009 06:24:44
Last modified: 14 October 2014 16:19:16
Default language: English (United States)
Other languages:
Dependent files:
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\install.wim
     \\NTSERVER29.domain.co.uk\REMINST\Images\DistributionGroup\res.rwm
OS version: Microsoft® Windows® Operating System, 6.1.7600
Service pack level: 0
User filter: O:BAG:DUD:(A;;FA;;;BA)(A;;FA;;;SY)(A;;FA;;;BA)(A;;0x1200a9;;;BU)
Unattend file present: No
Status: Enabled
Image Filters:
===============================================================================
Total number of image filters: 0
NON-NATIVE IMAGES
===============================================================================
===============================================================================
Summary:
Total number of non-wim image groups: 0
Total number of non-wim images: 0
An error occurred while trying to execute the command.
Error Code: 0xC10408B3
Error Description: One or more errors occurred while processing the command. Rev
iew the error logs for more information.
C:\Users\administrator>

Adobe air windows/C++:Error #3500: The extension context does not have a method with the name

I created a C++ dynamic dll called by air.
If the dll depends on other dlls, then the error#3500 occured. However removed other dlls, it works.
Could that mean the air can only call one dynamic dll that doesn't depend any other dlls?
does anybody met this problem before, or let me know what can I do?

Alex Rekish wrote:
Why you comment Windows-x86 in your extension.xml ?
I think that is a problem. You launch your application on Windows but ANE haven't got Windows-x86 implementation (also you don't include it while packaging). So your application use default implementation. But default implementation don't use any native code and cannot use ExtensionContext. And you got error.
If you don't need Windows-x86 native implementation than you need implement default implementation that different than Android-ARM. You don't need to use ExtensionContext in default implementation.
Thanks for you answer Alex Rekish, Sorry I didn't screen shoot all about the extension.xml. I comment it because the latest ANE that I build is contain Android-ARM and default. so I commented. but I already try it using just ANE that's just contain Android-ARM, with Android-ARM and windows-x86,and Android-ARM, and default, and Android-ARM,default,Windows-x86 the error still the same.
here the screen shoot, I embeded the ane that's i contain Windows-x86
in action script test.as I didn't change it anythings, I just play it on extension.xml to build the ane. is there any mistake over there? I interact with your answer that "If you don't need Windows-x86 native implementation than you need implement default implementation that different than Android-ARM. You don't need to use ExtensionContext in default implementation." I didn't need to user ExtensionContext? is means? in the actionscript? or in extension.xml? can you explained

PXE-T04: Access Violation

We are running SCCM 2012 R2 Primary Site Server
We configured PXE Service Point in Microsoft System Center Configuration Manager 2012, booting new bare metal vms fail with the following errors:
PXE-T04: Access Violation
PXE-E36: Error Received from TFTP Server
PXE-M-F Exiting PXE Rom
No errors in the SMSPXE.log.
We configured IP Helper settings on routers
next-ser er "IP Address of SCCM PXE Server"
filename smsboot\x64\wdsnbp.com
Below are WDS logs
Windows Deployment Services Management Utility [Version 6.3.9600.16384]
© 2013 Microsoft Corporation. All rights reserved.
SETUP INFORMATION FOR SERVER
Server State:
     OS version: 6.3
     WDS operational mode: Native
     Standalone configuration: No
Installation State:
     RemoteInstall location: E:\RemoteInstall
     RemoteInstall share up-to-date: Yes
     Boot files installed:
         x86     - Yes
         x64     - Yes
         ia64    - No
         arm     - Yes
         x86uefi - Yes
         x64uefi - Yes
CONFIGURATION INFORMATION FOR SERVER
Server Authorization:
     Authorization state: Not Authorized
Answer Policy:
     Answer clients: No
     Answer only known clients: No
     Response delay: 0 seconds
Active Directory Use Policy:
     Preferred DC:
     Preferred GC:
     Prestage devices using MAC: No
     New computer naming policy: %61Username%#
     Domain search order: Global Catalog Only
     New computers join domain: Yes
New Computer OU:
     OU type: Server Domain
     OU: CN=Computers,DC=nb,DC=com
DHCP Configuration:
     DHCP service status: Not Installed
     DHCP option 60 configured: <Not Applicable>
PXE Bind Policy:
     Use DHCP ports: Yes
     Rogue detection: Disabled
     RPC port: 5040
Interface Bind Policy:
     Policy: Exclude Registered
     Registered interfaces:
Boot Program Policy:
     Known client PXE prompt policy: OptIn
     New client PXE prompt policy: OptIn
     Allow N12 for new clients: <Not Applicable>
     Reset boot program: Disabled
     Default boot programs:
         x86     - boot\x86\pxeboot.com
         x64     - boot\x64\pxeboot.com
         ia64    - boot\ia64\bootmgfw.efi
         arm     - boot\arm\bootmgfw.efi
         x86uefi - Boot\x86\bootmgfw.efi
         x64uefi - Boot\x64\bootmgfw.efi
     Default N12 boot programs:
         x86     - boot\x86\pxeboot.n12
         x64     - boot\x64\pxeboot.n12
         ia64    - boot\ia64\bootmgfw.efi
         arm     - boot\arm\bootmgfw.efi
         x86uefi - Boot\x86\bootmgfw.efi
         x64uefi - Boot\x64\bootmgfw.efi
Banned GUIDs list:
Boot Image Policy:
     Default image type for x64 clients: Both
     Default boot images:
         x86     -
         x64     -
         ia64    -
         arm     -
         x86uefi -
         x64uefi -
Driver Policy:
     Avoid duplicate driver packages: Yes
WDS Client Policy:
     Logging policy:
         Enabled: No
         Logging level: Info
     Unattend policy:
         Enabled: No
         Command-line precedence: No
         WDS unattend files:
             x86     -
             x64     -
             ia64    -
             arm     -
             x86uefi -
             x64uefi -
Server Automatic Refresh Policy:
     Refresh period: 900 seconds
BCD Refresh Policy:
     Enabled: No
     Refresh period: 60 minutes
Pending Device Policy:
     Policy: Disabled
     Poll interval: 10 seconds
     Max retry count: 2160 times
     Message to pending clients:
     Retention period:
         Approved devices: 30 days
         Other devices: 1 days
     Defaults for x86:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for x64:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for ia64:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for arm:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Full
         Join domain: Yes
     Defaults for x86uefi:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Join Only
         Join domain: Yes
     Defaults for x64uefi:
         Referral server:
         Boot program path:
         WDS client unattend file path:
         Boot image path:
         User: Domain Admins
         Join rights: Join Only
         Join domain: Yes
WDS PXE Providers:
     Name: SMSPXE
     Path: C:\Program Files\Microsoft Configuration Manager\bin\x64\smspxe.dll
     Order: 1
     Critical: No
     Name: WDSDCPXE
     Path: C:\Windows\system32\wdsdcpxe.dll
     Order: 2
     Critical: No
WDS Device Controllers:
     Name: WDSADDC
     CLSID: {1F05CFEA-D4E4-4049-9C76-7B4F0013ECC9}
     Priority: 32768
     Enabled: Yes
     Name: WDSSDC
     CLSID: {17FD4B68-06B7-48EB-97B7-1575A171AED9}
     Priority: 32768
     Enabled: No
WDS Transport Server Policy:
     IPv4 source: Range
         Start address: 239.192.0.2
         End address: 239.192.0.254
     IPv6 source: Range
         Start address: FF15::1:1
         End address: FF15::1:FF
     UDP Port Policy: Dynamic
         Start port: <Not Applicable>
         End port: <Not Applicable>
     Network profile: <Not Applicable>
     TFTP Properties:
         Maximum block size: 0
         Variable window extension enabled: Yes
     Multicast session policy:
         Slow client handling policy: None
         AutoDisconnect threshold: 256 KBps
         Multistream stream count: 2
         Slow client fallback: Yes
     Multicast Content Providers:
         Name: WDS
         Description: Default Content Provider
         File path: C:\Windows\system32\wdscp.dll
         Initialization routine: WdsTransportProviderInit
IMAGE INFORMATION FOR SERVER
BOOT IMAGES
===============================================================================
Boot Images for x86
Image count: 0
Image Information:
There are no images that match the specified criteria.
Boot Images for x64
Image count: 0
Image Information:
There are no images that match the specified criteria.
Boot Images for ia64
Image count: 0
Image Information:
There are no images that match the specified criteria.
Boot Images for arm
Image count: 0
Image Information:
There are no images that match the specified criteria.
===============================================================================
Summary:
Total number of boot image stores: 4
Total number of boot images: 0
INSTALL IMAGES
===============================================================================
There are no image groups that match the specified criteria.
===============================================================================
Summary:
Total number of install image groups: 0
Total number of install images: 0
NON-NATIVE IMAGES
===============================================================================
===============================================================================
Summary:
Total number of non-wim image groups: 0
Total number of non-wim images: 0
OVERALL IMAGE SUMMARY:
Total number of boot image stores: 4
Total number of boot images: 0
Total number of install image groups: 0
Total number of install images: 0
Total number of non-wim image groups: 0
Total number of non-wim images: 0
The command completed successfully.
SMSPXE:
======
<![LOG[Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll]LOG]!><time="14:43:49.110+240" date="04-28-2014" component="SMSPXE" context=""
type="1" thread="6808" file="wimfile.cpp:344">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim]LOG]!><time="14:43:49.110+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:422">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim
PackageID: PRI00002
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="14:43:49.113+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim]LOG]!><time="14:43:49.113+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:458">
<![LOG[Begin validation of Certificate [Thumbprint 8B278656F312633DA23BDEAA99A625C7933019A2] issued to '{0D51C1EC-638A-4904-938E-58C733731F10}']LOG]!><time="14:43:49.119+240" date="04-28-2014" component="SMSPXE" context=""
type="1" thread="6032" file="ccmcert.cpp:1662">
<![LOG[Completed validation of Certificate [Thumbprint 8B278656F312633DA23BDEAA99A625C7933019A2] issued to '{0D51C1EC-638A-4904-938E-58C733731F10}']LOG]!><time="14:43:49.119+240" date="04-28-2014" component="SMSPXE"
context="" type="1" thread="6032" file="ccmcert.cpp:1803">
<![LOG[PXE Provider finished loading.]LOG]!><time="14:43:49.119+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6032" file="smspxe.cpp:184">
<![LOG[InstallBootFilesForImage failed. 0x80004005]LOG]!><time="14:43:49.392+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1608">
<![LOG[Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)]LOG]!><time="14:43:49.392+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1275">
<![LOG[Failed adding image E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="14:43:49.392+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1180">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.49.03.{E7B944DA-FDBA-4579-8AC8-B91550B1EA89}.boot.bcd deleted.]LOG]!><time="14:43:49.393+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:267">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.49.03.{E7B944DA-FDBA-4579-8AC8-B91550B1EA89}.boot.bcd.log deleted.]LOG]!><time="14:43:49.393+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:282">
<![LOG[Found new image PRI00005]LOG]!><time="14:43:49.393+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:1123">
<![LOG[Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll]LOG]!><time="14:43:49.394+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="wimfile.cpp:344">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim]LOG]!><time="14:43:49.394+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:422">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim
PackageID: PRI00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="14:43:49.397+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim]LOG]!><time="14:43:49.397+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:458">
<![LOG[InstallBootFilesForImage failed. 0x80004005]LOG]!><time="14:43:49.713+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1608">
<![LOG[Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)]LOG]!><time="14:43:49.713+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1275">
<![LOG[Failed adding image E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="14:43:49.713+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1180">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.49.04.{9C5C9A39-428B-4B20-B844-3454CB63F230}.boot.bcd deleted.]LOG]!><time="14:43:49.713+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:267">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.49.04.{9C5C9A39-428B-4B20-B844-3454CB63F230}.boot.bcd.log deleted.]LOG]!><time="14:43:49.714+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:282">
<![LOG[Found new image PRI00002]LOG]!><time="14:43:50.812+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:1123">
<![LOG[Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll]LOG]!><time="14:43:50.813+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="wimfile.cpp:344">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim]LOG]!><time="14:43:50.813+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:422">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim
PackageID: PRI00002
ProductName: Microsoft® Windows® Operating System
Architecture: 0
Description: Microsoft Windows PE (x86)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="14:43:50.815+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim]LOG]!><time="14:43:50.815+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:458">
<![LOG[InstallBootFilesForImage failed. 0x80004005]LOG]!><time="14:43:51.094+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1608">
<![LOG[Warning: Failed to copy the needed boot binaries from the boot image E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim.
The operation completed successfully. (Error: 00000000; Source: Windows)]LOG]!><time="14:43:51.095+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1275">
<![LOG[Failed adding image E:\RemoteInstall\SMSImages\PRI00002\boot.PRI00002.wim. Will Retry..
Unspecified error (Error: 80004005; Source: Windows)]LOG]!><time="14:43:51.095+240" date="04-28-2014" component="SMSPXE" context="" type="3" thread="6808" file="bootimagemgr.cpp:1180">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.50.05.{2A90265D-C49E-433D-868E-7CF173CB4B93}.boot.bcd deleted.]LOG]!><time="14:43:51.095+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:267">
<![LOG[File E:\RemoteInstall\SMSTemp\2014.04.28.14.43.50.05.{2A90265D-C49E-433D-868E-7CF173CB4B93}.boot.bcd.log deleted.]LOG]!><time="14:43:51.095+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="bootimagecache.cpp:282">
<![LOG[Found new image PRI00005]LOG]!><time="14:43:51.095+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:1123">
<![LOG[Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll]LOG]!><time="14:43:51.096+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="wimfile.cpp:344">
<![LOG[Opening image file E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim]LOG]!><time="14:43:51.096+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:422">
<![LOG[Found Image file: E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim
PackageID: PRI00005
ProductName: Microsoft® Windows® Operating System
Architecture: 9
Description: Microsoft Windows PE (x64)
Version:
Creator:
SystemDir: WINDOWS
]LOG]!><time="14:43:51.099+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:925">
<![LOG[Closing image file E:\RemoteInstall\SMSImages\PRI00005\boot.PRI00005.wim]LOG]!><time="14:43:51.099+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="wimfile.cpp:458">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\wdsnbp.com' does not exist. Ignore it]LOG]!><time="14:43:51.452+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\abortpxe.com' does not exist. Ignore it]LOG]!><time="14:43:51.452+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\pxeboot.com' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\pxeboot.n12' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\bootmgr.exe' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\wdsnbp.com' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\abortpxe.com' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\PXE\wdsmgfw.efi' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\EFI\bootmgfw.efi' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\Fonts\segmono_boot.ttf' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context=""
type="2" thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\Fonts\segoe_slboot.ttf' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context=""
type="2" thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\Fonts\segoen_slboot.ttf' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context=""
type="2" thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Source file 'E:\RemoteInstall\SMSTempBootFiles\PRI00005\WINDOWS\Boot\Fonts\wgl4_boot.ttf' does not exist. Ignore it]LOG]!><time="14:43:51.453+240" date="04-28-2014" component="SMSPXE" context="" type="2"
thread="6808" file="bootimagemgr.cpp:1453">
<![LOG[Cannot read the registry value of MACIgnoreListFile (800703e5)]LOG]!><time="14:43:53.086+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="provsettings.cpp:353">
<![LOG[MAC Ignore List Filename in registry is empty]LOG]!><time="14:43:53.086+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="provsettings.cpp:468">
<![LOG[Found new image PRI00002]LOG]!><time="14:43:56.973+240" date="04-28-2014" component="SMSPXE" context="" type="1" thread="6808" file="bootimagemgr.cpp:1123">
<![LOG[Loaded C:\Program Files (x86)\Windows Kits\8.1\Assessment and Deployment Kit\Deployment Tools\amd64\DISM\wimgapi.dll]LOG]!><time="14:43:56.974+240" date="04-28-2014" component="SMSPXE" context="" type="1"
thread="6808" file="wimfile.cpp:344">

\\smsboot\x64\wdsnbp.com fixed the issue.

JRegistryKey.dll on windows 7 throwing exception

Hi all,
I am using JRegistryKey.dll with one application. This application is 32 bit application and it runs perfectly fine in Windows XP. But when i tried to run this on 64-bit environment of Windows 7 It failed to get started. Please find below log snippet. Please provide your valuable inputs for the same. I would appreciate if you can help in this problem.
Looking forward for positive reply from all you out there.
Thanks in advance,
Jits.
# An unexpected error has been detected by Java Runtime Environment:
# EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x7724311d, pid=636, tid=2576
# Java VM: Java HotSpot(TM) Client VM (11.3-b02 mixed mode windows-x86)
# Problematic frame:
# C [ntdll.dll+0x3311d]
# If you would like to submit a bug report, please visit:
# http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.
--------------- T H R E A D ---------------
Current thread (0x02d89000): JavaThread "main" [_thread_in_native, id=2576, stack(0x00090000,0x00290000)]
siginfo: ExceptionCode=0xc0000005, reading address 0x0e4c9a20
Registers:
EAX=0x0000b95b, EBX=0x0e46cf48, ECX=0x0000009b, EDX=0x000007ff
ESP=0x0028104c, EBP=0x00281074, ESI=0x0e4c9a20, EDI=0x009a0000
EIP=0x7724311d, EFLAGS=0x00010206
Top of Stack: (sp=0x0028104c)
0x0028104c: 009a0000 0e46cf48 00000000 0e46cf50
0x0028105c: 0000000a 00281040 00350034 0028115c
0x0028106c: 7728041d 04a4b981 0028116c 77243407
0x0028107c: 009a0000 0e4c9a20 0028113c 00000000
0x0028108c: 73af664d 00000000 009a0000 0e46cf50
0x0028109c: 7724609f 772460a4 73af67ed 00000000
0x002810ac: 00281180 00281208 002810a4 002810f8
0x002810bc: 00281140 009a0000 009a2878 fffffffe
Instructions: (pc=0x7724311d)
0x7724310d: 7f 4c 00 8b 45 10 8b 00 8d 34 c3 89 75 0c 74 1d
0x7724311d: 8b 06 89 45 e4 33 47 50 8a c8 32 cc 89 45 e4 32
Stack: [0x00090000,0x00290000], sp=0x0028104c, free space=1988k
Native frames: (J=compiled Java code, j=interpreted, Vv=VM code, C=native code)
C [ntdll.dll+0x3311d]
C [ntdll.dll+0x33407]
C [ntdll.dll+0x332f2]
C [msvcrt.dll+0x98cd]
C [jRegistryKey.dll+0x1b0d]
C [jRegistryKey.dll+0x258f]
j ca.beq.util.win32.registry.RegistryKey.getValue(Ljava/lang/String;)

What do you have /32BIT flag set to in the assembly? Ie, was it compiled with AnyCPU, x86, etc? You can use corflags.exe with the .net sdk to find out.
Prior to VS2010, the default was AnyCPU which meant it ran as 64 bit on 64 bit OS, and 32 bit on 32 bit OS.
As of VS2010, the IDE defaults to x86, which means it runs as 32 bit no matter what.
32 bit apps need 32 bit odp/client. 64 bit apps need 64 bit odp/client.
The error you're getting usually means you have the wrong bits (32/64) of the Oracle client installed.
Assuming you have the wrong client bits installed, you could either
a) make the app run as the other bits by setting/clearing the 32BIT flag (also by using corflags.exe)
b) install the other bits of Oracle client software. a 32 bit home and a 64 bit home play rather nicely together for the most part, but you need to install them into separate homes.
Hope it helps,
Greg

Upgraded to 64 bit Oracle DataAccess.dll and now more open cursors errors

Hi, We recently converted from .net framework 1.1 application to .net 4.0 framework for 64 bit. We installed the 64 bit version of Oracle DataAccess dll. It now seems like we are getting many more open cursor error messages in our application. The open_cursor value set in the database has not changed and other than the 64 bit Oracle and .net 4.0 framework nothing has changed. I was just curious if anyone else that has converted to the 64 bit Oracle DataAccess dll has experienced an increased number of open cursor errors? If so, what was the resolution.
I apprecieate any feedback.
Thanks

What do you have /32BIT flag set to in the assembly? Ie, was it compiled with AnyCPU, x86, etc? You can use corflags.exe with the .net sdk to find out.
Prior to VS2010, the default was AnyCPU which meant it ran as 64 bit on 64 bit OS, and 32 bit on 32 bit OS.
As of VS2010, the IDE defaults to x86, which means it runs as 32 bit no matter what.
32 bit apps need 32 bit odp/client. 64 bit apps need 64 bit odp/client.
The error you're getting usually means you have the wrong bits (32/64) of the Oracle client installed.
Assuming you have the wrong client bits installed, you could either
a) make the app run as the other bits by setting/clearing the 32BIT flag (also by using corflags.exe)
b) install the other bits of Oracle client software. a 32 bit home and a 64 bit home play rather nicely together for the most part, but you need to install them into separate homes.
Hope it helps,
Greg

Unable to start default LocalDB instance on Windows 8 x86

Cannot start the default LocalDB instance, in our application or by typing in 'sqllocaldb s "v11.0"' on the command line. This issue only occurs on Windows 8 x86. Works fine on Windows 7 x86/64 and on Windows 8 x64. Have gotten the same results
on a physical Windows 8 x86 box, as well as on a Windows 8 x86 VM we created to retest the issue. ASP.NET 4.5 has been enabled in Windows Features. Here's what the Instance's error log has to say:
2012-11-01 16:22:17.90 Server      Microsoft SQL Server 2012 - 11.0.2318.0 (Intel X86)
   Apr 19 2012 11:55:51
   Copyright (c) Microsoft Corporation
   Express Edition on Windows NT 6.2 <X86> (Build 9200: ) (Hypervisor)
2012-11-01 16:22:17.90 Server      (c) Microsoft Corporation.
2012-11-01 16:22:17.90 Server      All rights reserved.
2012-11-01 16:22:17.90 Server      Server process ID is 2932.
2012-11-01 16:22:17.91 Server      System Manufacturer: 'Microsoft Corporation', System Model: 'Virtual Machine'.
2012-11-01 16:22:17.91 Server      Authentication mode is MIXED.
2012-11-01 16:22:17.91 Server      Logging SQL Server messages in file 'C:\Users\Testing\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0\error.log'.
2012-11-01 16:22:17.91 Server      The service account is 'TestWin8x86\Testing'. This is an informational message; no user action is required.
2012-11-01 16:22:17.91 Server      Command Line Startup Parameters:
   -c
   -S "MSSQL11E.LOCALDB"
   -s "LOCALDB#C930B37E"
   -d "C:\Users\Testing\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0\master.mdf"
   -l "C:\Users\Testing\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0\mastlog.ldf"
   -e "C:\Users\Testing\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0\error.log"
2012-11-01 16:22:18.14 Server      SQL Server detected 1 sockets with 2 cores per socket and 2 logical processors per socket, 2 total logical processors; using 2 logical processors based on SQL Server licensing. This is an informational
message; no user action is required.
2012-11-01 16:22:18.14 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2012-11-01 16:22:18.14 Server      Detected 2047 MB of RAM. This is an informational message; no user action is required.
2012-11-01 16:22:18.14 Server      Using conventional memory in the memory manager.
2012-11-01 16:22:18.21 Server      Node configuration: node 0: CPU mask: 0x00000003:0 Active CPU mask: 0x00000003:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only.
No user action is required.
2012-11-01 16:22:18.22 Server      Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2012-11-01 16:22:18.23 Server      Software Usage Metrics is disabled.
2012-11-01 16:22:18.23 spid8s      Starting up database 'master'.
2012-11-01 16:22:18.26 spid8s      1 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2012-11-01 16:22:18.28 spid8s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2012-11-01 16:22:18.36 Server      CLR version v4.0.30319 loaded.
2012-11-01 16:22:18.44 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework\v4.0.30319\.
2012-11-01 16:22:18.44 spid8s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2012-11-01 16:22:18.44 spid8s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2012-11-01 16:22:18.49 spid8s      SQL Trace ID 1 was started by login "sa".
2012-11-01 16:22:18.50 spid8s      Server name is 'TESTWIN8X86\LOCALDB#C930B37E'. This is an informational message only. No user action is required.
2012-11-01 16:22:18.51 spid11s     Server local connection provider is ready to accept connection on [ \\.\pipe\LOCALDB#C930B37E\tsql\query ].
2012-11-01 16:22:18.52 spid11s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace
flag 7806. This is an informational message only. No user action is required.
2012-11-01 16:22:18.52 spid8s      Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn\\ftimport.dll'.
2012-11-01 16:22:18.53 spid9s      Starting up database 'mssqlsystemresource'.
2012-11-01 16:22:18.53 spid8s      Error: 17204, Severity: 16, State: 1.
2012-11-01 16:22:18.53 spid8s      FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf for file number 0. OS error: 3(The system cannot find the path specified.).
2012-11-01 16:22:18.53 spid8s      Error: 5120, Severity: 16, State: 101.
2012-11-01 16:22:18.53 spid8s      Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\MSDBData.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2012-11-01 16:22:18.53 spid9s      The resource database build version is 11.00.2318. This is an informational message only. No user action is required.
2012-11-01 16:22:18.58 spid9s      Starting up database 'model'.
2012-11-01 16:22:18.58 spid9s      Error: 17204, Severity: 16, State: 1.
2012-11-01 16:22:18.58 spid9s      FCB::Open failed: Could not open file e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf for file number 1. OS error: 3(The system cannot find the path specified.).
2012-11-01 16:22:18.58 spid9s      Error: 5120, Severity: 16, State: 101.
2012-11-01 16:22:18.58 spid9s      Unable to open the physical file "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\model.mdf". Operating system error 3: "3(The system cannot find the path specified.)".
2012-11-01 16:22:18.58 spid9s      Error: 17207, Severity: 16, State: 1.
2012-11-01 16:22:18.58 spid9s      FileMgr::StartLogFiles: Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file 'e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf'.
Diagnose and correct the operating system error, and retry the operation.
2012-11-01 16:22:18.58 spid9s      File activation failure. The physical file name "e:\sql11_main_t.obj.x86release\sql\mkmastr\databases\objfre\i386\modellog.ldf" may be incorrect.
2012-11-01 16:22:18.58 spid9s      Error: 945, Severity: 14, State: 2.
2012-11-01 16:22:18.58 spid9s      Database 'model' cannot be opened due to inaccessible files or insufficient memory or disk space. See the SQL Server errorlog for details.
2012-11-01 16:22:18.58 spid9s      SQL Trace was stopped due to server shutdown. Trace ID = '1'. This is an informational message only; no user action is required.

Good idea. The log on a working Windows 8 x64 installation is almost identical, until the errors appear. Tried using SQL Server Management Studio 2012 to crack open the master.mdf on the Windows x86 database, but the LocalDB startup issue prevents
me from connecting to the instance. Also tried using Systools MDF Viewer, but it won't recognize the file. Guess it doesn't support 2012. Here's the log from the "good" installation:
2012-11-01 12:18:05.12 Server      Microsoft SQL Server 2012 - 11.0.2318.0 (X64)
   Apr 19 2012 11:53:44
   Copyright (c) Microsoft Corporation
   Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2012-11-01 12:18:05.12 Server      (c) Microsoft Corporation.
2012-11-01 12:18:05.12 Server      All rights reserved.
2012-11-01 12:18:05.12 Server      Server process ID is 3676.
2012-11-01 12:18:05.12 Server      System Manufacturer: 'powerspec', System Model: 'B667'.
2012-11-01 12:18:05.12 Server      Authentication mode is MIXED.
2012-11-01 12:18:05.12 Server      Logging SQL Server messages in file 'C:\Users\MobileEpiphany\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0\error.log'.
2012-11-01 12:18:05.12 Server      The service account is 'MEDJK2\MobileEpiphany'. This is an informational message; no user action is required.
2012-11-01 12:18:05.12 Server      Command Line Startup Parameters:
   -c
   -S "MSSQL11E.LOCALDB"
   -s "LOCALDB#1AFEC16C"
   -d "C:\Users\MobileEpiphany\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0\master.mdf"
   -l "C:\Users\MobileEpiphany\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0\mastlog.ldf"
   -e "C:\Users\MobileEpiphany\AppData\Local\Microsoft\Microsoft SQL Server Local DB\Instances\v11.0\error.log"
2012-11-01 12:18:05.27 Server      SQL Server detected 1 sockets with 4 cores per socket and 4 logical processors per socket, 4 total logical processors; using 4 logical processors based on SQL Server licensing. This is an informational
message; no user action is required.
2012-11-01 12:18:05.27 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2012-11-01 12:18:05.27 Server      Detected 4095 MB of RAM. This is an informational message; no user action is required.
2012-11-01 12:18:05.27 Server      Using conventional memory in the memory manager.
2012-11-01 12:18:05.32 Server      Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2012-11-01 12:18:05.32 Server      Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2012-11-01 12:18:05.33 Server      Software Usage Metrics is disabled.
2012-11-01 12:18:05.33 spid5s      Starting up database 'master'.
2012-11-01 12:18:05.38 spid5s      4 transactions rolled forward in database 'master' (1:0). This is an informational message only. No user action is required.
2012-11-01 12:18:05.39 spid5s      0 transactions rolled back in database 'master' (1:0). This is an informational message only. No user action is required.
2012-11-01 12:18:05.39 spid5s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2012-11-01 12:18:05.42 Server      CLR version v4.0.30319 loaded.
2012-11-01 12:18:05.45 Server      Common language runtime (CLR) functionality initialized using CLR version v4.0.30319 from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\.
2012-11-01 12:18:05.56 spid5s      SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2012-11-01 12:18:05.56 spid5s      SQL Server Audit has started the audits. This is an informational message. No user action is required.
2012-11-01 12:18:05.58 spid5s      SQL Trace ID 1 was started by login "sa".
2012-11-01 12:18:05.58 spid5s      Server name is 'MEDJK2\LOCALDB#1AFEC16C'. This is an informational message only. No user action is required.
2012-11-01 12:18:05.59 spid11s     Server local connection provider is ready to accept connection on [ \\.\pipe\LOCALDB#1AFEC16C\tsql\query ].
2012-11-01 12:18:05.59 spid11s     Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace
flag 7806. This is an informational message only. No user action is required.
2012-11-01 12:18:05.59 spid11s     SQL Server is now ready for client connections. This is an informational message; no user action is required.
2012-11-01 12:18:05.60 spid5s      Failed to verify Authenticode signature on DLL 'C:\Program Files\Microsoft SQL Server\110\LocalDB\Binn\\ftimport.dll'.
2012-11-01 12:18:05.60 spid9s      Starting up database 'mssqlsystemresource'.
2012-11-01 12:18:05.66 spid9s      The resource database build version is 11.00.2318. This is an informational message only. No user action is required.
2012-11-01 12:18:05.68 spid5s      Starting up database 'msdb'.
2012-11-01 12:18:05.76 spid9s      Starting up database 'model'.
2012-11-01 12:18:05.84 spid9s      Clearing tempdb database.
2012-11-01 12:18:06.15 spid9s      Starting up database 'tempdb'.
2012-11-01 12:18:06.33 spid14s     The Service Broker endpoint is in disabled or stopped state.
2012-11-01 12:18:06.33 spid14s     The Database Mirroring endpoint is in disabled or stopped state.
2012-11-01 12:18:06.38 spid14s     Service Broker manager has started.
2012-11-01 12:18:06.47 spid5s      Recovery is complete. This is an informational message only. No user action is required.

Need to install Adobe Reader to a 64 bit folder and not (x86) default 32 bit folder

Hi
We have a program on our system which searches on local machines for their Adobe Reader in able to open up a pdf. Only one pc on our network is 64 bit and of course when installing Reader will default install to C:\Program Files (x86).
We need to be able to install AR to C:\Program Files to allow the databse to work on this 64 bit pc.
I have tried using the cmd feature and also adobe customisation wizard but to no avail.
Is there any way to change folder location on install?
Many thanks

The software is wrong? How do you mean? The software by default tells the users computers to use Adobe Reader to open up the created pdf files by this program. This program has been designed for a specialist purpose and cost thousands. Unfortunately the default location is under the 32 bit directory which is Program Files on all the 32 bit machines which is just fine. Now we need the 64 bit pc to be able to run this software but changing the default location of where to find adobe reader would mean the 32 bit pc's would not work. To add another location would mean the designer of the program charging another huge amount (approx £300).
All I am asking is there anyway installing AR can override the default location in a 64 bit pc and put adobe in C:\Program Files as if it were a 32 bit pc?
Many thanks for replies so far

"/network/physical:default" problem in Solaris 10 x86

I have a problem with network interface on Solaris 10 x86 on HP Proliant ML 370 G4 server.
The problem is that at the boot time it report some problem with network interface and writes "see svcs -x"
# svcs -x
svc:/network/physical:default (physical network interfaces)
State: maintenance since Mon 21 Mar 2005 09:55:39
Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
See: http://sun.com/msg/SMF-8000-KS
See: ifconfig(1M)
See: /etc/svc/volatile/network-physical:default.log
Impact: 5 dependent services are not running. (Use -v for list.)
svc:/application/print/server:default (LP print server)
State: disabled since Mon 21 Mar 2005 09:55:38
Reason: Disabled by an administrator.
See: http://sun.com/msg/SMF-8000-05
See: lpsched(1M)
Impact: 2 dependent services are not running. (Use -v for list.)
svcs -v shows that /network/physical:default need maintance
# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000
# svcs -xv /network/physical:default
svc:/network/physical:default (physical network interfaces)
State: maintenance since Mon 21 Mar 2005 09:55:39
Reason: Start method exited with $SMF_EXIT_ERR_CONFIG.
See: http://sun.com/msg/SMF-8000-KS
See: man -M /usr/share/man -s 1M ifconfig
See: /etc/svc/volatile/network-physical:default.log
Impact: 5 dependent services are not running:
svc:/milestone/network:default
svc:/network/nfs/nlockmgr:default
svc:/network/nfs/client:default
svc:/network/nfs/status:default
svc:/network/ssh:default
# more /etc/svc/volatile/network-physical:default.log
[ Mar 21 09:55:37 Enabled. ]
[ Mar 21 09:55:38 Executing start method ("/lib/svc/method/net-physical") ]
[ Mar 21 09:55:38 Timeout override by svc.startd. Using infinite timeout ]
ifconfig: plumb: eri0: No such file or directory
moving addresses from failed IPv4 interfaces: eri0 (couldn't move, no alternative interface).
[ Mar 21 09:55:39 Method "start" exited with status 96 ]
I have not any eri device in /dev directory
How can I add a network interface?

Try elxl0 :-) This is: E L X L - zero :-) instead of: qfe0.
PS The 0 can increase to 1,2,.. if you have more 3com cards in the system.

Solaris 8 x86 doesn't ask for default route at install time

The Solaris 8 installation program doesn't ask what the machine's default route should be. This means that when you configure DNS servers later on that aren't on the same subnet as the machine you get error messages.
Anyone know a work around?

Re: Solaris 8 x86 doesn't ask for default route at install time
I had the same problem.
I was wondering why something so essential is missing for the GUI Install, it would be possilbe a patch to correct this?, instead of configuring nsswitch, and another files.
The easier the install and admin, more users solaris will have on Intel Platform.
P.D. Sorry for my english.
05-sep-00 : 0:51 :GavinCam
The Solaris 8 installation program doesn't ask what the machine's default route should be. This means that when you configure DNS servers later on that aren't on the same subnet as the machine you get error messages.
Anyone know a work around?

Booting x86 with serial console by default

Let's say I have a x86 box with no monitor and no keyboard. I'd like to boot the x86 Solaris 10 installation dvd and have it booted with the 'serial console' option. However, it's not selected by default and I can't select it without using the keyboard.
Is it possible to have the x86 installation DVD boot with serial console support by default?

Well, https://wiki.archlinux.org/index.php/Re … nstall_ISO doesn't help, genisoimage created iso is still not bootable.
The iso created with Archiso boots but - it creates an x86_64 kernel only...
Last edited by piwwo (2013-06-14 13:55:31)

No Largepages by default on x86

Similar Messages

Maybe you are looking for