Precalculation server on virtual windows server

Hi Friends,
Is it possible to use virtual windows server for workbook precalculation. If possible how we can configure precalculation server in it?
Thanks & Regards
Prasanth

Friends,
Kindly answer to my question.
Regards
Prasanth

Similar Messages

Install Precalculation server on Virtual Windows system

Hi Friends,
Is it possible to install Precalculation server on Virtual windows system?
Thanks & Regards
Prasanth

Hi,
Can anybody please reply to my thread.
Regards
Prasanth

Need help installing sql server 2012 on windows server 2012 core

Hi Guys
I am having trouble installing sql server 2012 on windows server 2012 core. I am doing this on VM and my VM is not connected to internet.
This setup is part of preparing lab for sql serve exam 70-462. I would really appreciate your help.
I am including the links to the log files that were generated after installation. There are following 2 files
Component Update and
Detail_Global_Rules
Thanks

Hi
iworkonline,
Regarding to your original question, you can work around it according to Prashanth’s post or unclick the “Include SQL Server Product Updates" checkbox when installing SQL Server on your VM.
Regarding to your second question, I make a test using TechNet Virtual Lab and everything works as expected . Below are my steps.
1. Choose Web client after laughing the Lab.
2. Choose SQLONE machine and “OPEN CHARMS” as follows, then search SQL Server Management Studio, use it to connect to the default instance (which has been installed in the lab).
From your description, you get error message “Device not ready”. Could you please post more details? Are you installing SQL Server 2012 on the TechNet Virtual Lab?
Thanks,
Lydia Zhang
If you have any feedback on our support, please click
here.
Lydia Zhang
TechNet Community Support

Set up Search Service App For SharePoint server 2013 on Windows server 2012 R2 not working

Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM was set up to access
the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate to search service app
admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is in
a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean
isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message:
Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2    at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem with Search
Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.    This seems also to be a SP set up issue.
Thanks a lot.

Using new Search Service App wizard to create SSA is always a success. I could delete existing SSA and recreate it and no problem. It says successful but when I open Search Admin page from CA, it gives me errors as mentioned.
Now I used the following PS script for creating SSA from Max Mercher, but it stays at the last setps in following script:
Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
$IndexLocation = "C:\Search" #Location must be empty, will be deleted during the process!
$SearchAppPoolName = "SSAPool"
$SearchAppPoolAccountName = "mydomain\admin"
$SearchServiceName = "SSA"
$SearchServiceProxyName = "SSA Proxy"
$DatabaseServer = "W12R2DC1"
$DatabaseName = "SSA"
$spAppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
if (!$spAppPool)
$spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
$ServiceApplication = Get-SPEnterpriseSearchServiceApplication -Identity $SearchServiceName -ErrorAction SilentlyContinue
if (!$ServiceApplication)
# process stays at the following step forever, already one hour now.
$ServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseServer $DatabaseServer -DatabaseName $DatabaseName
Account mydomain\admin is an farm managed account, domain admin account, in WG_ADMIN role, It is in all SQL server roles and is DBO. I see search DBs are already on SQL server. From Event viewer, I got following errors in sequence:
(1) Crawler:Content Plugin under source Crawler:Content Plugin
Content Plugin can not be initialized - list of CSS addresses is not set.
(2) Warning for SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(3) Error for SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application 'cbc5a055-996b-44a7-9cbc-404322f9cfdf'
(4) Error for SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
(5) Error Shared Services for SharePoint Server Search
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
   at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
   at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob
Above errors keep being generated. Last step for SSA creation stay there forever. Any clue what is really going on? Thanks.

Project Server 2013 on Windows Server 2012 R2

Can we install Project Server 2013 on Windows Server 2012 R2? Is it supported? I searched a bit but couldn't find any concrete information if it is supported or not.

From the article:
http://blogs.technet.com/b/office_sustained_engineering/archive/2014/03/03/announcing-availability-of-slipstreamed-office-2013-and-sharepoint-server-2013-with-sp1.aspx
Today, aligned with the SharePoint Conference, we’re announcing availability
of a slipstreamed SharePoint Server 2013 with SP1. SharePoint administrators
will be able to use this updated installer to deploy on Windows Server 2012 R2.
which I got linked from the following
http://blogs.technet.com/b/projectsupport/archive/2014/02/25/project-2013-and-project-server-2013-service-pack-1.aspx

How do I run a non-server program on Windows Server 2008

