CM 2012 SP1 equivalent of App-V Publishing Server

Good morning everyone.
I'm trying to virtualize Adobe Flash 10.3 for IE. That's beside the point but I wanted to mention my ultimate goal.
Sparing you all the App-V stuff I have to go through there's one obstacle that is hindering me at this point.
I've converted completely to CM 2012 SP1 for my App-V deployment functions but find myself needing to specify our main CM server as the "AppVPublishingServer". The ultimate goal here is to set the virtual app attribute of "IsPublishedGlobally"
to TRUE. This is normally done with a PoSH command "Set-AppVpublishingserver", manipulating the Global parameters.
Do any of you know how to configure this attrib through CM, or, how to declare the CM server as a Publishing Server (in App-V's eyes)?
Thanks very much.
IAmStrings

I am not sure about deployment, but I know for content the publishing server is the ConfigMgr cache. I know this was the case with 4.6, but not sure what has changed in 5.0.
We never had to specify the publishing server when we sequenced or deployed our packages with ConfigMgr.
Daniel Ratliff | http://www.PotentEngineer.com
This will depend how you publish the package (stream or download). If downloaded the package will reside in the cache but if streamed only the xml files will.
Ultimately the ConfigMgr client will handle and nothing will need to be specified.
Cheers
Paul | sccmentor.wordpress.com

Similar Messages

Issue with SCCM 2012 SP1 U5 upgrade and client published version

Recently we upgraded our SCCM server to SP1 U5, and our published and available client version is still at 5.00.7804.1000 instead of 5.00.7804.1600. We ran the hotfix to upgrade it and it looked like everything had went through. Does this not also
upgrade the client? It doesn't seem like you can run the hotfix again after you've already installed it once to repair either. Is there another way to update the published version inside the console? We have it as a package right now to deploy to all the systems
but I was hoping we could upgrade the internal one and let it run more automatically. Any advice would be greatly appreciated.

More info:
How to update ConfigMgr clients automatically… in SP1
http://configmgrblog.com/2012/12/03/how-to-update-configmgr-clients-automatically-in-sp1/
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place.

Windows Server 2012 and win 8 app on terminal server

On a windows 2012 server, is it possible to install a windows 8 app that can be accessed (via terminal services/remote desktop) by client computers running prior version of Windows, such as 7, Vista and maybe XP? (Obviously without the touch capability).
In other words, can a windows 8 app be accessed via terminal server by other versions of Windows or it must be only Windows 8?
Also, I read that the new RDC can also be downloaded from the Windows Store to a tablet, but what tablet? "Surface" , iPad, Android?
Thanks so much
CBJunior

Hi,
Windows app store is only available on the windows 8 platform.So it is not possible to install a windows 8 app that can be accessed (via terminal services/remote desktop) by client computers running prior version of Windows, such as 7, Vista
and maybe XP.
Also, I read that the new RDC can also be downloaded from the Windows Store to a tablet, but what tablet? "Surface" , iPad, Android?
It is available in the windows app store on Surface which is installed with windows 8 RT.
Regards,
Clarence
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedbackhere.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Declaring an SCCM 2012 SP1 server as the "Publishing Server" for App-V 5 SP2

Good morning everyone.
I'm trying to virtualize Adobe Flash 10.3 for IE. That's beside the point but I wanted to mention my ultimate goal.
Sparing you all the App-V stuff I have to go through there's one obstacle that is hindering me at this point.
I've converted completely to CM 2012 SP1 for my App-V deployment functions but find myself needing to specify our main CM server as the "AppVPublishingServer". The ultimate goal here is to set the virtual app attribute of "IsPublishedGlobally"
to TRUE. I need to refer to the Publishing Server's URL in order to use the PoSH command "Set-AppVpublishingserver" to manipulate the "Global" parameters.
Do any of you know how to configure this attrib through CM, or, how to declare the CM server as a Publishing Server (in App-V's eyes)?
Thanks very much.
IAmStrings

Hello,
If using SCCM and the App-V 5 integration, you can never configure a publishing server.
Read this whitepaper for the full-story;
http://blogs.technet.com/b/virtualvibes/archive/2013/04/22/sccm-2012-sp1-and-app-v-5-0-documentation.aspx
It contains step-by-step instructions on howto use the integration.
Nicke Källén | The Knack| Twitter:
@Znackattack

App-V 5 Virtual Environments in SCCM 2012 SP1

I am attempting to use SCCM 2012 SP1 to Deploy App-V v5 Applications. So far deploying applications to user groups (like I did with 4.6) seem to work well. The only issue that I am having is deploying Virtual Environments (the new way of
"dynamic sequencing). My problem is that on the client side, the App Connection Groups are not being populated. What can I do to fix this? The applications are deployed to a user group collection and not a machine collection. From
what I have found this is possible but it is not working for me. Anything to help is GREATLY appreciated!!
Brian

Since no one has answer this post, I recommend opening a support case with CSS as they can work with you to solve this problem.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

SCOM 2012 SP1 - PowerShell Script failed to run - 3 alerts appear after every reboot of the SCOM Server

Brand new SCOM 2012 SP1 install with Update Rollup 1 applied
Single server, local SQL install, SQL Server 2012 SP1
Hyper-V VM running on Server 2012. VM has 8GB Ram, single vCPU
Going through initial management pack importing and configuration, at this point I have the Windows Server 2012 and SQL 2012 MP's installed.
See screenshot
http://i.imgur.com/l0Molh1.png
I am getting the following alerts in my SCOM console and cannot find a resolution to fix the issue. I don't want to set an override, as an override will prevent the PowerShell alert in other instances, where I might want to receive an alert.
Looking at the alert description, it states "The Data Access service is either not running or not yet initialized"
The SCOM Console launches and responds fine, and I get no other errors. I check the Data Access service and it is online. I have left the system alone for a couple of hours and no other errors. I then closed those alerts and restarted the
server, and they came right back in, so I know that this is something that is happening at either server startup of during the start of the SCOM services.
Is it possible that SCOM is trying to execute these scripts and the Data Access service has not come online yet?
Has anyone else come across this before?

Please try the method in the following thread:
Note: As there is operations related to Registry, please perform a backup before doing this.
OpsMgr 2012 - Power Shell Script failed to run
http://social.technet.microsoft.com/Forums/de-DE/systemcenterde/thread/4be37f8d-1e7b-450c-8cb9-f1e95f3b2bd0/
Thanks.
Nicholas Li
TechNet Community Support

Upgrading DPM 2012 SP1 to DPM 2012 R2 fails (DPM Setup is unable to connect to the specific instance of SQL Server Reporting Service (ID: 33431)

The Background:
1. DPM 2012 SP1 was originally installed on a server with local SQL 2008 R2 instance (SQL was installed as part of DPM)
2. SQL database was upgraded to SQL 2012 SP1
Now I want to upgrade DPM 2012 SP1 CU3 to R2. It is throwing the following error. Any help would be appreciated.

This absolutely fixed my issue. I had upgraded my version of SQL and was then trying to upgrade DPM 2012 to 2012R2 and I could not figure out where the installation was querying old version of the reporting services.
DPM Log Before:
[6/4/2014 2:53:32 PM] Information : Query WMI provider for path of configuration file for SQL Server 2008 Reporting Services.
[6/4/2014 2:53:32 PM] Information : Querying WMI Namespace: \\DPMServer\root\Microsoft\SqlServer\ReportServer\RS_MSDPM2012\v10\admin for query: SELECT * FROM MSReportServer_ConfigurationSetting WHERE InstanceName='MSDPM2012'
[6/4/2014 2:53:32 PM] * Exception : => System.Management.ManagementException: Provider load failure
DPM Log After:
[6/4/2014 3:25:36 PM] Information : SQL Server 2008 R2 SP2 instance MSDPM2012 is not present on this system.
[6/4/2014 3:25:36 PM] Information : Query WMI provider for SQL Server 2008.
[6/4/2014 3:25:36 PM] Information : Querying WMI Namespace: \\DPMServer\root\Microsoft\SqlServer\ComputerManagement11 for query: Select * from SqlServiceAdvancedProperty where ServiceName='MSSQL$MSDPM2012' and PropertyName='Version'
[6/4/2014 3:25:36 PM] Information : SQL Server 2008 R2 SP2 instance MSDPM2012 is present on this system.
[6/4/2014 3:25:36 PM] Information : Inspect context initialized with
SQL Server namespace: \\{0}\root\Microsoft\SqlServer\ComputerManagement11
Reporting namespace: \\{0}\root\Microsoft\SqlServer\ReportServer\RS_{1}\v11\admin
SqlServerDetected: True
[6/4/2014 3:25:36 PM] Information : Check if SQL Server 2012 Service Pack 1 Tools is installed.
[6/4/2014 3:25:36 PM] Information : Inspect.CheckSqlServerTools : MsiQueryProductState returned : INSTALLSTATE_DEFAULT
[6/4/2014 3:25:36 PM] Information : **********************************************************************************
Thanks for This FIX!

Best practice - Heartbeat discovery and Clear Install Flag settings (SCCM client) - SCCM 2012 SP1 CU5

Dear All,
Is there any best practice to avoid having around 50 Clients, where the Client version number shows in the right side, but client doesn't show as installed, see attached screenshot.
SCCM version is 2012 SP1 CU5 (5.00.7804.1600), Server, Admin console have been upgraded, clients is being pushed to SP1 CU5.
Following settings is set:
Heartbeat Discovery every 2nd day
Clear Install Flag maintenance task is enabled - Client Rediscovery period is set to 21 days
Client Installation settings
Software Update-based client installation is not enabled
Automatic site-wide client push installation is enabled.
Any advise is appreciated

Hi,
I saw a similar case with yours. They clients were stuck in provisioning mode.
"we finally figured out that the clients were stuck in provisioning mode causing them to stop reporting. There are two registry entries we changed under [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec]:
ProvisioningMode=false
SystemTaskExcludes=*blank*
When the clients were affected, ProvisioningMode was set to true and SystemTaskExcludes had several entries listed. After correcting those through a GPO and restarting the SMSAgentHost service the clients started reporting again."
https://social.technet.microsoft.com/Forums/en-US/6d20b5df-9f4a-47cd-bdc3-2082c1faff58/some-clients-have-suddenly-stopped-reporting?forum=configmanagerdeployment
Best Regards,
Joyce
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]

SCCM 2012 SP1 - SUP Error

Hi guys,
i upgraded my SCCM 2012 test Environment to SP1. I have only one Primary Site Server which holds all Roles. Everything seems to work fine except the SUP Role. If i try to synchronize the latest Updates it says that it cannot find a WSUS Server
and i should check WCM.LOG.
Within WCM.LOG i can find the following Messages:
Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 08:56:44 3620 (0x0E24)
Trigger event array index 0 ended. SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:07:56 3620 (0x0E24)
SCF change notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Setting new configuration state to 1 (WSUS_CONFIG_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
Changes in active SUP list detected. New active SUP List is: SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:04 3620 (0x0E24)
SUP0: CM01.TEST.LOCAL, group = , nlb = SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Updating active SUP groups... SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Bad Configuration, SUPs present but no default SUP SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Default SUP not specified SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Setting new configuration state to 0 (WSUS_CONFIG_NONE) SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
Waiting for changes for 47 minutes SMS_WSUS_CONFIGURATION_MANAGER 09.01.2013 09:08:05 3620 (0x0E24)
So in General this tells me that it can find a SUP but this one is not specified as a DEFAULT SUP. How can i tell SCCM that this is my Default SUP? (I only have this one and it is configured to sync from Microsoft Update site). I have never seen
this before so i guess this is related to SP1?
PS: I also installed the 2 necessary WSUS Updates before i upgraded to SCCM SP1.
Thanks in lot in advance.
Stefan

None of your solutions apply to WSUS 4.0 on Server 2012
None of the specified patches applies or will run on a Windows 2012 Std server. They either report that WSUS 3 SP 2 isn't installed OR that the patch isn't applicable to the server version installed.
Here is a excerpt of MY WCM.LOG
I have a fully patched Windows 2012 Standard Server, Fully updated SCCM 2012 SP1 installed, and am connected to a fully patched SQL2012 Server on another fully patched Windows 2012 Std server.
Ports 8530 and 8531 designated on both the WSUS 4.0 Role and SCCM 2012 SP1 system (both are on same server)
SUP0: SCCM2012.xxdomainname.ORG, group = , nlb = ~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.496+420><thread=6052 (0x17A4)>
Updating active SUP groups...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.503+420><thread=6052 (0x17A4)>
Bad Configuration, SUPs present but no default SUP $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.510+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.525+420><thread=6052 (0x17A4)>
Setting new configuration state to 0 (WSUS_CONFIG_NONE)~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.535+420><thread=6052 (0x17A4)>
Waiting for changes for 11 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 10:54:14.543+420><thread=6052 (0x17A4)>
Wait timed out after 11 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:04:54.569+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.577+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.585+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 11:05:04.592+420><thread=6052 (0x17A4)>
Wait timed out after 60 minutes while waiting for at least one trigger event. $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:04:54.714+420><thread=6052 (0x17A4)>
Timed Out...~ $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.721+420><thread=6052 (0x17A4)>
Default SUP not specified $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.728+420><thread=6052 (0x17A4)>
Waiting for changes for 60 minutes $$<SMS_WSUS_CONFIGURATION_MANAGER><03-14-2014 12:05:04.734+420><thread=6052 (0x17A4)>
Randall

SCOM 2012 SP1 failed to send notifications by IM Channel

Hello, I have a problem with my SCOM 2012 SP1. When it tries to send notification by IM Channel I get the following alert in SCOM:
Notification subsystem failed to send notification using
device/server 'live.august.ru:5060' over 'sip' protocol to
'sip:[email protected]'.
Microsoft.Rtc.Signaling.OperationFailureException: The GetInbandDataAsyncResult
operation has failed with message: "The data session subscription to server
failed.". See the InnerException and FailureReason properties as well as the
logs for additional information. . Rule id:
Subscription077dc311_59c0_4ba5_a432_072b486cd287
At the same time the following event in the Application Event Log generates on the server with IM service:
Event Type: Warning
Event Source: Live Communications Server Authentication
Event Category: (1003)
Event ID: 16435
User: N/A
Computer: LCS
Description:
At least one invalid authentication signature was detected.
There were 2 messages with invalid signatures in the last 7112 minutes. The last one had the FROM header: sip:[email protected]
Cause: This could be due to a client or server which is not handling authentication correctly, or it could be due to an attacker.
Resolution:
None needed unless the failure count is high (>100). Check your network for any rogue clients. Restart the server if problem persists.
Notifications sent by the SMTP channel work fine!
I Have the following Servers:
LCS (live.august.ru) - Win 2003 EE SP2 + Live Communication Server 2005 SP1
SCOM - Win 2012 + SCOM 2012 SP1
Also I have a third server (Win 2003 + SCOM 2007 R2) and it sends notifications to the same VMLCS server successfully. The configurations of IM Channels are identical on both servers:
IM server: live.august.ru
Return address: sip:[email protected]
Protocol option: TCP
Authentication method: Kerberos
IM port: 5060
I tried to change the Authentication method to NTLM, and the port to 5061, but it doesn't help...

Hi,
Please refer to these following articles to configure IM channel correctly:
How to Create and Configure the Notification Action Account
http://technet.microsoft.com/en-us/library/hh212835.aspx
How to Enable an Instant Message Notification Channel
http://technet.microsoft.com/en-us/library/hh212690.aspx
Enabling Instant Messaging Notifications in System Center 2012 Operations Manager
http://opsmgrunleashed.wordpress.com/2012/02/24/enabling-instant-messaging-notifications-in-system-center-2012-operations-manager/
Alex Zhao
TechNet Community Support

Error Event ID 103 on publishing server

Hello everyone
I started migrating my environment from App-V 4.x to App-V 5.0
I installed one App-V Management Server and one App-V Publishing server, I created a new group called App-V Admins which includes all the App-V administrators and the machine accounts of both servers and I added it to the local
administrator group on both of the servers so they will have full permission on each other
the management server seems to work fine but the publishing server get
AuthenticationFailed when I navigate to http://localhost:82.
on the event viewer of the publishing server I see the Error Event ID 103.
as a workaround I tired to install the Publishing role on the Management server and there - everything works fine and I can publish packages to clients without any issues.
firewall is disabled on both servers so there's shouldn't be any block
I re-installed the publishing server, changed ports... everything I could think of... I still get that annoying error
my environment is a bit restrict in general because it's a finance organization, so permissions on DC are not widely open but still, I even tried to add permissions on my DC's root for App-V Admins and it makes no difference.
anyway, following TechNet, there's no special permission request so I don't even know if that's the problem
anyone with ideas?
thanks
Tamir Levy

Hi Sayareddy,
What operations did you do when you met this issue?
Whether you created some event receviers in your SharePoint.
Please provid access to nt authority\authenticated users group in the master page gallery as read.
Repairing SharePoint installation, compare the result.
If this issue still exists, I suggest you install the latest CU to check if it works.
Here are some similar posts for your references:
https://technet.microsoft.com/en-us/library/ff382637%28v=office.14%29.aspx?f=255&MSPPError=-2147217396
https://social.technet.microsoft.com/Forums/en-US/45690250-9c63-49b8-96ea-fe471568e5ad/event-6875-error-help?forum=sharepointadminprevious
Thanks,
Wendy
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

App-V 5.0 Streaming over SCCM 2012 SP1 - High Availability / Load Balancig

Hello Anybody,
the default App-V 5.0 Streaming (SharedContentStoreMode = on) Deployment over SCCM belongs to a HTTP-Streaming over http:\\SCCM-Server\... . The whole content flows from SCCM to the App-V-Client. Is it possible to create there a high availability solution?
Yes, we can set a second distribution point. But in th App-V-Client are always only one Distribution Source.
Is it possible to set there an clustered adress of an other IIS? Is it possible to change the publishing Distribution Source with an SMB-Path to File-Cluster? Is there a trick with Source-Root-Parameter in App-V-Client? Or are ther anything else to create
a high availibility App-V-Streaming-Solution?
Yes, with App-V-Management-Server there is a high availability solution. - But we have only SCCM-Infrastruktur for App-V-Distribution.
Thank you, best regards
Daniel

Daniel, do you found solution?

SCCM 2012 SP1 errors when downloading updates

Currently using SCCM 2012 SP1 with CU2 and I am having some update download issue with Automatic Deployment Rules.
The Environment is:
Server 2008 R2
SCCM 2012 SP1 CU2 (Upgraded from SCCM 2012 CU2)
I created an Automatic Deployment Rule for Adobe Flash. Since I was having the same issue with Adobe Reader, when I published via SCUP to WSUS I chose not to sign the updates.
After publishing to WSUS I then sync SCCM, I see the updates and then in the ADR I had it download the updates and I see this error:
Authentication of file C:\Windows\TEMP\CABDEC5.tmp failed, error 0x800b0004 Software Updates Patch Downloader 8/15/2013 6:49:43 PM 3712 (0x0E80)
ERROR: DownloadContentFiles() failed with hr=0x80073633 Software Updates Patch Downloader 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Failed to download the update from internet. Error = 13875 SMS_RULE_ENGINE 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Failed to download ContentID 16845337 for UpdateID 16841530. Error code = 13875 SMS_RULE_ENGINE 8/15/2013 6:49:43 PM 6876 (0x1ADC)
Now the funny thing is if I go to the update itself within update group that Flash is a member I can right click it and choose download and the error doesn't occur.
I observed that the UNC path for ADR Adobe flash, when the rule is ran, is populated with folders that have a name something like 44738297895427890.1 or 423154325378u867234789.1. I have come to realize that those are failed downloads. So for the
heck of it I then right clicked the update itself and chose download and it downloaded without issue. Now I'm guessing that when I chose to download directly from the update maybe the system is getting the update from adobe and not from wherever the rule was
trying to get it from. I then see the .1 removed from the directory name and there are updates within them.
Just for clarity here are the steps I go through from SCUP to Syncing...
Log in to WSUS server
Run SCUP as administrator
Get notified there are updates from Adobe and let SCUP download updates
Find the updates the specify the following publishing options
Full Content
Sign all software updates with a new publishing certificate .... (Is this necessary by the way?)
Then click Next
After that's done I then go to SCCM Manager Console and go to Software Updates and right click to Synchronize them.
After that's done then I run the ADR for Adobe Flash and when it goes to download the updates that's when the error occurs.
What am I missing?
Also, while I wait for help I just recently added the WSUS SCUP certificate to the SCCM server to see if by chance that fixes stuff. If it does then I'll post the results of adding the certificate to the SCCM server.
One other thing, is there a way to delete updates? When I was having this issue in the past, I went in to SCUP I marked the updates as expired and then deleted the updates. Went to SCCM and synchronized the updates and they went from not expired to expired
then I waited, maybe 30 days or so before I could add the updates back in.
Thanks for the help!

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
Have you seen the note at the bottom of this page about this error?
http://technet.microsoft.com/en-us/library/bb932193.aspx
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

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.

SharePoint server 2013 Search Service App 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.
Thanks a lot.

Hi,
According to your post, my understanding is that SharePoint server 2013 Search Service App did not work on Windows server 2012 R2.
Please make sure you configure Search Service Application correctly. You can refer to:Create and configure a Search service application in SharePoint Server 2013
I recommend to created new Search Service Application, and made a full crawl. Then assigned the new SSA as the default SSA for webapplications. Finnlay checked the issue doesnt occur now,
If all search related components now are online, to keep the enviroonment clean, you can delete the old SSA.
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support

CM 2012 SP1 equivalent of App-V Publishing Server

Similar Messages

Maybe you are looking for