UtterAccess.com
X   Site Message
(Message will auto close in 2 seconds)

Welcome to UtterAccess! Please ( Login   or   Register )

Custom Search
 
   Reply to this topicStart new topic
> Error Connect SQL Server Azure, Access 2013    
 
   
carlo
post Jun 5 2017, 04:01 AM
Post#1



Posts: 80
Joined: 12-February 15



Hi

It worked until yesterday and Today i can not connect SQL SQL databases. I not have modify the configuration azure.. the error is image attachment..

error:
sqlstate "37000"
error SQL server "923"


The string for connection in my access VBA 2013

Dim strConnectionStringWeb As String
strConnectionStringWeb = "ODBC;DRIVER=SQL Server Native Client 11.0; " & _
"SERVER=xxxxx;DATABASE=db_xxxxxx;UID=xxxxxxExternalWriter;pwd=xxxxx"


Thank

Attached File(s)
Attached File  error.png ( 11.39K )Number of downloads: 3
 
Go to the top of the page
 
GroverParkGeorge
post Jun 5 2017, 07:09 AM
Post#2


UA Admin
Posts: 29,965
Joined: 20-June 02
From: Newcastle, WA


This is the SQL Azure database behind an Access Web App I'll bet.

If so, here is what happened.

You'll have to re-enable external connections to the SQL Azure database in the accdw. Then, get the new server name, database name, UID and PWD and use them to relink your accdb to the new database.

If this is not your problem, we'll have to search further.

--------------------
Go to the top of the page
 
carlo
post Jun 5 2017, 07:26 AM
Post#3



Posts: 80
Joined: 12-February 15



Yes this is my problem, all connection modify ..... pullhair.gif

Have been changed the istance without notice microsoft...!!!!

Thank you for information

Now I change the names in all inormation in odbc source


Go to the top of the page
 
GroverParkGeorge
post Jun 5 2017, 08:21 AM
Post#4


UA Admin
Posts: 29,965
Joined: 20-June 02
From: Newcastle, WA


Totally outrageous behavior. I have long been a fan and supporter of Microsoft, but this one is just unbelievably poor decision making on their part.

--------------------
Go to the top of the page
 
GroverParkGeorge
post Jun 5 2017, 08:26 AM
Post#5


UA Admin
Posts: 29,965
Joined: 20-June 02
From: Newcastle, WA


By the way, I'm gathering examples of how wide-spread this is. I'd like to pass the message along to my contacts at Microsoft. Where are you located? So far I know of users in three states in the USA and one in Sweden. Not everyone everywhere is impacted, but it looks like it's not isolated either.

Also, in case anyone else comes along and sees this, I have amended my blog to include instructions on re-enabling external connections, just in case.

--------------------
Go to the top of the page
 
carlo
post Jun 5 2017, 08:32 AM
Post#6



Posts: 80
Joined: 12-February 15



I' am in Italy..


I lost a working day to fix the problem mad.gif
Go to the top of the page
 
carlo
post Jun 5 2017, 11:13 AM
Post#7



Posts: 80
Joined: 12-February 15



I found this in microsoft

https://support.office.com/en-us/article/Ac...en-US&ad=US

Go to the top of the page
 
GroverParkGeorge
post Jun 5 2017, 11:20 AM
Post#8


UA Admin
Posts: 29,965
Joined: 20-June 02
From: Newcastle, WA


Thanks for sharing that.

I've been blogging about this for a while. Unfortunately, this issue was NOT part of the plan, at least as far as I knew.


--------------------
Go to the top of the page
 
OldMike
post Jun 5 2017, 11:52 AM
Post#9



Posts: 56
Joined: 21-July 15



Hi George, I'm in the UK and we've got what looks like the same problem.

Server has changed though the database name looks the same, no Read/Write connection.

I'd been considering recreating the connection just wasn't sure in case there was something else going on. However now got the confidence to carry on.

Microsoft Customer Service - what's that!?!

Regards

Go to the top of the page
 
GroverParkGeorge
post Jun 5 2017, 11:57 AM
Post#10


UA Admin
Posts: 29,965
Joined: 20-June 02
From: Newcastle, WA


I'm now hearing that Microsoft is telling people who do contact support that this move to new servers is part of the deprecation process and that it can happen again--at any time.


--------------------
Go to the top of the page
 
GroverParkGeorge
post Jun 5 2017, 11:58 AM
Post#11


UA Admin
Posts: 29,965
Joined: 20-June 02
From: Newcastle, WA


I believe when you do re-enable external connections, you will see a new server and database name, as well as UserName and password.

--------------------
Go to the top of the page
 
GroverParkGeorge
post Jun 6 2017, 06:18 AM
Post#12


UA Admin
Posts: 29,965
Joined: 20-June 02
From: Newcastle, WA


I have heard back from the Access team. They are looking into what happened and will reply directly when they have a better picture of the events.

As I thought, the Access team themselves were not involved in the move; it doesn't mitigate the pain, of course, but it does suggest the people who made the change were not aware of the potential problems it would cause.

--------------------
Go to the top of the page
 
GroverParkGeorge
post Jun 7 2017, 08:33 AM
Post#13


UA Admin
Posts: 29,965
Joined: 20-June 02
From: Newcastle, WA


The Access team has responded to my request for clarification.

This was a result of a planned maintenance operation on SPO servers and tenants.

They will work with the owners of that operation to improve communication in the future.

--------------------
Go to the top of the page
 
carlo
post Jun 8 2017, 02:23 AM
Post#14



Posts: 80
Joined: 12-February 15



Than for information..


this problem also connection with Power BI... pullhair.gif


I think that solution is buy Service Azure SQL database....


Go to the top of the page
 
GroverParkGeorge
post Jun 8 2017, 06:11 AM
Post#15


UA Admin
Posts: 29,965
Joined: 20-June 02
From: Newcastle, WA


Moving to SQL Azure is one option, for sure.

--------------------
Go to the top of the page
 


Custom Search
RSSSearch   Top   Lo-Fi    26th July 2017 - 01:35 PM