After you started Viya, it may take a few minutes to get it up and running. Please let us know if you still get 503s after 5 minutes or so, and any logs from the failures. Thanks. ... View more

I see this post below has some relevant info that you can try.  https://communities.sas.com/t5/SAS-Viya-on-Microsoft-Azure/Resource-size-availability-error-despite-adequate-quotas-Azure/m-p/870297 Also, you can find out which zones are supported for each region using AZ CLI and use that accordingly.  this may also help - https://learn.microsoft.com/en-us/azure/reliability/availability-zones-service-support Please let us know if you are able to get it to work. Thanks!   ... View more

Sorry to hear it failed, we need more info on the failures. Are there any info available if you go to the failed deployment and check for any errors there or if you have any activity logs related to the failed deployment? It may have a reason for the timeout. Sometimes the 'Resource quota limit exceeded' could be the reason, in that case try to increaase the quota. Alternatively, you can try deploying in another region like eastus and see if that works.  If we know the reason (from the failed deployment logs) for time exceeded that would help. Thanks!    ... View more

The deploy could fail for various reasons, curious if you are able to see what release of Viya is being used? I ran a deploy internally for 2025.02 and it deployed successfully. If you have part of the logs in the deployment storage account and share where it got stuck, that can help us figure out.  Sometimes microsoft network issues could cause it to fail, and deleting old deployment and starting a re-deploy may help. ... View more

This post might also help: https://communities.sas.com/t5/SAS-Viya-on-Microsoft-Azure/Unable-to-Create-Account-on-SAS-Viya/m-p/921919 Please let us know if you still experience problems. Thanks! ... View more

Please try the suggestion from this post and let us know if it helps https://communities.sas.com/t5/SAS-Viya-on-Microsoft-Azure/SAS-Viya-Deployment-through-Azure-Marketplace-stuck/m-p/936151   ... View more

Sometimes it takes a little bit of time after deploy is finished to get the SAS Studio link to work, you can try again and see if it works. Also, you may find the doc useful for some config tasks https://go.documentation.sas.com/doc/en/viyaakscdc/v_001/viyaakswlcm/home.htm What version does it show that you are using?   Thanks Priyha ... View more

@Lillioja  Hope using the deletion links and different name for each deployment as suggested above helped with the problem. If it did not solve the problem, it could be a different issue based on the error message you have posted. It says the automation account is already exists. It could be related to the recent changes by Microsoft on the restrictions of only 2 automation account can be created  per region, see the link below.   https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/azure-subscription-service-limits#automation-limits Pay-as-you-go, MPN, Azure Pass subscriptions can create 2 Automation accounts per subscription in any of the regions supported by the service. A possible solution could be to try your deployment in a different region if you are still facing issues.   ... View more

Please try the deploying again with the latest 2024.08 release, we have fixed the issue and able to deploy successfully. ... View more

Thank you for all the details, looking into this and will get back. Thanks. ... View more

Hi, I am looking at the issue and would like more details. Are you connecting to Denado using SAS/Access to JDBC and the libname is failing? Would you mind sharing the error details? Thanks, Priyha ... View more

Below are the steps for connecting to Azure SQL server: 1. In the odbc.ini file that is located in the jump vm of the deployment (/viya-share/access-clients/odbc/odbc.ini), under section [ODBC Data Sources] section, add the bold font for Azure Synapse. Then add the block for Azure synapse [SQL Server Wire Protocol - Azure Synapse/SSL Enabled Example].   [ODBC Data Sources] SQL Server Legacy Wire Protocol=SAS ACCESS to MS SQL Server Legacy SQL Server Wire Protocol=SAS ACCESS to MS SQL Server Amazon RedShift Wire Protocol=SAS ACCESS to Amazon Redshift Greenplum Wire Protocol=SAS ACCESS to Greenplum SQL Server Wire Protocol - Azure Synapse/SSL Enabled Example=SAS ACCESS to MS SQL Server [SQL Server Wire Protocol - Azure Synapse/SSL Enabled Example] Driver=/opt/sas/viya/home/lib64/accessclients/lib/S0sqls28.so Description=SAS Institute, Inc 8.0 SQL Server Wire Protocol AEKeyCacheTTL=-1 AEKeystorePrincipalId= AEKeystoreClientSecret= AlternateServers= AlwaysReportTriggerResults=0 AnsiNPW=1 ApplicationIntent=0 ApplicationName= ApplicationUsingThreads=1 AuthenticationMethod=1 BulkBinaryThreshold=32 BulkCharacterThreshold=-1 BulkLoadBatchSize=1024 BulkLoadFieldDelimiter= BulkLoadOptions=2 BulkLoadRecordDelimiter= BulkLoadThreshold=2 ColumnEncryption=Disabled ConnectionReset=0 ConnectionRetryCount=0 ConnectionRetryDelay=3 CryptoProtocolVersion=TLSV1,TLSV1.1,TLSV1.2 Database= Domain= EnableBulkLoad=0 EnableQuotedIdentifiers=0 EnableServerSideCursors=1 EnableScrollableCursors=4 EncryptionMethod=1 FailoverGranularity=0 FailoverMode=0 FailoverPreconnect=0 FetchTSWTZasTimestamp=0 FetchTWFSasTime=1 GSSClient=native HostName=<SQL_Server_host> HostNameInCertificate= #IANAAppCodePage= InitializationString= KeepAlive=0 Language= LoadBalanceTimeout=0 LoadBalancing=0 LoginTimeout=15 LogonID= MaxPoolSize=100 MinPoolSize=0 MultiSubnetFailover=0 PacketSize=-1 Pooling=0 PortNumber=<SQL_Server_server_port> PRNGSeedFile=/dev/random PRNGSeedSource=0 ProxyHost= ProxyMode=0 ProxyPassword= ProxyPort= ProxyUser= QueryTimeout=0 ReportCodepageConversionErrors=0 SnapshotSerializable=0 TrustStore= TrustStorePassword= ValidateServerCertificate=1 WorkStationID= XMLDescribeType=-10 SSLLibName=/usr/lib64/libssl.so.10 CryptoLibName=/usr/lib64/libcrypto.so.10 2. In Azure portal for SQL server, make sql db accesible to all azure services as shown below.    3. Make sure there is a sql database exists in the SQL server created, else create a new database.  4. In the libname statement, use these options: SSLLibName=/usr/lib64/libssl.so.1.1; CryptoLibName=/usr/lib64/libcrypto.so.1.1; libname paygsql sqlsvr noprompt="DRIVER=SAS ACCESS to MS SQL Server; HOST=mysqlserver.database.windows.net; PORT=1433; database=sqlsdbname; UID=user; PWD=pwd; SSLLibName=/usr/lib64/libssl.so.1.1; CryptoLibName=/usr/lib64/libcrypto.so.1.1;"; With these steps, the connection to Azure SQL server is successful. Please let us know if you have further questions.    ... View more

We have added a runbook that will allow adding more IP addresses after the deployment. This is available in the latest, so new deployment with latest is needed. This is documented here: https://go.documentation.sas.com/doc/en/viyaakscdc/v_001/viyaakstasks/n0kldoq6spqxman129kk4f5klmq8.htm Please let us know any questions. Thanks, Priyha   ... View more

Thanks for the update, we will look into this and get back to you. ... View more