Cannot install InDesign Server CS4: Win 2003 x64

One of my customers has just purchased InDesign Server CS4 (Single Instance, Premium License) and I'm trying to install build 525 on Windows Server 2003 Enterprise Edition x64. I select the default 'Easy/Recommended' installation settings and the installer runs through, but then displays the message below. I've tried installing to different directories but hit the same error every time.
When I select 'Next' the installer lists the following products and components have been successfully installed:
Adobe InDesign CS4 Server
ID Server service files
ID Server components
ID Server service files (x64)
However, it doesn't appear to have installed correctly, as if I start the InDesign Server service and then execute the following test script nothing happens:
#target indesignserver;
//HelloWorld.jsx
//Create a new document.
    var myDocument = app.documents.add();
//Get a reference to the first page.
    var myPage = myDocument.pages.item(0);
//Create a text frame.
    var myTextFrame = myPage.textFrames.add();
//Specify the size and shape of the text frame.
    myTextFrame.geometricBounds = ["6p0", "6p0", "18p0", "18p0"];
//Enter text in the text frame.
    myTextFrame.contents = "Hello World!";
//Save the document (fill in a valid file path).
    myDocument.save(new File("/e/HelloWorld.indd"));
//Close the document.
//Close the document.
    app.documents.item(0).close();
Any ideas?

I gave up on this and ended up installing the 32 bit version which works fine. It appears that there is a problem installing 64 bit on Windows 2003 Enterprise Edition so watch out...

