1 validation error detected
Value '[]' at 'subnetIds' failed to satisfy constraint: Member must have length greater than or equal to 1
I want to make Sagemaker studio Domain in Ohio region, but I got ↑ error.
I also confirmed that vpc existed (no default) and one subnet existed.
How can I fix the error? Please share your knowledge.
On the setup SageMaker Domain screen, if you've been trying with the "Quick Setup" instead try using the "Standard Setup". That got me past this issue.
Related
While trying to add a new fe_users record, on save I get
(1/1) Exception
Could not determine pid
It's TYPO3 9.5.20.
We already have a lot of entries in multiple folders which could be edited without problem.
But those records were imported (by EXT:ig_ldap_sso_auth or with mysql terminal)
These records are used only to be shown (no login is used).
What configuration is missing or could be wrong?
EDIT:
as #biesior mentioned: the error message does not come from the core but from an extension. It's EXT:solrfal (in version 7.0.0)
The real error was not in EXT:solrfal. this extension just hides the error with a misleading message.
The real reason was a wrong database configuration for the table fe_users. Although it is not possible in SQL to have a default value for fields of type text (and any given value is ignored) TYPO3 expects a default value if it is configured. As this is not returned from the database it assumes an error. And EXT:solrfal hooks into the error handling and assumes a wrong error.
Hi just got the same problem.
The error message was called in solrfal ConsistencyAspect::getRecordPageId() which was called by ConsistencyAspect::getDetectorsForSiteExclusiveRecord(). I remember that I have added various tablenames to siteExclusiveRecordTables of Extension Settings of solrfal. And yes, there was one table without pid. After removing this table from list, deleting files works again.
I have spent 10+ hours working with Microsoft's support to configure a hybrid setup between our On-Premises Exchange 2016 Server and Azure AD environments and are currently stuck on an error (see below) when trying to assign the TlsCertificateName value to the On-Premises Receive Connector.
These commands create a variable $TLSCertName that include the certificate issuer and subject values:
$TLSCert = Get-ExchangeCertificate -Thumbprint <Thumbprint>
$TLSCertName = "<I>$($TLSCert.Issuer)<S>$($TLSCert.Subject)"
Set-ReceiveConnector "<Receive Connector Name" -TlsCertificateName $TLSCertName
The error displayed when trying to execute this command is:
Cannot process argument transformation on parameter 'TlsCertificateName'. Cannot convert value "<TLSCertName>" to type "Microsoft.Exchange.Data.SmtpX509Identifier". Error:
""<TLSCertName>" isn't a valid Certificate Identifier."
+ CategoryInfo : InvalidData: (:) [Set-ReceiveConnector], ParameterBindin...mationException
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,Set-ReceiveConnector
+ PSComputerName : <Server's FQDN>
Microsoft believes the problem is caused by some of the values in the certificate subject that contain quotes, i.e. OU="Hosted by CONTOSO, Inc.", O="CONTOSO, Inc.", thus causing the command to truncate the contents of the TLSCertName variable.
I have tried manually entering the argument instead of using the variable (with and without quotes), using single quotes, escaping the quotes (`"), but nothing has worked.
Has anyone come across this issue? I have tried researching online but haven't been able to find a solution.
Any help will be greatly appreciated!
So, after a few hours venturing on my own instead of working with Microsoft support I finally figured out the reason for the error by complete coincidence + guess work.
While reviewing values for the certificate's subject in EAC, I noticed when I clicked on the subject field a message popped up saying:
"In the subject of the certificate, the important value is the common
name (CN), which indicates the host that the certificate can be used
for."
The SSL certificate I'm using is a Multi-domain certificate, and since the common name can only contain up to one entry, the certificate uses a field called Subject Alternate Name (SAN) which allows multiple names to be included. Therefor there is no CN field available in the subject.
Exchange does not read/use the SAN field and wasn't accepting the command because of the missing CN (wish this was documented somewhere and their support knew it as well).
The solution was to use the contents of the TLSCertName variable in the command, and manually add the CN value to the subject section, as in:
<S>CN=contoso.com, OU=Multi-Domain SSL, OU="Hosted by CONTOSO, INC.", O="CONTOSO, Inc."...
Keep in mind the CN must exist in the SAN per standard mandates. You can read more information about this in https://support.dnsimple.com/articles/what-is-common-name/
Hope this helps someone looking for an answer for the same problem.
Now off to solve the issue that depended on this!
For anyone else finding this and having trouble with the guidance at https://social.technet.microsoft.com/wiki/contents/articles/54393.exchange-2019-set-tls-certificate-name-on-your-receive-connector.aspx, I solved the same problem by using these slightly modified commands:
$cert = Get-ExchangeCertificate -Thumbprint <THUMBPRINT>
$tlscertificatename = "<I>$($cert.Issuer)<S>$($cert.Subject)"
Set-ReceiveConnector "EX2019\Client Frontend EX2019" -TlsCertificateName $tlscertificatename
My change from the TechNet post is the addition of <I> and <S> in the 2nd line.
I log the error to Google StackDriver Logging.
But the Google Cloud Error Reporting doesn't recognise it (work for others).
Is my formatting so different that error reporter can not recognise it ?
What's the parsing rule of Google Cloud Error Report ?
The logs is:
02:05:12 ERROR application -
! #78in3pjc5 - Internal server error, for (GET) [/api/news/page/1] ->
play.api.UnexpectedException: Unexpected exception[NonNullableColumnRead: SQL `NULL` read at column 5 (JDBC type Array) but mapping is to a non-Option type; use Option here. Note that JDBC column indexing is 1-based.]
at play.api.http.HttpErrorHandlerExceptions$.throwableToUsefulException(HttpErrorHandler.scala:247)
at play.api.http.DefaultHttpErrorHandler.onServerError(HttpErrorHandler.scala:178)
at play.core.server.AkkaHttpServer$$anonfun$1.applyOrElse(AkkaHttpServer.scala:363)
at play.core.server.AkkaHttpServer$$anonfun$1.applyOrElse(AkkaHttpServer.scala:361)
at scala.concurrent.Future.$anonfun$recoverWith$1(Future.scala:413)
at scala.concurrent.impl.Promise.$anonfun$transformWith$1(Promise.scala:37)
at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:60)
at akka.dispatch.BatchingExecutor$AbstractBatch.processBatch(BatchingExecutor.scala:55)
at akka.dispatch.BatchingExecutor$BlockableBatch.$anonfun$run$1(BatchingExecutor.scala:91)
at scala.runtime.java8.JFunction0$mcV$sp.apply(JFunction0$mcV$sp.java:12)
Caused by: doobie.util.invariant$NonNullableColumnRead: SQL `NULL` read at column 5 (JDBC type Array) but mapping is to a non-Option type; use Option here. Note that JDBC column indexing is 1-based.
at doobie.util.meta$Meta.unsafeGetNonNullable(meta.scala:50)
at doobie.util.composite$Composite$$anon$6$$anon$7.$anonfun$get$3(composite.scala:121)
at doobie.util.composite$Composite$$anon$6$$anon$7.$anonfun$get$3$adapted(composite.scala:121)
at doobie.util.kernel$Kernel$$anon$6.$anonfun$get$3(kernel.scala:80)
at doobie.util.kernel$Kernel$$anon$6.$anonfun$get$3$adapted(kernel.scala:80)
at doobie.util.kernel$Kernel$$anon$6.$anonfun$get$3(kernel.scala:80)
at doobie.util.kernel$Kernel$$anon$6.$anonfun$get$3$adapted(kernel.scala:80)
at doobie.util.kernel$Kernel$$anon$6.$anonfun$get$3(kernel.scala:80)
at doobie.util.kernel$Kernel$$anon$6.$anonfun$get$3$adapted(kernel.scala:80)
at doobie.util.kernel$Kernel$$anon$6.$anonfun$get$3(kernel.scala:80)
Could you provide the full log entry (e.g. as it appears then fully expanded in https://console.cloud.google.com/logs)?
The problem doesn't appear to be in the format of the stacktrace. The error is captured by if I:
go to the Cloud Console API explorer
enter "projects/[PROJECT_NAME]" for projectName
copy your content (i.e. starting from 02:05:12)
replace newlines with "\n"
paste that as a message in the Request Body
hit "Execute"
While creating Kinesis Analytics application it successfully discovered my schema based on the data. However, when I hit save and continue, I get following error
Error updating application There was an issue updating your
application. Error message: 1 validation error detected: Value 'C' at
'input.inputSchema.recordColumns.2.member.name' failed to satisfy
constraint: Member must satisfy regular expression pattern:
[a-zA-Z][a-zA-Z0-9_]+
my sample record is below
{"reported": {"timestamp": "1482231365", "C": "40", "id": "D_aa-bb"}}
My bad, I overlooked the error message. Found the solution, hope it might help someone.
The auto detected schema name was the issue. From the sample record, the auto detected column name was C and the regex says it should contains atleast two characters. After editing the schema manually with two characters it succeeded.
There was another issue though, the auto detected column name timestamp is a reserved keyword, which we need to change.
So I want to create a database link in oracle, my username is jefferson and I want to connect trough opms so I was told to do this.
create database link tmpp connect to jefferson[opms] identified by nothing using $something ;
For some reason when I try to use [] syntax it just tells me indentified is missing. Why is this not working, I was told to do it this way but I can't find any help in the official documentation for [] usage or the correct syntax.
You can create a fixed-user database link like this, but you need to enclose the entire proxy user identifier in double-quotes; and because it's now a quoted identifier the case has to match the DBA_USERS username, which is uppercase by default:
create database link tmpp connect to "JEFFERSON[OPMS]" identified by nothing using ... ;
As noted in MOS document 1477939.1 you can't create a connected-user database link (which you aren't trying to do); and the 30-character limit on identifiers applies, so the total length of both usernames plus the square brackets has to be 30 characters or less (which is also fine in your example).
However, as discussed in this related question, this functionality is currently broken in 11.2.0.4 and above because of bug 19191702.