I currently run a synchronization software application on my desktop in order to backup and synchronize over 600GB of data. I would like to install this on our server, which runs Windows Server 2008, but the software does not provide for installation
on this operating system. I continue to receive a message stating that the software may not run properly on Windows Server OS, but it does not allow me to bypass this message. Is there any way to create a partition or trick the software into thinking
that it is running on a different operating system or do I have to abandon Server 2008 and install a basic home operating system in order to run this software? Any help would be tremendously appreciated.
Thanks!

Hi,
According to your description, my understanding is that you want to install an software which is not supported by Windows Server.
Try to install this software in other compatibility mode:
1. Right-click the installation program and select properties.
2. Select Compatibility tab, select the checkbox Run this program in compatibility mode for.
3. try to use different OS to install this program.
Besides, you may right-click the installation program and select Run as administrator.
Above are my personal suggestion and just for your reference. If the problem still exit, I suggest you to connect the software‘s support/form for better help.
If you want to backup date, I suggest you to use Windows Server Backup, you may reference the link below for detailed information:
http://technet.microsoft.com/en-us/library/cc770757.aspx
Best Regards,
Eve Wang

Window SBS server 2008 and window server 2008 R2 on the same domain

Hi all,
I am a person only work for linux system. Recently i work for my company that using microsoft technologie. So i have a lot of trouble. Could you please help me and below are my big troble that i have met:
In my system, i have the first window SBS server 2008 run on our domain. However my organization growth up and we have more than 150 users and mailbox of exchange server 2007. So i do not want to use my sbs server 2008 anymore.
I am going to install a window server 2008 R2 64 bit and join it into the same domain with sbs server 2008. It will be replicate the username, dns, OU and group policy...After that i will tranfer FSMO role to new server and i will demote then remove the
sbs server.
My boss say that i should not use this solution because window server sbs can not run with any other kinds of window server 2008 (R2, standard, enterprise...) and it will automatically shutdown the main server after a couple of days.
Someone have experience can help me. I am so confuse now

Maybe this will also help to better understand the steps involved:
Transition from Small Business Server to Standard Windows Server
http://blogs.technet.com/b/infratalks/archive/2012/09/07/transition-from-small-business-server-to-standard-windows-server.aspx
Migrating away from SBS 2011
http://social.technet.microsoft.com/Forums/en-US/07c58cc4-7d6d-419a-b1a0-439c2cc0c48d/migrating-away-from-sbs-2011?forum=smallbusinessserver
Migrating from SBS 2008 to Windows Server 2012 R2 (NOT Essentials and with NO Exchange)
http://social.technet.microsoft.com/Forums/en-US/1276d2d3-a8f2-4786-82f3-4308a2affb11/migrating-from-sbs-2008-to-windows-server-2012-r2-not-essentials-and-with-no-exchange?forum=smallbusinessserver
And remember, as long as you don't move the PDC to one of the new DCs, you can leave the SBS 2008 up indefinitely. But I would remove Exchange 2007 off it right away once I've migrated the mailboxes and public folders, otherwise
you will get yourself into an Exchange coexistence scenario which is much more complex to configure and support because of the CAS differences, changing the URLs on the old one to "legacy.domain.com," getting a new UC/SAN cert with the correct
names on it, and more. Believe me, you really don't want to coexist them. The only time I've coexisted Exchange versions is during large migrations, such as 500 or more. Otherwise, I just migrate the mailboxes over a weekend and get it done with.
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Connect SQL Server 2012 from Windows Server 2003 with native client 9.0

Hi,
I currently have a setup where ETL tool Ab Intio, running on a Linux server, connects to the SQL Server 2005 through a passthrough Wintel server with Windows Server 2003 OS using SQL server native client 9.0
Now I have the requirement to upgrade the SQL server from 2005 to 2012.
My question is, will it be possible to connect to SQL server 2012 through Windows Server 2003 with native client 9.0?
As per the specs, I need native client 11.0+ to fully support SQL Server 2012, but then, as per specs, native client 11.0 doesnot run on Windows server 2003. OS upgradation is currently not on the cards.
So will it be possible to the run the basic queries we use currently, if we can connect SQL server 2012 through Windows Server 2003 with native client 9.0/10.0, without updgrading the OS of the Wintel server?
Thanking you in advance!

Hi Soumya,
Yes, you can use the SQL Server Native Client shipped with SQL Server 2005 to connect to a SQL Server 2012 instance, and there is no need to upgrade the operating system.
Regards,
Mike Yin
TechNet Community Support

How to enable high availability on SQL Server 2005 with Windows Server 2008 Enterprise R2

