I'm not an Unified Communications developer and my head is thumping.
I have three virtual computers (Windows Server 2012 R2) that are joined to the domain. They are pingable among themselves and two Lync clients on VM#2 and VM#3 can talk to each other:
VM#1 AD DC
VM#2 Lync 2013 Server
VM#3 Application Server
The UCMA application is supposed to run on VM#3 that is also my development environment (Visual Studio and UMCA 4.0 SDK are installed). But then I can't start the collaboration platform with ProvisionedApplicationPlatformSettings since I get a ProvisioningFailureException that says that somebody was "unable to find the Sqld database".
I followed "General application activation" http://msdn.microsoft.com/en-us/library/office/dn466115(v=office.15).aspx step by step. Question 1: Do I have to execute these PowerShell cmdlets on VM#2 or VM#3?
I do not know what database the exception is talking about. Question 2: Is it looking for a local database that should be in sync with the Central Management Store on VM#2?
Question 3: I read about installing Central Management Store replication service by running Bootstrapper.exe /BootstrapLocalMgmt /MinCache. When do I need replication in my system? Is that an optional thing?
Post update:
When I execute the New-CsTrustedApplicationPool and Enable-CsTopology cmdlets on VM#2, Get-CsManagementStoreReplicationStatus will display two entries:
UpToDate : True
ReplicationFqdn : LYNCSERVER.artus.demo
and
UpToDate : False
ReplicationFqdn : APPSERVER.artus.demo
Question 1.1: UpToDate should be set to True after executing Enable-CsReplica and Invoke-CsManagementStoreReplication cmdlets, shouldn't it? Does the second entry mean a Local Management Store that is located in VM#2?
Question 1.2: Are the following parameters correct?
New-CsTrustedApplicationPool -Identity trustedapps.artus.demo
-Registrar Registrar:LYNCSERVER.artus.demo -Site Site:DemoSite1 -ComputerFqdn APPSERVER.artus.demo;
Question 3.1: On what VM do I have to run Bootstrapper.exe /BootstrapLocalMgmt /MinCache. I think this was automatically done during Lync Server 2013 installation on VM#3 and I can't imagine that on VM#2 Lync Server 2013 core components have to be installed.
Thanks for answering.
Question #1: It Depends on the command. If you are referring to the new-csTrustedApplicationPool, new-csTrustedApplication,enable-cstopology and new-csTrustedApplicationEndpoint commands then they need to be run on vm#2 your Lync 2013 server. Request-CSCertificate needs to be run on vm#3 your application server.
(Response To Update) So I guess APPSERVER.artus.demo is the name of vm #3. You need to run the boot-strapper on it to allow replication to work.
**Question #2:**Yes it's the CMS Db, looking at question 3 it sounds as if you haven't run bootstrapper.
Question #3: Have never deployed a UCMA service without replication although it can be done. Have seen people try to turn off replication on the application pool and it fail. Regardless for a first time install it's not optional.
Related
Two month ago I deployed a new VM in Azure. I used the pre-configured "SQL Server 2016 SP1 Standard on Windows Server 2016" with 7 GB of RAM, and I chose the offered option to make backups automatically. Only other things I changed is add it to AD and put some databases (largest of ~2 GB size of backup file)
Now the server is running a service called SqlIaaSExtension.Service which I understand is for doing these backups as well as automated patching. You can find the services description here: MS service description
The problem is, it keeps on building up memory until after some weeks the SQL Server itself fails to execute larger queries. A restart of the SqlIaaSExtension.Service fixes the problem, but this is not at all a sustainable solution.
Does anybody know a working solution other then disabling the service and loosing the functionality altogether?
My setup (german):
I have meanwhile got some Information from Microsoft:
There seems to be an error in the SqlIaaSExtension.Service which is known to MS and will eventually be fixed.
Workaround is:
A: If you don´t need the functionality - remove this service, as indicated in the service description.
B: If you want to keep the functionality - restart the service periodically. Possibly automate via Task-planner.
Updated info from MS 19/07/2017: Error is identified and should be fixed in the next 7-10 Days. A mitigation is restarting the service if necessary.
Updated info from MS 31/07/2017: Error should be fixed in Version 1.2.19.0. This can be checked from the Azure Portal under "extensions" in the VM-Menu.
I am trying to deploy a Asp.NET MVC 4 app to a third-party host, and encountered some problems while following this tutorial.
The tutorial created 2 New SQL Server Database, and set the Remote connection string of DefaultConnection to one SQLExpress database and that of SchoolContext to another. However, I want to have only one database, so I only created one New SQL Server Database, and used the same connection string for DefaultConnection AND MyAppContext. Would this cause problem?
Right now my app won't publish with the following error. not sure if it stems from this. MyAppUsr comes from a Grant script, Grant.sql, that I developed from this tutorial.
Error 3 Web deployment task failed. (An error occurred during execution of the database script. The error occurred between the following lines of the script: "8" and "11". The verbose log might have more information about the error. The command started with the following:
"CREATE USER [MyAppUsr] "
The login already has an account under a different user name. http://go.microsoft.com/fwlink/?LinkId=178587 Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_SQL_EXECUTION_FAILURE.) 0 0 MvcCP
MyAppContext uses LocalDb instead of SQLExpress. The deployment in the tutorial uses SQLExpress. Can I just create a new SQLExpress database and have MyAppContext (LocalDb) "points to" the SQLExpress database?
You must have run the script at least once prior, correct? Because what it is saying is that the user [MyAppUsr] already exists. You will need to drop the user first, then rerun it. ie:
DROP USER [MyAppUsr]
You can embed that into your script, better yet, put a conditional check if exists...
I have a small wpf application using Entity Framework attached with Local DB. Development machine no issue it works fine. But when I deploy run or try to run other machine it crashes.
Following is error message.
Problem Event Name: CLR20r3
Problem Signature 01: ena-wixomwindowapplication.exe
Problem Signature 02: 1.0.0.0
Problem Signature 03: 53fc8435
Problem Signature 04: System.Data
Problem Signature 05: 4.0.30319.18047
Problem Signature 06: 51553556
Problem Signature 07: 2592
Problem Signature 08: 27
Problem Signature 09: System.Data.Entity.Core.Entity
OS Version: 6.1.7601.2.1.0.256.4
Locale ID: 1033
Additional Information 1: 0a9e
Additional Information 2: 0a9e372d3b4ad19135b953a78882e789
Additional Information 3: 0a9e
Additional Information 4: 0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
If the online privacy statement is not available, please read our privacy statement offline:
C:\WINDOWS\system32\en-US\erofflps.txt
LocalDB is a special version of Microsoft SQL Server Express that is automatically installed with Visual Studio (since version 2012). The main thing about LocalDB is that it automatically shuts down when it isn't used, thus it does not consume any resources while your developing (only during your test runs).
If you want to run your application on another machine that does not have a version of Visual Studio installed, you have to manually install another DB Server, e.g. SQL Server Express. After you've done this you have to change your Database Connection String within your App.config file to accommodate the change.
If you have any further questions, please feel free to ask.
Update after Bal Sharma's answer:
Of course you can install a stand-alone version of LocalDB on your target machine - just type 'LocalDB download' into your favorite search engine. But the following problem will remain: LocalDB shuts down when it isn't used. This is of course done on a per-user basis. That means that a LocalDB instance only runs in the context of the user currently logged in, which implies that if another user logs in, he or she will get another instance of LocalDB with the previously used database(s) not present.
Now I don't know your production environment, but usually this is not what you want. Use SQL Server (Express) or any other DB server you're familiar with (maybe Oracle) that can run in the service context.
Read the following for more information:
Is it normal to use LocalDb in production?
http://blogs.msdn.com/b/sqlexpress/archive/2011/12/09/using-localdb-with-full-iis-part-1-user-profile.aspx
http://blogs.msdn.com/b/sqlexpress/archive/2011/12/09/using-localdb-with-full-iis-part-2-instance-ownership.aspx
I'm using the AWS Toolkit in Visual Studio 2013 to attempt to launch a new instance on Amazon RDS. I get through the wizard for creating the new instance and after clicking finish, there is a delay, and then a message appears saying:
Error launching DB instance: DB Security Groups can only be associated with VPC DB Instances using API version 2012-01-15 through 2012-09-17.
Launching different types of instances (SQL Server SE vs MySQL) doesn't seem to help, nor does selecting different versions of the platforms (SQL Server 2008 vs 2012). The only thing that gets it to go through is unchecking the box for "default" in the DB Security Groups area. However, I feel like something is going on here that shouldn't be happening.
Can anyone explain why this is happening and how I can resolve it other than by not setting a default security group? Thank you.
If you created your AWS account recently, you will be using a VPC by default.
It sounds like the API the plugin is trying to use hasn't been updated. The latest version is 1.5.6, and looking at the history it seems like some of these features were added in 1.5.0.
I finally solved it! Since I couldn't use the API that the VS 2013 plugin uses, I had to manually add my IP to the Security Group created for my Elastic Beanstalk.
Go to the console, ec2's security groups configuration
Find the one which description matches your Beanstalk (e.g.: Security Group created for Beanstalk Environment to give access to RDS instances)
Hit Inbound, Edit and add a new rule for All Traffic (I guess HTTP should be enough, but just in case).
In Source, select My IP and Save.
I installed Oracle DB 11g,
everything was working well, but suddenly process
OracleDbConsoleorcl didn't start anymore, I try
manually but it always shows this message:
Windows could not start OracleDbConsoleorcl on
Local Computer. If this is a non-Microsoft service,
contact the service vendor, and refer the service
specific error code 2
What should I do??
You can use the following command to check the issues/configuration status of OracleDBConsoleorcle:
emctl status dbconsole
You can then configure accordingly.
Oracle 11g: Windows could not start the OracleDBConsoleorcl on Local Computer
I was using the Oracle 11g in my Windows 7 Professional system for few days.. Suddenly, I was not able to use the sql developer to connect the schema/user.
I found that the Oracle... services were down in the Windows services windows.
a) Oracle ORCL VSS Writer Service - running
b) OracleDBConsoleorcle - not running
c) OracleJobSchedulerORCL - not running
d) OracleServiceORCL - not running
When I started the OracleDBConsoleoracle, it thrown a error "Windows could not start the OracleDBConsoleorcl on Local Computer".
(Below solution is worked for me, based on the various fo rum threads)...
a. go to C:.......\product\11.1.0\db_1\oc4j\j2ee
b. copy paste the folder: OC4J_DBConsole_192.168.x.y_orcl, two times
c. rename one of the two new folder as OC4J_DBConsole_localhost_orcl
d. rename the other one as OC4J_DBConsole__orcl
after making these changes and a reboot, it started to running.........
In my case was the server IP was changed, I've placed the IP back and It's working!