Xcelsius 2008 cannot install
Hi all,
A customer cannot install Xcelsius 2008 on XP Home 2002 with SP2, with Office 2003 installed. There error message are "Office XP application : Excel, Word, Outlook or Powerpoint must be pre-installed. Higher versions work fine". Anyone encounter this before?
Regards,
Derek
Per the supported platforms documentation (platforms.txt located in the installation files or media) the following is supported:
Supported Operating Systems
============================
Windows XP SP1 Professional
Windows XP SP2 Professional
Windows Server 2003 Enterprise Edition
Windows Server 2003 Standard Edition
Windows Server 2003 SP1 Enterprise Edition
Windows Server 2003 SP1 Standard Edition
Windows Vista
Windows Vista SP1
Windows Vista 64-bit
Other Tools
=============
Office (Excel, PowerPoint, Outlook, Word)
Windows Office 2003
Windows Office 2003 SP1
Windows Office 2003 SP2
Windows Office XP SP3
Windows Office 2007
Unfortunately, your customer's XP Home version is not a supported operating system.
Similar Messages
-
Hi Forum,
I am trying to install Xcelsius 2008 SP3...
I uninstalled Xcelsius 2008. Succesfully
I downloaded Xcelsius 2008 SP3, and when i enter the Product Key i am getting a message saying that the Key is Invalid....
This is the same key that i used to install it the first time....
Can someone tell me what am i doing wrong.... maybe the installation requieres for me to do it via CD instead of a download?
The reason i am saying that is because the product key starts with CDXXX. Or am i using the wrong key?
Regards,
Manuel RomanMake sure Xcelsius 2008 is fully uninstalled, reboot and install Xcelsius 2008 SP3.
The Xcelsius SP3 is a Cumulative Service Pack not an incremental. That means, you need to uninstall the existing version of Xcelsius on your machine and then run the executable that you have downloaded.
While installing please keep the Key code ready. The installation will ask you to enter at at the beginning. This is the same key code that you might have received from SAP when you purchased the license.
Make sure you type it in exactly in all caps and with dashes. -
Xcelsius 2008 - Known Issues (Installation)
AA: Area Affected
PD: Problem Description
WA: WorkAround
AA: Installing QAAWS from BOE Client
PD: The Query As A Web Service (QAAWS) application has been combined with the BOE XI 3 BusinessObjects Client application. It was previously a separate application.
This means that to use BOE XI 3 QAAWS with Xcelsius 2008, you must download the BOE XI 3 BusinessObject Client from the Business Objects Support site and install it on your client machine.
WA: To install QAAWS download the BOE XI 3 BusinessObjects Client. You may or may not have access to this download based on the type of licensing agreement you have with Business Objects. Note that the BOE XI 3 BusinessObject client is about 600MB in size.
AA: Installing Xcelsius 2008 when a higher version of the Adobe Flash Player exists
PD: The Xcelsius 2008 installer will install a version of the Adobe Flash Player. If you have previously installed a higher version of the Flash player, you will get a warning message from the Xcelsius 2008 installer.
WA: You can ignore this warning message. Your newer version of the Flash Player will not be changed.
AA: Installing Xcelsius 2008 with other older BOE products.
PD: After installing Xcelsius 2008 on a machine, some other older BOE products on the same machine stop working (eg. WebI Report Server, BOE XIR2)
WA: Many BOE products share the same installer, as a result installing Xcelsius 2008 on the same machine other older products changes the default install folder to the newer BOE folder. For example with BOE XIR2 it changes the default BOE install directory to change to BOE XI 3 folder.
C:\program files\business objects\businessobjects enterprise 11.5\" is changed to
C:\program files\business objects\businessobjects enterprise 12\"
The workaround is to manually edit the registry and change the key folder name back to its previous name.
Use regedit to view the folder name in the key "HKEY_LOCAL_MACHINE/Software/Business Objects/Enterprise/InstallRoot/Path".
Double-click on path and change the Value data. In most cases the folder name is C:\program files\business objects\businessobjects enterprise 11.5\
Note: please back up your registry before making any changes.
AA: Uninstalling Live Office XI 3 from a machine with Xcelsius 2008
PD: If you uninstall Live Office XI3 on a machine with Xcelsius 2008 also installed, the Xcelsius Keycode Expiry dialog box (License manager) pops up asking for the Xcelsius Keycode.
WA: The Xcelsius keycode must be entered again to re-enable Xcelsius.
AA: Installing Xcelsius with Office XP
PD: Currently installing Xcelsius 2008 with Office XP is not supported due to a bug. Use Office 2003 or Office 2007 instead. If Office XP must be used see the workaround.
WA: As a workaround to the issue of Xcelsius 2008 not installing with Office XP, users can manually add a registry key to enable installation. Please make a backup copy of the registry before making any changes.
1. Go to Start > Run. Start the registry editor by entering 'regedit'.
2. Select the folder HKEY_LOCAL_MACHINE and navigate to \Software\Microsoft\Office\
3. Create an 11.0 folder, if it doesn't exist, by selecting Edit > New > Key from the menu.
4. Create a subfolder called PowerPoint
5. Create a subfolder under PowerPoint called InstallRoot
You should now have the folder structure listed below:
HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\PowerPoint\InstallRoot
6. From the InstallRoot folder create a string value called "Path" by selecting Edit > New > String Value
7. Select the newly created Path value and select Edit > Modify.
8. Under the Value Data field enter "C:\Program Files\Microsoft Office\Office11\"
9. Click OK.
10. Exit the registry editor.
11. Reboot your machine.
You should now be able to install Xcelsius 2008.
AA: Creating a Web Part for SharePoint Portal Server 2007
PD: The current Xcelsius Web Part installer Setup.exe does not work with SharePoint Portal Server 2007.
Note: Sharepoint Portal 2003 is supported.
WA: You can manually install the web part to use with Microsoft SharePoint Portal Server 2007. Microsoft does not provide a mechanism to build a Web Part installer for SharePoint 2007. For instruction on manual installation see the Xcelsius Support website. (see follow up post below)The current Xcelsius Web Part installer Setup.exe does not work with SharePoint 2007 (Windows SharePoint Services 3.0). Here is the workaround to install Web Part in SharePoint 2007 manually.
The easiest way to install a web part in SharePoint is to add the web part assemblies to Global Assembly Cache. To do so:
1. Download and unzip the attached Xwp.zip. Drag Xwp.dll and ICSharpCode.SharpZipLib.dll into C:\WINDOWS\assembly folder on the machine running SharePoint 2007.
2. Open web.config file located in the root of a Windows SharePoint Service 3.0 Web Application directory with Notepad. Normally, the physical location of the default WSS 3.0 Web Application root is C:\Inetpub\wwwroot\wss\VirtualDirectories\80.
[Click here for more information on how to Find the Web Application Root|http://msdn2.microsoft.com/en-us/library/ms474356.aspx].
3. Insert the following <SafeControl> tag between <SafeControls> and </SafeControls>.
<SafeControl Assembly="Xwp, Version=1.0.0.0, Culture=neutral, PublicKeyToken=7e58495f1a9ea430"
Namespace="CrystalXcelsius.SharePoint.WebParts" TypeName="*" Safe="True" />
4. In SharePoint Portal Site Home page, from Site Actions drop-down menu, go to Site Settings->Modify All Site Settings. Click Web Parts under Galleries to open Web Part Gallery Page. Click New to open New Web Parts page. Check CrystalXcelsius.SharePoint.WebParts.Container checkbox and click Populate Gallery. Once it is populated, you will be able to add Container web part to your web part page in SharePoint 2007. -
Xcelsius 2008 won't accept keycode
I just upgrade to Xcelsius SP1 FP1. Everything seemed to work great and I have the new version. However, everytime I open Xcelsius it asks for my keycode. I enter the correct keycode and the program opens and appears to be active. However, I repeat this the next time I open Xcelsius.
I have tried the instructions for "set_registry_permissions" with no luck.
Any help would be appreciated.
Thanks!
-GregPost Author: abrat
CA Forum: Xcelsius and Live Office
As a workaround to the issue of Xcelsius
2008 not installing with Office XP, users can manually add a registry key to
enable installation. Please make a backup copy of the registry before making any
changes.
Manual Change
1. Go to Start > Run. Start the registry editor by
entering 'regedit'.
2. Select the folder HKEY_LOCAL_MACHINE and navigate to
\Software\Microsoft\Office\
3. Create an 11.0 folder, if it doesn't exist, by
selecting Edit > New > Key from the menu.
4. Create a subfolder called PowerPoint
5. Create a subfolder under PowerPoint called
InstallRoot
You should now have the folder structure listed
below:HKEY_LOCAL_MACHINE\Software\Microsoft\Office\11.0\PowerPoint\InstallRoot
6. From the InstallRoot folder create a string value
called "Path" by selecting Edit > New > String Value.
7. Select the newly created Path value and select Edit
> Modify.
8. Under the Value Data field enter "C:\Program
Files\Microsoft Office\Office11\"
9. Click OK.
10. Exit the registry editor.
11. Reboot your machine.
You should now be able to install
Xcelsius 2008.
Please note that although
all other Office XP applications will work, Xcelsius 2008 export to Word
produces a blank document. -
Error while installing Xcelsius 2008
Hi,
We are getting error while installing Xcelsius 2008 version 5.3.....
"The upgrade patch cannot be installed by windows installer service because the program to be upgraded may be missing, or the upgrade patch may update a different version of the program. Verify that the program to be upgraded exists on your computer and that you have the correct upgrade patch"
Kindly suggest how to install the Xcelsius latest verion.
With Regards,
PearlHi Pearl,
Sorry if you've already done this, but have you installed Xcelsius 2008 SP3 first? It sounds like you are trying to install a fix pack without first installing Xcelsius 2008.
The downloads are all available from the [downloads service market place|http://www.sdn.sap.com/irj/boc/] (as per the stickied thread)
If you choose Service Pack as the software type it will allow for download of the SP3 full install.
OR
Could it be this issue [Xcelsius FP3.5 error installing Excel2010; with solution from F. Kooij if you are referring to the latest fix pack 3.5 with Office 2010?
Regards,
Paul
Edited by: zygorf on May 24, 2011 12:53 PM -
Error to install Xcelsius 2008 on Windows vista. Error 1935.
I have a big problem, I need install Xcelsius 2008 on Windows vista, but when I install the software apper the nex message:
Error 1935 Error al instalar el ensamblado.
"Microsoft.VC80.ATL,type ="Win32",version= "8.0.50727.762",pubicKeyToken="1fc8b3b9a1e18e3b",processorArchitecture="x86"". Consulte Ayude y soporte tecnico para obtener mas informacion.From a brief Google search, I determined this error message is from Vista. It is not being produced by Xcelsius. You will need to do your own search and determine what is causing Vista to report this error. You can also try installing using instructions for Xcelsius installation on Vista posted elsewhere in these forums.
-
Hello -
I just installed a new M500 Crucial ssd in my late 2008 mbp - everything was working fine on old hard drive (running snow leopard) but was getting slow and wanted to upgrade - i lost my snow leopard disk when moving from hawaii so i found an iso online - using a flash drive i partitioned the disk and made the bootable image on flash drive - formatted as extended/journaled - switched out the hard drives - plugged in the flash drive - started the comp - held option - install begins to boot - choose language - all is fine - choose english - next step window pops up saying 'cannot install os on this computer' - click on utility but all options are greyed out - disk util is greyed out - only options it gives is to start from backup or restart - real confused here - all help appreciated - thanks in advance and happy new year!Snow Leopard comes in discs only. The USB drive may be a counterfeit and/or corrupt. There are two options for you:
Get replacement original OSX installation disks from Apple customer service. Have your MBP serial number ready and there is a charge.
Or two, purchase a Snow Leopard disk from the Apple online store:
http://store.apple.com/us/product/MC573Z/A/mac-os-x-106-snow-leopard
Ciao. -
'Error applying transforms' when trying to install Xcelsius 2008 fp3.2
Hello
I've just tried to install Xcelsius 2008 fp3.2 (I am currently on Xcelsius 2008 sp3). I did read the installation notes, and I wonder if the problem I had is related to the fact that I am not logged in as administrator (I'm on XP).
The package extracted and as the installer ran I got the message:
'Error applying transforms. Verify that the specified transform oaths are valid'.
Thanks
PhilHi Phil,
Can be...
To resolve this error, copy all files from the disc to a local computer location (for example, the desktop). Install Crystal Xcelsius from the setup.exe file at that location.
Hope this helps.
Kind Regards,
Marcio -
Xcelsius 2008 Engage Won't Install in Windows 7
The installation of Xcelsius 2008 Engage completes but the program cannot be used at all because the license key is stated to be missing or invalid.
This is a common problem on other systems but it can be worked around in various ways. However the workarounds fail in Windows 7.
The required registry entries that need to be edited are not present in Windows 7. Running as administrator does not solve the problem either.
It seems Xcelsius 2008 can only be used on Windows 7 by running under an XP virtual machine.
Does anyone have a way to get Xcelsius running natively on Windows 7?
My Windows 7 system is the 64-bit release candidate. Xcelsius 4.5 runs on this but only when run as administrator and in XP SP3 compatibility mode with desktop composition and visual themes disabled.Download the offline installer from http://helpx.adobe.com/content/help/en/flash-player/kb/installation-problems-flash-player- windows.html#main-pars_header and save it to disk, then close all browser windows and run the downloaded installer.
If you still have problems, please post the contents of the FlashInstall.log file in
C:\Windows\system32\Macromed\Flash
C:\Windows\syswow64\Macromed\Flash
[topic moved to Flash Player forum] -
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 -
Best Practice Re-install Process? (Xcelsius 2008 Engage)
The main impetus of this post is now to request a best practice reinstall process. E.g., what files/directories or registry keys to delete after uninstalling under Windows XP? Running Xcelsius 2008 5.1.1.0 Build 12,1,1,344 (Windows XP SP2)? I want to clean it up and reinstall completely, ideally without also reinstalling Office 2007.
Earlier today, I had loaded up an otherwise healthy project and all of a sudden my edits were not taking. I could perform the change in the Component Properties window but the change did not translate in the project display area.
I had closed and reopened this project several times, killed both "Xcelsius" and "EXCEL" processes, rebooted the machine a couple of times, all to no avail. I was totally stuck, it seems. Then, it randomly corrected itself after the Xth close/reboot/reload. I'm past the issue now it seems, but please consider this an official bug report. These issues are no longer a mere minor nuisance, and I am looking forward to a nice big update in the next Fix Pack release, which I assume is right around the corner (hint, hint).
Thanks.
Edited by: f l on Nov 17, 2008 9:20 PMf l,
I'm not sure deleting keys from the registry is ever a best practice, however Xcelsius has listings in:
HKEY_CURRENT_USER > Software > Business Objects > Xcelsius
HKEY_LOCAL_MACHINE > SOFTWARE > Business Objects > Suite 12.0 > Xcelsius
The current user folder holds temporary settings, such as how you've modified your interface.
The local machine folder holds more important information.
As always, it's recommended that you backup the registry and/or create a restore point before modifying or deleting any keys.
As for directories, the only directory Xcelsius uses is the one you install to. It also places some install logs in the temp directory, but they have no effect on the application. -
Can't uninstall XCelsius 2008 SP1, in order to install SP3.
Hello,
I'm attempting to uninstall XCelsius 2008 SP1 (FP3), in order to install SP3, as per the instructions. However I am running into the same error message that is found in this thread: [SP3 Wont install because I can't get current version off|SP3 Wont install because I can't get current version off].
I am receiving the same error code u201Ccanu2019t find Xcelsius.msiu201D and then u201CError 1706.u201D
I attempted to follow the instructions to edit the registry, but could not find the string "MediaPackage" anywhere, so I don't know what my next step should be. Can anyone help me out with this? Thanks!!
- GeorgeHi,
I had a similar problem and had no luck resolving it until I tried the MS installer fix utility.
http://download.microsoft.com/download/e/9/d/e9d80355-7ab4-45b8-80e8-983a48d5e1bd/msicuu2.exe
That worked for me.
Bill -
Can't Install Xcelsius 2008 with Office/Excel 2010 Beta on XP
I am running the latest beta version of Office 2010 and when I try to install Xcelsius 2008 i get an error and it aborts the install. Error says:
Office XP application: Excel, Word, Outlook or Powerpoint must be pre-installed. Higher versions work fine.
Am I missing something on why this wouldnt work?
Thanks,
TimHi Tim,
There is a work around for your problem, go to my blog: http://www.pieterverstraeten.com/blog/sap-bo-crystal-dashboard-design-2008-installation-cobmination-with-ms-office-2010-xcelsius-liveoffice/
Today I downloaded the new version of Xcelius, SAP BO Dashboards 4.0. This version will support MS Office 2010! This version will be available the 23th of February 2011.
I hope this will solve your problem.
Regards,
Pieter -
How to fresh install Xcelsius 2008 SP4 on Win7/Office2010
How do I do a fresh install of Xcelsius 2008 and get up to SP4 if I am unable to do an install of Xcelsius 2008 on Win7/Office2010 in the first place?
Hi Chris
You can install Xcelsius 2008 Service Pack 4 without having a previous version of Xcelsius 2008 installed because each Service Pack is a full install (or it can be used to upgrade from a previous Service Pack).
So download and install SP4 which supports Office 2010 (32-bit) and Windows 7.
Regards
Matt -
Cannot Install PB Runtime 12.0 or 12.5 on Windows 8 Server 2008 R2
Greetings All!!
I am trying to set up a new server for deployment and when I run either the PB Runtime for 12.0 or 12.5 I get an error stating (in general) module pbjvm120.dll failed to register.
I am also having this problem with another Windows 2008 Server install. I had to move on with the last one, but I need this one up and running now so I am asking for advice/help.
I attached a screenshot of the error.
Thanks all!!
Best,
PaulThanks Gentlmen!!
I don't know how the '8' in Windows 8 Server 2008 R2 got in there, but it is just Windows Server 2008 R2.
I copied msvcr71.dll , msvcp71.dll and atl71.dll to the c:\windows\system32 directory. Tried again and got the same error as shown in my screenshot. This 'is' a VM. I am logged into the machine as Administrator.
Chris, what do you mean by official MR?
I am creating the runtime files using the PB Runtime Packager.
Thank you!!
Paul
Maybe you are looking for
-
My Ipod Touch 3rd Gen will not update
I have a 3rd Gen Ipod Touch, and it states on the website that this supported to update to iOS 4.3 However, when I try to update, I get the same error message. "This version of the Ipod software (4.2.1) is the current version" anyone have any idea wh
-
Help with Informix and Weblogic
Listed below is what is specified in the properties file but I get an error from the Informix database like this: listener-thread: err = -951: oserr = 0: errstr = -p: Incorrect password or user -p is not known on the database server. -951 refers to
-
Visual Hub questions (related to Apple TV) and others
Hey guys, Just bought Visual Hub to convert my stuff. What do you recommend for the settings ? Right now this is what I use : (NOTE : I translated on the fly from french so maybe it's a bit different) -To : iTunes -Optimize for : Apple TV 5.1 -Qualit
-
Won't recognize Monitor through Monitor Share
If I plug my monitor directly into my G5, the G5 knows it's a Dell D1226H. BUT if I plug my monitor into a monitor share, the G5 tries to use some generic monitor extension, and the display is really hard to see.
-
Generating wsdl for the adapters in soa 11g
Hi, how can we generate a wsdl only for the adapter that we use in soa 11g?? for eg.. my scenario is frm the previous posts it was said that we need to generate the wsdl for the adapter and should import it in OSB for proxy services... (so this is in