Dear Folks,
I would like to ask you about this thing. I'm working for IT department for bank in Myanmar. Our bank have up to 96 branches across all of Myanmar including H.O. We are using Microsoft SQL Server 2005 with Windows Server 2008 for our banking
information system. My main problem is having to backup and restore the database backup files every time the servers in branches goes down for whatever reasons. I want to deploy this feature of high availability and failover cluster using Windows Server 2008
and SQL Server 2005. Our branches have 2 Servers. One is for Primary and other is for Backup. What I want to do is that, I want to change Backup Server to Primary Server whenever the Primary Server goes down for whatever reasons. All the working data and databases
from Primary will immediately replicated into Backup Server along with all the IP information of Primary Server. Please give me step by step guide for this process.

Try below
http://blogs.msdn.com/b/cindygross/archive/2009/10/23/checklist-for-installing-sql-server-2005-as-a-clustered-instance.aspx
I will recommend you to upgrade SQL server to newer version for support as well as flexibility.
Regards,
Vishal Patel
Blog: http://vspatel.co.uk
Site: http://lehrity.com

Migration of Windows Small Business Server 2003 to Windows Server 2012 Essentials

Hi,
I am trying to migrate Windows Small Business Server 2003 to Windows Server 2012 Essentials by following the steps given in the link below:
http://technet.microsoft.com/en-us/library/jj200112.aspx
I have looked at other threads on the forum but none of them have been too helpful.
The issue: When
I run the Migration Preparation Tool on the Source Server, it runs successfully and does not report any errors. However, when I try installing Windows Server 2012 Essentials on the Destination Server, it displays an error that says 'Source
Server not prepared for migration: After you run the Migration Preparation Tool successfully on your source Server, click retry'.
The Source Server has 2 network adapters-one for the local network and the other for connection to the internet and the router is set as the default gateway this adapter.
Since it is mentioned in the documentation - 'configure your Source Server to use one network adapter', I'm wondering if this is the issue and I need to make changes in this configuration?
On running the Microsoft IT Environment Health Scanner tool it
reported an error - 'DNS Server listening on multiple addresses' and a warning ‘Domain Controller listening on multiple addresses’. Both point to the same solution KB 272294 (http://support.microsoft.com/kb/272294).
But it did not remove the errors.
Other steps performed:
As per the steps, I performed a backup, installed recent service packs and synchronized the source server time with external source.
On running the Best Practices Analyser. It shows 3 warnings.
- The threshold for the Allocated Memory alert is set to the default value. However the server has more than 2 GB of RAM installed.
- Microsoft Outlook Client not installed" Text="Microsoft Outlook Client is not installed in the ClientApps folder. You must run Windows SBS integrated setup.
- The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000. The MSFW instance should use the latest available service pack for Microsoft SQL Server 2000.
I also ran the Ran netdiag.exe, dcdiag.exe commands
and no failures were reported.
The Event Viewer does not show any errors.
Not sure to what extent these warnings would affect the migration.
Any help would be appreciated. Thanks!

The SBS2003 needs to use one NIC only so you'll need to change that before starting. If it is the premium version and has ISA server installed, that will need to be removed first. See:
http://blogs.technet.com/b/sbs/archive/2011/07/01/sbs-2011-standard-migrations-keys-to-success.aspx
-- Al

Not able to install Exchange Server 2013 on Windows Server 2012

I got an error while installing exchange server 2013 on windows server 2012 : "The registry key "SOFTWARE\Microsoft\Exchange Server\v15\Pickup" does not exist under "HKEY_LOCAL_MACHINE " any related solutions highly appreciated
thanks :

Hello,
Come back and mark the replies as answers if they help and unmark them if they provide no help.
I'm marking the reply as answer as there has been no update for a couple of days.
If you come back to find it doesn't work for you, please reply to us and unmark the answer.
Cara Chen
TechNet Community Support

WSUS server role on Windows Server 2012 R2 - Supported SQL Configurations

According to
this page the supported SQL configurations for WSUS on Windows Server 2012/2012 R2 stop at SQL Server 2012 SP1, but there is no mention of SQL Server 2012 SP2 being supported.
However, both the SCCM 2012 R2
supported configuration page and this announcement state that SQL Server 2012 SP2 is fully supported on SCCM 2012 R2 with no
known limitations. Bearing in mind a big part of SCCM is to perform software updates which in turn requires WSUS to be installed...
... Is SQL Server 2012 SP2 supported on WSUS 4.0 (aka WSUS server role on Windows Server 2012 R2)?

The only thing that mattered for the versions mentioned on TechNet probably is the date the articles are published. I'm no Microsoft employee so I cannot guarantee you support even if I trace back some Microsoft article that explains the lifecycle of MS
products and support.
Fact is that MDT uses a database, SQL is a database server. SQL server has all kinds of compatibility modes to support databases dating multiple versions back.
Another fact is that a Service pack is an
update to the software (be it a large one) Microsoft will not break compatibility with their own products (and may others that relay on SQL server) by an update.
And a last fact is that in general, updates are required when you need support. After all, updates fix issues, and engineers generally don't like ghosthunting a bug that has already been patched.
MCP/MCSA/MCTS/MCITP

Backed up files partially disappear after restore (Windows Server 2008 R2 - Windows Server Backup)

Dear all,
I am experiencing a problem with "Windows Server 2008 R2", using Windows Server Backup.
Here's my setup:
Server: RAID 5 Disk setup
Backup:
By using Windows Server Backup (within Windows Server 2008 R2), C: and D: were fully backed up, with "System State" and "Baremetal Recovery" options selected. Backup went okay without any errors.
Restore:
By using Windows Recovery Environment (booted from Windows Server DVD), C: and D: were fully restored to the original partitions with "System Recovery" option found within Windows RE (without re-formatting partitions during restore). Restore
went OK without any errors. Rebooted, and system has been running fine.
Problem:
After the restore, the system itself seems running OK; no BSOD, no crash, no visible errors.
However, our client insisted some files (around 6 to 7) which are related to the propriety software has "disappeared" right after System Recovery.
Question:
Since Windows Server Backup is using "Volume Shadow Copy" technology which enables "live backup" of the running system, is it possible that some files will disappear (=restore error) after
System Recovery?
I cannot really find any errors or warnings related to Windows Server Backup in the event log, through. No Windows-backup errors. No VSS errors, too.
Do anybody have experienced this kind of problem in the past? Any suggestion will be greatly appreciated.

Thank you for your reply, Ms. Mandy.
To make things clear, let me explain to you briefly:
1. The "missing data" was backed up with "full system backup".
2. After a system restore from the above backup image, as you mentioned, partitions has been overwritten with the partions' backup data in the Backup Data Set taken by Windows Server Backup. No error with backup. No error after restore, and reboot - system
has been running fine.
3. Although there was a report that the affected files(about 7 java exectables) were missing after the above restore operation, other aspect of system was running fine at the time of the report.
4. I have checked the original backup data set - and voila, there ARE files which seems to gone after restore.
5. When I used Windows Server Backup "on" Windows Server 2008 R2 normal environment (= NOT Recovery environment from DVD) and selectd ONLY these affected files to restore, these files could be RESTORED successfully, without any errors. SO... data
was property backed up.
> The recovery will overwrite the partitions so files created after the backup point will be missing.
I understand, and this is not the case this time, because the affected files are already present in the backup data set (= I have mounted the backup data as VHD, and I could clearly see them present in the mounted VHD file)
Plus, these files are completely restoreable via "selective file restore" in Windows Server Backup.
Things I want to know/confirm:
> The recovery will overwrite the partitions
If I understand this correctly, in case that the files in question are already present in the backup data set, these files SHOULD be restored after full system restore, right? (If these files could not be restored, Windows Server Backup SHOULD show some errors.)
What do you think, Ms. Mandy? :)
Jo

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

