Error Creating Server Instance. Check Access Permission For The Directory
Board ExportXMLWordPrintable Details Type: Bug Status: Resolved Priority: Major Resolution: Complete Affects Version/s: 2.8.1.RELEASE Fix Version/s: 2.9.0.M2 Component/s: SERVER Labels: Y5M5 Environment: Windows Vista64 Description Right click in the Servers window, choose New - Server Select a properly configured (JDK set correctly, etc) instance of tc server from the VMware folder, Finish The tc server object created in the Servers window is useless. Attempting to start, publish, drop objects on it - all result in an error dialog with title "Problem Occurred" and http://forum.spring.io/forum/spring-projects/springsource-tool-suite/117830-creating-tc-server-instance-in-sts text: "Could not load the Tomcat server configuration at \Servers\tc_server2.6.2 at localhost-config. The configuration may be corrupt or incomplete." And indeed, STS has created a folder under the current workspace at the path \Servers\tc_server2.6.2 at localhost-config which is empty. It would seem that some Tomcat configuration files should have been copied there by the New Server wizard. I https://issuetracker.springsource.com/browse/STS-2338 think this bug has existed since at least STS 2.5.2. There have many numerous queries and complaints about it on the Spring forums and elsewhere. Some related fixes have been made to templates (a problem with spaces in the server name) and Spring folk always ask users to A. Install STS in a non-protected area of Windows i.e. outside of Program Files and B. run tcruntime-instance.bat create myserver at the cmd line. I have done both of these and the bug remains. In the case of B, the cmd prints the correct output and the created directory "myserver" is nicely filled with a bunch of tc server files. OptionsShow AllShow OpenSub-Tasks 1. instance creation fails when JAVA_HOME is not set correctly Resolved Steffen Pingel 2. instance verification should be more strict Resolved Steffen Pingel Activity Ascending order - Click to sort in descending order All Comments History Activity Transitions Hide Permalink Martin Lippert added a comment - 14/Dec/11 9:32 AM Some more comments and problem descriptions here: http://forum.springsource.org/showthread.php?101098-Embedded-TC-
ExportXMLWordPrintable Details Type: Bug Status: Resolved Priority: Minor Resolution: Fixed Affects Version/s: 3.2.0.RELEASE, 3.7.0.RELEASE Fix Version/s: 3.7.2.RELEASE Component/s: SERVER Labels: None Environment: Windows 7 Description When creating a Pivotal tc Server through the New Server wizard, https://issuetracker.springsource.com/browse/STS-4259 the wizard fails to create the server if the path contains parentheses. Error creating https://blogs.msdn.microsoft.com/psssql/2013/09/30/error-during-installation-of-an-sql-server-failover-cluster-instance/ server instance with command: "C:\DEV\springsource-3.7.0(x86)\pivotal-tc-server-developer-3.1.1.RELEASE\tcruntime-instance.bat create server -v 8.0.23.A.RELEASE -t bio --java-home C:\Program Files (x86)\Java\jre1.8.0_65". Check access permission for the directory C:/DEV/springsource-3.7.0(x86)/pivotal-tc-server-developer-3.1.1.RELEASE and its files and subdirectories. The instance creation command failed and returned code 1 Output of the instance creation command: 'C:\DEV\springsource-3.7.0' is not recognized as an internal or external command, operable program or error creating batch file. When I remove the parentheses (x86), the server creates correctly. Activity Ascending order - Click to sort in descending order All Comments History Activity Transitions Hide Permalink Alex Boyko added a comment - 19/Nov/15 9:07 AM - edited I think this should be fixed with the fix put in for STS-4198 in 3.7.1 Which was add double-quotes for arg values that are paths. Show Alex Boyko error creating server added a comment - 19/Nov/15 9:07 AM - edited I think this should be fixed with the fix put in for STS-4198 in 3.7.1 Which was add double-quotes for arg values that are paths. Hide Permalink Martin Lippert added a comment - 20/Nov/15 3:58 AM Hey Alex, are you sure this is the same? STS-4198 was about the launch configs, this is about the instance creation. Just asking... Show Martin Lippert added a comment - 20/Nov/15 3:58 AM Hey Alex, are you sure this is the same? STS-4198 was about the launch configs, this is about the instance creation. Just asking... Hide Permalink Alex Boyko added a comment - 20/Nov/15 7:57 AM You're right Martin, I indeed overlooked it and this is about the instance creation rather than launching. However, I've tried to reproduce this with 3.7.1 STS om Mac - it works fine. I'll try this on Windows when i get a chance. Show Alex Boyko added a comment - 20/Nov/15 7:57 AM You're right Martin, I indeed overlooked it and this is about the instance creation rather than launching. However, I've tried to reproduce this with 3.7.1 STS om Mac - it works fine. I'll try this on Windows when i get
Escalation Services team. Error during installation of an SQL server Failover Cluster Instance ★★★★★★★★★★★★★★★ psssqlSeptember 30, 201317 0 0 0 A common issue I've run into while helping with SQL Server Failover Cluster (FCI) installations is the failure of the Network Name. In the following post I'll discuss a bit of background, the common root cause, and how to resolve it. Background The SQL Server Database Engine service is dependent on the Network Name resource. A failure of the Network Name will result in the SQL Server Resource not coming online. When the Windows Failover Cluster (WFC) is initially configured a Cluster Name object (CNO) will be created. The CNO is visible as a computer object in your Activity Directory Users and Computer snap-in (dsa.msc). By default the CNO will be created in the Computers container and granted specific permissions: After a successful SQL Server FCI installation you will now see a Virtual Computer Object (VCO) for the SQL Server Network Name: *Note: After the CNO is created any additional Network Name resource in the cluster is considered a Virtual Computer Object. VCO’s are simply Computer objects in which the CNO has permissions to change the properties or reset the password. Problem But what if the CNO does not possess the required permissions to create computer objects in the “Computers” container? It is in the above scenario where we commonly see the following errors during SQL Server FCI installation: The following error has occurred: The cluster resource ‘SQL Server (SQL2012)' could not be brought online due to an error bringing the dependency resource ‘SQL Network Name(VSQL2012)' online. Refer to the Cluster Events in the Failover Cluster Manager for more information. A user encountering the same issue while installing a pre-SQL Server 2012 version may see: The cluster resource ‘SQL Server (MSSQLSERVER)' could not be brought online. Error: The resource failed to come online due to the failure of one or more provider resources. (Exception from HRESULT: 0x80071736) System log: Cluster network name resource ‘SQL Network Name (VSQL2012)' failed to create its associated computer object in domain ‘motox.com' during: Resource online. The text for the associated error code is: A constraint violation occurred. Please work with your domain administrator to ensure that: - The cluster identity ‘CLUS2012$' has Create Computer Objects permissions. By default all computer objec