Similar Messages

  • Indesign Server CS4 service is not starting on Windows Server 2003 64bit

    Hello guys,
    I am not able to start Indesign Server CS4 service on windows Server 2003 SP2 64bit .
    I have successfuly configured the service with InDesignServerService.msc, set the port to 18555. InDesignServerWinService the Log On option is set to "This Account". Also tried using different accounts!
    When starting the indesign service from windows Service control panel I get this error:
    Could not start the InDesignServerService x64 service on Local Computer.
    Error 1053: The service did not respond to the start or control request in a timely fashion.
    Error log from windows Event viewer:
    Error
    Timeout (30000 milliseconds) waiting for the InDesignServerService x64 service to connect.
    Indesign server application works if launching from command line with the specified port 18555.
    If trying to lauch IndesignServerService.exe from command line, there is a delay and finally nothing happens.
    I have also tried launching 32bit indesign server service and the same error comes.
    Would be grateful for your thoughts!
    Message was edited by: Andrewdev
    Server specs:
    Windows Server 2003
    Standard x64 Edition
    Service Pack 2
    Intel Xeon CPU 3.00Ghz
    9.76 GB of Ram
    Server is running virtualy on Xen hypervisor, there is no antivirus and windows firewall is disabled.

    Hi Chandi,
          If Microsoft fix is not working or it is too old to apply then go for manual process i.e.;
          In the Microsoft KB article follow this :-
         Services that use the local system account to log on to a Windows Server 2003-based computer start if the Allow service to interact with desktop
         option is turned on. To turn this option on, follow these steps:
    In the Services tool, click the service that you want to start, and then click Properties.
    Right-click the Log On tab, and then click to select the Allow service to interact with desktop check box.
    Click OK to exit the Properties dialog box.
       This will solve your problem.
       Thanks,
       Akansh Upadhyaya,
       System Engineer,
       (Windows + Unix.)

  • Installing Transparency Flattener Preset for Indesign Server CS4

    I'm trying to figure out how to install a transparency flattener preset for InDesign Server CS4.
    I can see how they are installed for the InDesign app.  Edit -> Transparency Flattener Presets...
    But I'm not sure which directory to install these on for the server.
    I've seen a post that mentions:
    C:\Documents and Settings\<UserName>\Application Data\Adobe\InDesign\Version 6.0\en_US\Transparency Flattener Presets
    /Users/<UserName>/Library/Preferences/Adobe InDesign/Version 6.0/en_US/Transparency Flattener Presets
    for the Desktop version.  But when I place files here even for the CS4 Desktop, they don't seem to show up in the UI.
    Any help would be appreciated,
    Thanks,
    Dennis

    Thanks, to get this working in a server script, I ended up just programmatically creating the flattener preset, rather than worrying about the .flst files.  (Java code below)
      //Setup Transparency Flattener (if not in application)
      FlattenerPreset flattenerPreset = app.getNamedChildFlattenerPreset("Test");
      if (flattenerPreset == null) {
          flattenerPreset = app.addFlattenerPreset();
          flattenerPreset.setName("Test");
          flattenerPreset.setRasterVectorBalance(VariableTypeUtils.createLong(100));
          flattenerPreset.setLineArtAndTextResolution(2400.0);
          flattenerPreset.setGradientAndMeshResolution(400.0);
          flattenerPreset.setConvertAllTextToOutlines(false);
          flattenerPreset.setConvertAllStrokesToOutlines(false);
          flattenerPreset.setClipComplexRegions(false);
      pdfPreset.setAppliedFlattenerPreset(flattenerPreset);

  • Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"

    I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
    Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
    I tried all the things below;
    * I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
    * I'm deleting all the keys related with Sql Server from Regedit.
    * Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
    Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
    * My firewall is already closed. And i have not any antivirus software.
    * I gave the permission for port 1433 on firewall.
    Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.

    Here's the ERRORLOG file which i found under the folder;
    Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
    2014-09-27 03:39:40.15 Server      Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64) 
    Apr  2 2010 15:48:46 
    Copyright (c) Microsoft Corporation
    Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
    2014-09-27 03:39:40.15 Server      (c) Microsoft Corporation.
    2014-09-27 03:39:40.15 Server      All rights reserved.
    2014-09-27 03:39:40.15 Server      Server process ID is 5768.
    2014-09-27 03:39:40.15 Server      System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
    2014-09-27 03:39:40.15 Server      Authentication mode is MIXED.
    2014-09-27 03:39:40.15 Server      Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
    2014-09-27 03:39:40.15 Server      Registry startup parameters: 
    -d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
    -e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
    -l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
    2014-09-27 03:39:40.15 Server      Command Line Startup Parameters:
    -m SqlSetup
    -f
    -Q
    -q Turkish_CI_AS
    -T 4022
    -T 4010
    -T 3659
    -T 3610
    2014-09-27 03:39:40.18 Server      Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.  After
    the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
    2014-09-27 03:39:40.18 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.18 Server      Detected 4 CPUs. This is an informational message; no user action is required.
    2014-09-27 03:39:40.31 Server      Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
    2014-09-27 03:39:40.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.
    2014-09-27 03:39:40.43 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.
    2014-09-27 03:39:40.45 Server      Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
    is required.
    2014-09-27 03:39:40.45 spid7s      Warning ******************
    2014-09-27 03:39:40.45 spid7s      SQL Server started in single-user mode. This an informational message only. No user action is required.
    2014-09-27 03:39:40.46 spid7s      Starting up database 'master'.
    2014-09-27 03:39:40.52 spid7s      Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
    2014-09-27 03:39:40.58 spid7s      SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
    2014-09-27 03:39:40.59 spid7s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:40.59 spid7s      Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
    2014-09-27 03:39:40.59 spid7s      Starting up database 'mssqlsystemresource'.
    2014-09-27 03:39:40.61 spid7s      The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
    2014-09-27 03:39:40.94 spid7s      Password policy update was successful.
    2014-09-27 03:39:40.94 spid8s      Starting up database 'model'.
    2014-09-27 03:39:40.95 spid7s      Server name is 'CAGATAY'. This is an informational message only. No user action is required.
    2014-09-27 03:39:41.21 spid8s      Clearing tempdb database.
    2014-09-27 03:39:41.21 spid10s     A new instance of the full-text filter daemon host process has been successfully started.
    2014-09-27 03:39:41.24 Server      A self-generated certificate was successfully loaded for encryption.
    2014-09-27 03:39:41.24 Server      Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
    2014-09-27 03:39:41.24 Server      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.
    2014-09-27 03:39:41.28 Server      The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
    to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
    2014-09-27 03:39:41.28 Server      SQL Server is now ready for client connections. This is an informational message; no user action is required.
    2014-09-27 03:39:41.70 spid8s      Starting up database 'tempdb'.
    2014-09-27 03:39:41.86 spid7s      Warning ******************
    2014-09-27 03:39:41.86 spid7s      Attempting to change default collation to Turkish_CI_AS.
    2014-09-27 03:39:41.92 spid7s       index restored for master.syspriorities.
    2014-09-27 03:39:41.95 spid7s       index restored for master.sysbrickfiles.
    2014-09-27 03:39:41.96 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:41.96 spid7s       index restored for master.sysowners.
    2014-09-27 03:39:42.13 spid7s       index restored for master.sysdbreg.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.16 spid7s       index restored for master.sysschobjs.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.17 spid7s       index restored for master.syscolpars.
    2014-09-27 03:39:42.17 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxlgns.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysxsrvs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.sysnsobjs.
    2014-09-27 03:39:42.18 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.18 spid7s       index restored for master.syscerts.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysrmtlgns.
    2014-09-27 03:39:42.19 spid7s       index restored for master.sysxprops.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.19 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysscalartypes.
    2014-09-27 03:39:42.31 spid7s       index restored for master.sysidxstats.
    2014-09-27 03:39:42.31 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysendpts.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysclsobjs.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysremsvcbinds.
    2014-09-27 03:39:42.32 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.32 spid7s       index restored for master.sysrts.
    2014-09-27 03:39:42.33 spid7s       index restored for master.sysasymkeys.
    2014-09-27 03:39:42.33 spid7s       index restored for master.syssqlguides.
    2014-09-27 03:39:42.44 spid7s       index restored for master.syssoftobjrefs.
    2014-09-27 03:39:42.47 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.48 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.49 spid7s       index restored for master.spt_values.
    2014-09-27 03:39:42.49 spid7s       index restored for master.MSreplication_options.
    2014-09-27 03:39:42.56 spid7s       index restored for tempdb.syspriorities.
    2014-09-27 03:39:42.56 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysowners.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.57 spid7s       index restored for tempdb.sysschobjs.
    2014-09-27 03:39:42.57 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.59 spid7s       index restored for tempdb.syscolpars.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysnsobjs.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.syscerts.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysxprops.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.60 spid7s       index restored for tempdb.sysscalartypes.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysidxstats.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysclsobjs.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysremsvcbinds.
    2014-09-27 03:39:42.61 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.61 spid7s       index restored for tempdb.sysrts.
    2014-09-27 03:39:42.62 spid7s       index restored for tempdb.sysasymkeys.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssqlguides.
    2014-09-27 03:39:42.69 spid7s       index restored for tempdb.syssoftobjrefs.
    2014-09-27 03:39:42.75 spid7s       index restored for model.syspriorities.
    2014-09-27 03:39:42.75 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.75 spid7s       index restored for model.sysowners.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:42.76 spid7s       index restored for model.sysschobjs.
    2014-09-27 03:39:42.76 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscolpars.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysnsobjs.
    2014-09-27 03:39:43.00 spid7s       index restored for model.syscerts.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysxprops.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysscalartypes.
    2014-09-27 03:39:43.00 spid7s       index restored for model.sysidxstats.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysclsobjs.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysremsvcbinds.
    2014-09-27 03:39:43.01 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysrts.
    2014-09-27 03:39:43.01 spid7s       index restored for model.sysasymkeys.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssqlguides.
    2014-09-27 03:39:43.01 spid7s       index restored for model.syssoftobjrefs.
    2014-09-27 03:39:43.02 spid7s      Starting up database 'msdb'.
    2014-09-27 03:39:43.82 spid7s       index restored for msdb.syspriorities.
    2014-09-27 03:39:43.85 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:43.93 spid7s       index restored for msdb.sysowners.
    2014-09-27 03:39:43.99 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.00 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.09 spid7s       index restored for msdb.sysschobjs.
    2014-09-27 03:39:44.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.syscolpars.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.20 spid7s       index restored for msdb.sysnsobjs.
    2014-09-27 03:39:44.20 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.25 spid7s       index restored for msdb.syscerts.
    2014-09-27 03:39:44.25 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s       index restored for msdb.sysxprops.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.26 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.27 spid7s       index restored for msdb.sysscalartypes.
    2014-09-27 03:39:44.37 spid7s       index restored for msdb.sysidxstats.
    2014-09-27 03:39:44.41 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysclsobjs.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysremsvcbinds.
    2014-09-27 03:39:44.42 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.42 spid7s       index restored for msdb.sysrts.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.sysasymkeys.
    2014-09-27 03:39:44.54 spid7s       index restored for msdb.syssqlguides.
    2014-09-27 03:39:44.59 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.74 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:44.85 spid7s       index restored for msdb.syssoftobjrefs.
    2014-09-27 03:39:44.89 spid7s       index restored for msdb.syspolicy_policies_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.sysproxies.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syscollector_execution_stats_internal.
    2014-09-27 03:39:44.90 spid7s       index restored for msdb.syssubsystems.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_primary_secondaries.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.sysdownloadlist.
    2014-09-27 03:39:44.91 spid7s       index restored for msdb.log_shipping_monitor_primary.
    2014-09-27 03:39:44.92 spid7s       index restored for msdb.sysoriginatingservers.
    2014-09-27 03:39:44.93 spid7s       index restored for msdb.log_shipping_monitor_history_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_monitor_error_detail.
    2014-09-27 03:39:44.95 spid7s       index restored for msdb.log_shipping_secondary.
    2014-09-27 03:39:44.97 spid7s       index restored for msdb.log_shipping_secondary_databases.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.log_shipping_monitor_secondary.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysjobs.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.sysutility_ucp_mi_database_health_internal.
    2014-09-27 03:39:45.10 spid7s       index restored for msdb.syscollector_blobs_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysjobsteps.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.logmarkhistory.
    2014-09-27 03:39:45.11 spid7s       index restored for msdb.sysutility_mi_session_statistics_internal.
    2014-09-27 03:39:45.12 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.12 spid7s       index restored for msdb.sysdtscategories.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.syspolicy_target_sets_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysschedules.
    2014-09-27 03:39:45.33 spid7s       index restored for msdb.sysdac_instances_internal.
    2014-09-27 03:39:45.33 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.50 spid7s       index restored for msdb.sysssispackages.
    2014-09-27 03:39:45.51 spid7s       index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
    2014-09-27 03:39:45.51 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysssispackagefolders.
    2014-09-27 03:39:45.52 spid7s       index restored for msdb.sysdac_history_internal.
    2014-09-27 03:39:45.53 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syscategories.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservers.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.systargetservergroups.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.syspolicy_policy_category_subscriptions_internal.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysalerts.
    2014-09-27 03:39:45.62 spid7s       index restored for msdb.sysoperators.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syspolicy_system_health_state_internal.
    2014-09-27 03:39:45.63 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.63 spid7s       index restored for msdb.syscollector_config_store_internal.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.65 spid7s       index restored for msdb.sysmanagement_shared_server_groups_internal.
    2014-09-27 03:39:45.66 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.sysmanagement_shared_registered_servers_internal.
    2014-09-27 03:39:45.66 spid7s       index restored for msdb.syscachedcredentials.
    2014-09-27 03:39:45.79 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.syscollector_collection_sets_internal.
    2014-09-27 03:39:45.79 spid7s       index restored for msdb.sysutility_ucp_dac_health_internal.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.MSdbms_datatype.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysmail_profile.
    2014-09-27 03:39:45.80 spid7s       index restored for msdb.sysutility_ucp_managed_instances_internal.
    2014-09-27 03:39:45.83 spid7s       index restored for msdb.syspolicy_management_facets.
    2014-09-27 03:39:45.84 spid7s       index restored for msdb.sysutility_ucp_mi_health_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syscollector_collector_types_internal.
    2014-09-27 03:39:45.86 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.86 spid7s       index restored for msdb.syspolicy_configuration_internal.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_facet_events.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.sysmail_account.
    2014-09-27 03:39:45.87 spid7s       index restored for msdb.syspolicy_conditions_internal.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.sysutility_ucp_health_policies_internal.
    2014-09-27 03:39:45.88 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:45.88 spid7s       index restored for msdb.syscollector_collection_items_internal.
    2014-09-27 03:39:45.90 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysmail_servertype.
    2014-09-27 03:39:46.00 spid7s       index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
    2014-09-27 03:39:46.02 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_configuration_internal.
    2014-09-27 03:39:46.03 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.03 spid7s       index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.sysmail_server.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_policy_categories_internal.
    2014-09-27 03:39:46.04 spid7s       index restored for msdb.syspolicy_object_sets_internal.
    2014-09-27 03:39:46.04 spid7s      Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
    because the former has to be smaller than the latter.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysmail_configuration.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.sysdbmaintplan_databases.
    2014-09-27 03:39:46.05 spid7s       index restored for msdb.log_shipping_primary_databases.
    2014-09-27 03:39:46.39 spid7s      The default collation was successfully changed.
    2014-09-27 03:39:46.39 spid7s      Recovery is complete. This is an informational message only. No user action is required.
    2014-09-27 03:39:47.17 spid51      Changed database context to 'master'.
    2014-09-27 03:39:47.18 spid51      Changed language setting to us_english.
    2014-09-27 03:39:47.72 spid51      Setting database option RECOVERY to FULL for database model.
    2014-09-27 03:39:47.84 spid51      Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.84 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:47.98 spid51      Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
    2014-09-27 03:39:47.98 spid51      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
    2014-09-27 03:39:48.27 spid51      Error: 15007, Severity: 16, State: 1.
    2014-09-27 03:39:48.27 spid51      '' is not a valid login or you do not have permission.
    2014-09-27 03:51:25.13 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:25.13 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:32.67 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:51:32.67 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:51:42.11 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:51:42.11 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:52:42.07 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:52:42.07 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:53:01.23 Logon       Error: 18461, Severity: 14, State: 1.
    2014-09-27 03:53:01.23 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
    2014-09-27 03:53:17.57 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:53:17.57 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    2014-09-27 03:53:32.54 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:53:32.54 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:04.29 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:04.29 Logon       Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:10.36 Logon       Error: 18456, Severity: 14, State: 5.
    2014-09-27 03:54:10.36 Logon       Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
    2014-09-27 03:54:47.18 Logon       Error: 18456, Severity: 14, State: 8.
    2014-09-27 03:54:47.18 Logon       Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
    Resolve the error, please refer to the following links.
    Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
    could not register the SPN Kerberos:
    http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html  
    Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server

  • Cannot install updates to CS4 in Win 7 64-bit

    I have installed CS4 on a new Win 7 64-bit PC.  There are 5 updates to install, however, although they download, I cannot install them
    I have updated the driver of my AMD Radeon graphics card.
    Please can you help?
    Regards......

    Many thanks Curt and Trevor.
    I'm afraid I'm not used to how the operation of this Forum is structured, so I apologise for my delay in replying to you.  Indeed it still puzzles me a bit!
    As the result of your comments, I am satisfied that my CS 4 has been updated as far as it can be!  I'm on Version 11 and the Camera Raw Version is 5.0.0.178
    No later Camera Raw versions can be downloaded into CS 4 and that includes the requirement of my current SLR and my Compact, however, I am free of that worry, as I always convert my images to .DNG as I download from the camera!
    I understand now Curt, how to determine the individual download files included in a proposed update operation......so thank you for that.
    Regards and again than you.....Noel

  • Spool server on Windows 2003 x64 ?

    Hi,
    I'm installing SAP NetWeaver PI 7.1 on Windows 2003 x64 with MaxDB.
    Printing Guide for SAP NetWeaver PI 7.1 states "For a Microsoft Windows XP host, choose access method C. other Microsoft Windows operating systems are not suitable for local printing, as you cannot set up a spool server on them."
    However, by default, there is a spool server defined in my installation of SAP NetWeaver PI 7.1 on Windows 2003 x64.  But I see plenty of "Spool / print: Calling program reports invalid handle for TemSe object (magic==X'NULL-ptr')" errors in the system log when the background processes run every night.
    Printing Guide for SAP NetWeaver 7.0 talks about a SAP spool server running on "the Microsoft Windows NT/Windows 2000 system", suggesting that Windows systems other than XP are supported for local printing.
    Is that correct?  i.e. Has local printing support for Windows 2003 been removed in PI 7.1 ?
    I'm surprised, and more than a little confused by this.  I'd appreciate any help/explanation.
    Regards,
    Mark

    Just a follow-up if anyone's interested...
    I did try setting-up Access Method C in my NetWeaver 7.1 on Windows 2003 x64 with MaxDB and so far the local printing seems to be working OK. So, either:
    a) The Printing Guide for SAP NetWeaver PI 7.1 is wrong on this issue.
    b) The Printing Guide for SAP NetWeaver PI 7.1 is right, and this is an undocumented behavior that might break in the future.
    c) I just got lucky (and I shouldn't look a gift horse in the mouth).
    Also, Access Method G works fine.

  • Cannot install Exchange server 2013

    hey,
    I'm trying to install exchange server 2013 on windows server 2012 and I getting this error :
    One or more servers in the existing organization are running Exchange 2000 Server or Exchange Server 2003. Installation can't proceed until all Exchange 2000 or Exchange 2003 servers are removed.
    Warning:
    Cannot find the Recipient Update Service responsible for domain 'DC=Nesstr,DC=com'. New and existing users may not be properly Exchange-enabled.
    Now, I think before I got here there was exchange server 2003 in virtual machine but I cant find the vm, probably someone has deleted the vm without uninstall the exchange properly and maybe this is the problem.
    anyone suggestion what to do next ?
    best Regards,
    Idan keshet

    Hi Idan,
    We need to do these steps to connect to Configuration:
    1. Open ADSI Edit.
    2. Right-click ADSI Edit, select Connect to… .
    3. In Connection Point, Select a well known Naming Context > Configuration.
    4. Click OK.
    Thanks,
    Winnie Liang
    TechNet Community Support

  • Installing OID on 10G / Win 2003

    I need to find two things:
    (1) The install file(s) for OID for 10G on win 2003.
    (2) Install instructions for installing OID for 10g on win 2003.
    I have no idea how to install OID for 10G and the 10G docs do not appear to cover OID. I think 9i used to provide some info . . .
    Thanks,
    Michael

    It would be useful, you post the whole error stack. RMAN-10038 is a very generic error, which means only the database session has gone for some reason. It's an error like ORA-03113 (end of communication channel) from the database server.
    A very general hint is, there could be a lack of resources, you may try to increase the settings for PGA and SHARED_POOL_SIZE, if the server allows it.

  • Cannot install SQL Server 2008 R2 on Widows 7 Pro

    I've tried unsuccesfully to install SQL Server 2008 R2 on my laptop running Windows 7 Pro.
    I previously installed Visual Studio 2010 and downloaded the SQL Server 2008 R2 disk image, burned the disk and then tried to install SQL Server.
    I get a "Microsoft .NET Framework" unhandled exception dialog box with the following detail message:
    See the end of this message for details on invoking
    just-in-time (JIT) debugging instead of this dialog box.
    ************** Exception Text **************
    System.Configuration.ConfigurationErrorsException: An error occurred creating the configuration section handler for userSettings/Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings: Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral,
    PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified. (C:\Users\Louis\AppData\Local\Microsoft_Corporation\LandingPage.exe_StrongName_ryspccglaxmt4nhllj5z3thycltsvyyx\10.0.0.0\user.config line 5) ---> System.IO.FileNotFoundException:
    Could not load file or assembly 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' or one of its dependencies. The system cannot find the file specified.
    File name: 'System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089'
       at System.Configuration.TypeUtil.GetTypeWithReflectionPermission(IInternalConfigHost host, String typeString, Boolean throwOnError)
       at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.Init(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
       at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory.InitWithRestrictedPermissions(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
       at System.Configuration.RuntimeConfigurationRecord.RuntimeConfigurationFactory..ctor(RuntimeConfigurationRecord configRecord, FactoryRecord factoryRecord)
       at System.Configuration.RuntimeConfigurationRecord.CreateSectionFactory(FactoryRecord factoryRecord)
       at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
    WRN: Assembly binding logging is turned OFF.
    To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
    Note: There is some performance penalty associated with assembly bind failure logging.
    To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
       --- End of inner exception stack trace ---
       at System.Configuration.BaseConfigurationRecord.FindAndEnsureFactoryRecord(String configKey, Boolean& isRootDeclaredHere)
       at System.Configuration.BaseConfigurationRecord.GetSectionRecursive(String configKey, Boolean getLkg, Boolean checkPermission, Boolean getRuntimeObject, Boolean requestIsHere, Object& result, Object& resultRuntimeObject)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey, Boolean getLkg, Boolean checkPermission)
       at System.Configuration.BaseConfigurationRecord.GetSection(String configKey)
       at System.Configuration.ClientConfigurationSystem.System.Configuration.Internal.IInternalConfigSystem.GetSection(String sectionName)
       at System.Configuration.ConfigurationManager.GetSection(String sectionName)
       at System.Configuration.ClientSettingsStore.ReadSettings(String sectionName, Boolean isUserScoped)
       at System.Configuration.LocalFileSettingsProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection properties)
       at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
       at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
       at System.Configuration.SettingsBase.get_Item(String propertyName)
       at System.Configuration.ApplicationSettingsBase.GetPropertyValue(String propertyName)
       at System.Configuration.ApplicationSettingsBase.get_Item(String propertyName)
       at Microsoft.SqlServer.Configuration.LandingPage.Properties.Settings.get_WindowPlacement()
       at Microsoft.SqlServer.Configuration.LandingPage.LandingPageForm.OnLoad(EventArgs e)
       at System.Windows.Forms.Form.OnCreateControl()
       at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
       at System.Windows.Forms.Control.CreateControl()
       at System.Windows.Forms.Control.WmShowWindow(Message& m)
       at System.Windows.Forms.Control.WndProc(Message& m)
       at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
       at System.Windows.Forms.ContainerControl.WndProc(Message& m)
       at System.Windows.Forms.Form.WmShowWindow(Message& m)
       at System.Windows.Forms.Form.WndProc(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
       at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
       at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
    ************** Loaded Assemblies **************
    mscorlib
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4952 (win7RTMGDR.050727-4900)
        CodeBase:
    file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
    LandingPage
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase: file:///E:/x86/LandingPage.exe
    System.Windows.Forms
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
    System
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
    System.Drawing
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
    Microsoft.SqlServer.Configuration.Sco
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase:
    file:///E:/x86/Microsoft.SqlServer.Configuration.Sco.DLL
    Microsoft.SqlServer.Chainer.Infrastructure
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase:
    file:///E:/x86/Microsoft.SqlServer.Chainer.Infrastructure.DLL
    System.Xml
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
    Accessibility
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
    Microsoft.SqlServer.Management.Controls
        Assembly Version: 10.0.0.0
        Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
        CodeBase:
    file:///E:/x86/Microsoft.SqlServer.Management.Controls.DLL
    System.Configuration
        Assembly Version: 2.0.0.0
        Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
        CodeBase:
    file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
    ************** JIT Debugging **************
    To enable just-in-time (JIT) debugging, the .config file for this
    application or computer (machine.config) must have the
    jitDebugging value set in the system.windows.forms section.
    The application must also be compiled with debugging
    enabled.
    For example:
    <configuration>
        <system.windows.forms jitDebugging="true" />
    </configuration>
    When JIT debugging is enabled, any unhandled exception
    will be sent to the JIT debugger registered on the computer
    rather than be handled by this dialog box.
    ////  End of message.
    I have all the updates on my laptop per Microsoft Update.
    Any ideas what is wrong?

    Hello,
    Please try the solution posted in the following thread:
    http://social.msdn.microsoft.com/Forums/en/sqlkjsetupandupgrade/thread/35356bf2-6db7-4785-a104-bc62d18913f7
    Hope this helps.
    Regards,
    Alberto Morillo
    SQLCoffee.com

  • Cannot install InDesign on my MAC book pro

    New to Mac, so when I put in the cd, the Adobe folder appearson my desktop, I click on it and select install Adobe InDesign, it opens FTP Client Ultimate to install and of course says cannot install, wrong program.. So I tell it to use Automator, it says cannot install corrupt file, new disk, opened the seal myself. Can anyone shed any light on this?
    this is where I miss windows..
    OS 10.8.5 8gig memory.

    InDesign 2.0 was released in January 2002. Any version of Macintosh which can run Mac OS X 10.8.5 would NOT be able to install InDesign 2.0. It was created before the Mac was using Intel processors, and cannot run on any current Mac.

  • Cannot install SQL Server 2008 R2 Developer on Windows 8.1

    I am unable to install SQL Server 2008 R2 Developer edition on Windows 8.1 Enterprise evaluation and about 3/4 of the way through the installation I get this error msg:
    TITLE: SQL Server 2008 R2 Setup
    The following error has occurred:
    Attempted to perform an unauthorized operation.
    Click 'Retry' to retry the failed action, or click 'Cancel' to cancel this action and continue setup.
    For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.4000.0&EvtType=0x88792597%25400xBB814387
    This is my log file:
    Overall summary:
    Final result: User cancelled
    Exit code (Decimal): 0
    Exit message: User cancelled
    Start time: 2014-04-23 23:49:10
    End time: 2014-04-24 00:03:44
    Requested action: Install
    Machine Properties:
    Machine name: PC
    Machine processor count: 2
    OS version: Future Windows Version
    OS service pack:
    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: 1
    Installation location: F:\My Files\My Downloads\EXISTING\SQLServer2008R2Dev\SQLFULL_ENU\x64\setup\
    Installation edition: DEVELOPER
    User Input Settings:
    ACTION: Install
    ADDCURRENTUSERASSQLADMIN: False
    AGTSVCACCOUNT: NT AUTHORITY\SYSTEM
    AGTSVCPASSWORD: *****
    AGTSVCSTARTUPTYPE: Manual
    ASBACKUPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Backup
    ASCOLLATION: Latin1_General_CI_AS
    ASCONFIGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Config
    ASDATADIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Data
    ASDOMAINGROUP: <empty>
    ASLOGDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Log
    ASPROVIDERMSOLAP: 1
    ASSVCACCOUNT: NT AUTHORITY\SYSTEM
    ASSVCPASSWORD: *****
    ASSVCSTARTUPTYPE: Automatic
    ASSYSADMINACCOUNTS: PC\computername
    ASTEMPDIR: C:\Program Files\Microsoft SQL Server\MSAS10_50.MSSQLSERVER\OLAP\Temp
    BROWSERSVCSTARTUPTYPE: Disabled
    CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
    CUSOURCE:
    ENABLERANU: False
    ENU: True
    ERRORREPORTING: False
    FARMACCOUNT: <empty>
    FARMADMINPORT: 0
    FARMPASSWORD: *****
    FEATURES: SQLENGINE,REPLICATION,FULLTEXT,AS,RS,BIDS,CONN,IS,BC,SDK,BOL,SSMS,ADV_SSMS,OCS
    FILESTREAMLEVEL: 2
    FILESTREAMSHARENAME: MSSQLSERVER
    FTSVCACCOUNT: NT AUTHORITY\LOCAL SERVICE
    FTSVCPASSWORD: *****
    HELP: 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: DefaultNativeMode
    RSSVCACCOUNT: NT AUTHORITY\SYSTEM
    RSSVCPASSWORD: *****
    RSSVCSTARTUPTYPE: Automatic
    SAPWD: *****
    SECURITYMODE: <empty>
    SQLBACKUPDIR: <empty>
    SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
    SQLSVCACCOUNT: NT AUTHORITY\SYSTEM
    SQLSVCPASSWORD: *****
    SQLSVCSTARTUPTYPE: Automatic
    SQLSYSADMINACCOUNTS: PC\computername
    SQLTEMPDBDIR: <empty>
    SQLTEMPDBLOGDIR: <empty>
    SQLUSERDBDIR: <empty>
    SQLUSERDBLOGDIR: <empty>
    SQMREPORTING: False
    TCPENABLED: 0
    UIMODE: Normal
    X86: False
    Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20140423_234604\ConfigurationFile.ini
    Detailed results:
    Feature: Database Engine Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: SQL Server Replication
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Full-Text Search
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Analysis Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Reporting Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Integration Services
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Client Tools Connectivity
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Management Tools - Complete
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Management Tools - Basic
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Client Tools SDK
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Client Tools Backwards Compatibility
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Business Intelligence Development Studio
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: SQL Server Books Online
    Status: Failed: see logs for details
    MSI status: Passed
    Configuration status: Passed
    Feature: Microsoft Sync Framework
    Status: Passed
    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\20140423_234604\SystemConfigurationCheck_Report.htm
    I tried installing as adminstrator and in compatability mode with Windows 7/Vista but that didn't work. Trying to install from the dvd or from the extracted files in my drive made no difference.
    I am now wondering if there is a download link for SQL Server 2008 R2 Developer edition with SP2 included (i.e. not just SP2 but the whole application (5GB+) otherwise I am not sure how to install this.

    Hello,
    1. Please refer to solution provided in below thread
    http://social.msdn.microsoft.com/Forums/sqlserver/en-US/61d56f64-2575-4a58-9503-84579476afaf/sql-server-2008-setup-error-attempted-to-perform-an-unauthorized-operation?forum=sqlsetupandupgrade
    2. Make sure you stop antivirus services during running the setup.Make sure you Right click on setup.exe file and select run as administrator.
    If above does not works include below as well
    3. Please verify WMI service is started.
    If WMI is started, consider to repair WMI.
    http://windowsxp.mvps.org/repairwmi.htm
    Reference
    Link
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • Problem with Mac OS X Lion reinstall - Cannot install on server volume

    Hi
    I have a MacbookPro 2011 that has been upgraded to Lion from Snow Leopard. I can log on and use the computer but I want to reinstall Lion and make a clean start. I have created a rcovery partition on an external drive and booted to this partition using the option command when re-booting. The Lion install process goes well until the screen which asks you to select the disk where you want to install Mac OS X Lion. The Macintosh HD drive is there, but I cannot select it as I get the following message with it:
    You cannot install Mac OS X on a server volume. You need to use disk utility to erase this volume before you can continue to install Mac OS X.
    I have no idea why the install is seeing my hard drive as a server volume. I just want to install OS X Lion, preferably using the archive and install option, on a standard MacbookPro. If I go ahead and erase the HD  will I still be able to install Lion? How will Apple know that I have already paid for the Lion upgrade if the main HD is erased? I have already created a clone of the existing HD so I have a backup of all files I need.

    Slight Update. I found a guy with my EXACT problem here.  https://discussions.apple.com/thread/4103108?start=0&tstart=0  Go to this discussion for further details.

  • Cannot install InDesign once removed from computer

    Hi Indesign users,
    Here are some tech details:
    1. MacMini 3.1, 6Gb RAM, OS X 10.9
    2. Adobe CC - InDesign, Photoshop, Illustrator
    3. InDesign worked without errors until this morning.
    4. No updates from yesterday (Saturday, Novermber 30) and today (December 1st)
    5. No fonts installed in between.
    What I did:
    This morning (December 1st) I tried to open an InDesign file to check if my collaborator finished the project. The file is hosted on Dropbox in a folder we are sharing. Therefore, I did what I am always doing with any of my IND files: double click on it to open it. It opened the file, showed me a white screen with all the InDesign tools and menus. And it stood that way for several minutes until I decide to force IND to quit.
    Then I tried again to open just the IND software. IND started to gave me an error like: IND is shuting down from a serious error.....
    I turned off the computer and started it again. InDesign opened the file properly, but I cannot do anything: no scrolling, no navigating between pages, nothing. It was frozen showing me a rainbow circle cursor for minutes. Therefore I decide, again, to force the software to close. I cannot open InDesign at all after that. The same message of a serious error is showed.
    I delete all kind of files based on things I read on the forum: from caches, workplaces etc. Nothing worked.
    As I had enough of those errors I was experiencing several months ago, I decide to completeely remove the InDesign hoping that I can reinstall it again, clean without errors.
    I delete all instances where InDesign might be present. At least I think that way.
    I shut down the computer and open it again, went to Creative Cloud Desktop Manager and when I tried to choose install InDesign, surprise. The manager is shopwing me that InDesign is Up to Date. I cannot install it.
    Please help.
    I did a complete instalation of my MAC a month ago just to get rid of those InDesign errors. I had enough of it. I do not care to reinstall my MAC again from zero just because that damn application.
    Warm regards,
    Sebastian
    P.S. I just read on an older post something. In that folder I am sharing there is a file having the extension: *.idlk That's why I cannot open the InDesign file? What to do in the future when I see files like that? Anyway, that is now unimportant since it will not save me from missing installing option for InDesign.
    Message was edited by: sebdea

    Hi Peter,
    I finally manage to make a clean install of InDesign. I remove it using the uninstall option then I reboot computer entered to creative cloud desktop application and I installed InDesign. Now it is working without hassle.
    Thank you very much for your support and for making time to read and answer. Much appreciate it.
    Warm regards,
    Sebastian

  • Cannot install Indesign CS2

    I have Indesign CS2, and learned that I cannot install it from my CD's anymore, because the activation disk doesn't work anymore.
    I tried to download the version that's available on adobe.com, I follow the guidelines, but something is not going right. It took 5 hours to download over 700 MB. And trying to open this huge file, there is no installing happening. My computer is Dell DM061, Processor Intel (R) Core (TM) 2CPU, 2GB RAM and running Windows Vista.
    Is the problem with my pc, or is it anything else?

    you should have a ~740mb file.  do you?
    if so, right click > click 'run as administrator'.

  • Ucs blade iscsi boot cannot install windows server

    Hi all,
    i have some problem when i try to install windows server 2008 in nexenta storage using iSCSI via ucs b-series, but its working fine when i install ESXi 5.5. i cannot find drive on windows server installation, and in ESXi i can see all LUN what im create before in nexenta storage and working when i install it.
    this vnic iSCSI Configuration:
    vnic_id: 13
              link_state: Up
           Initiator Cfg:
         initiator_state: ISCSI_INITIATOR_READY
    initiator_error_code: ISCSI_BOOT_NIC_NO_ERROR
                    vlan: 0
             dhcp status: false
                     IQN: test:iqn.2014-11.com.:8
                 IP Addr: 192.168.1.59
             Subnet Mask: 255.255.255.0
                 Gateway: 192.168.1.5
              Target Cfg:
              Target Idx: 0
                   State: ISCSI_TARGET_READY
              Prev State: ISCSI_TARGET_DISABLED
            Target Error: ISCSI_TARGET_NO_ERROR
                     IQN: iqn.2010-08.org.illumos:02:windowsboot
                 IP Addr: 192.168.1.49
                    Port: 3260
                Boot Lun: 6
              Ping Stats: Success (986.646ms)
            Session Info:
              session_id: 0
             host_number: 0
              bus_number: 0
               target_id: 0
    does anyone can help me to solve this issue?
    thanks in advance - fadli

    enic / fnic driver have to be installed; they are not part of any Windows OS.
    they can be found in
    Downloads Home
    Products
    Servers - Unified Computing
    UCS B-Series Blade Server Software
    Unified Computing System (UCS) Drivers-2.2(3)
    ISO image of UCS-related drivers 
    ucs-bxxx-drivers.2.2.3.iso
    depending on the UCS version.

Maybe you are looking for

  • Schedule line item link to delivery qty

    dear all, I used the function module RV_SCHEDULE_CHECK_DELIVERIES to find for a sales order all the shedule lines with the delivery qties. I faced to a problem to link schedule and delivery for this case : schedule item _______date ____________order.

  • IPhone 4 reception

    Hi, I've got an iPhone 4S and not had a problem with it in the 15 months since I've had it. However, on Saturday my reception dropped off completely but I could still receive wireless and 3G. After a few attempts to reboot (power&menu button) it woul

  • SQL Cluster with FQDN only (no instance names)

    Is it possible to setup a SQL failover cluster with multiple instances but basically be named the "default instance". Right now I have three instances: AAA, BBB, and CCC. With failover clusters you associate each SQL instance with its own Drive, its

  • CC 5.2 and JDE

    Ladies and Gentlemen: I would like a swag of how we could analyze the JDE side with CC 5.2 (cross system Analysis) Is this even possible 5.2 or how about with 5.3? Regards, Greg Edited by: Gregory Cook on Nov 17, 2008 5:46 PM

  • VI to read CPU and Memory usage on XP machines

    Need a VI to read CPU and Memory usage on an XP machine.