please post you question on failover clusters in the cluster forum. THey will explain how this works and point you at scipts.
You should also look in the Gallery for cluster management scripts.
¯\_(ツ)_/¯

How to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster) with scrpiting

I have a scenario with the three nodes with server 2012 standard, each running an instance of SQL Server 2012 enterprise, participate in a
single Windows Server Failover Cluster (WSFC) that spans two data centers.
If the nodes in the primary data center are unavailable due to data center outage. Then how I can able to access node in the WSFC (Windows Server Failover Cluster) in the secondary disaster recovery data center automatically with some script.
I want to write script that can be able to check primary data center by pinging some IP after every 5 or 10 minutes.
If that IP is unable to respond then script can be able to Perform Forced Manual Failover of Availability Group (SQL Server) and WSFC (Windows Server Failover Cluster)
Can you please guide me for script writing for automatic failover in case of primary datacenter outage?

You are trying to implement manually what should be happening automatically in the cluster. If the primary SQL Server becomes unavailable in the data center, it should fail over to the secondary SQL Server automatically. Is that not working?
You also might want to run this configuration by some SQL experts. I am not a SQL expert, but if you have both hosts in the data center in a cluster, there is no need for replication between those two nodes as they would be accessing
the database from some form of shared storage. Then it looks like you are trying to implement Always On to the DR site. I'm not sure you can mix both types of failover in a single configuration.
FYI, it would make more sense to establish a file share witness in your DR site instead of placing a third node in the data center for Node Majority quorum.
. : | : . : | : . tim

Precalculation server on virtual windows server

Similar Messages

Maybe you are looking for