Forum Discussion
Feb 2024 updates: Access->SQL Server performance issues in the Monthly Enterprise Channel
Hi,
Microsoft fixed the problem last night. There's no new build. You just have to restart Access to restore normal performance with the "SQL Server" driver.
I have also updated our documenting blog article. As written there, it would be good if affected users could briefly report back whether the fix works for them.
HeinziAT Extremely bad luck with this unusual order of appearance of the bug. S*** happens. At least you contributed to a quicker fix by reporting it here.
Servus
Karl
****************
Access Forever
Access News
Access DevCon
Access-Entwickler-Konferenz AEK
Karl_Donaubauer Semi colon issue still seems to be a problem on machines updated to 2312 on Monday February 19. At least Machines with this version fail to refresh tdf links to SQL Server. No issue on the machines that updated to 2311.
The Connect string looks OK, no missing semi colon but the .RefreshLink fails in VBA (but refreshes OK using the linked table manager).
Given that MS tries to fix this stuff via a backdoor rather than issuing a new build, there is no way of knowing from the version/build if a machine should or should not be affected.
Not a great way to manage a SDLC.
Hi Kent,
And I repeat for the third time (after AFo and LI) that I cannot do anything unless you provide a build number where you still see the bug. Without a build, I/we do not know the situation or channel of your client and cannot attempt to reproduce the problem or report it purposefully to MSFT.
Servus
Karl
****************
Access Forever
Access News
Access DevCon
Access-Entwickler-Konferenz AEK
- I'm now a bit confused. re: "There's no new build." are you saying that for a given version (eg 2312) sometimes they do issue a new build number and sometimes not?
Typically my clients turn off Automatic Updates but in this case we wanted 2311 for the LAA. and it seems they forgot to turn Auto Updates off on some machines. Previously I'd used OfficeC2RClient.exe /update user updatetoversion=16.0.xxxxx.xxxxx to install a a specific build but found this failing in recent times. After this week's fiasco, I'm now recommending the ODT.
What exactly is the process for updates?
in your (excellent) article on Roll backs you give the example of using OfficeC2RClient.exe to roll back to a specific build. Is this still working OK for you?
But if you still have Automatic Updates turned on, will that negate your roll back?
and if you have Automatic Updates turned off, can MS still sneak through fixes like the one in this post?
I'll get back to you on the build number for the VBA refreshlink issue. I only have attended TeamViewer access to those machines.Hi Kent,
Too many subjects and questions for a single post. 😉
In your (confusing 🙂 previous post in this thread, which is about the "SQL Server" performance problem, you mentioned 2 different problems:
> Semi colon issue still seems to be a problem on machines updated to 2312 on Monday February 19.
But then you wrote:
> no missing semi colon
So, it is NOT the semicolon problem.
2. ... the .RefreshLink fails in VBA
Is there an error number and message?
For example there was or is a bug around where RefreshLink fails and people (now) in the Monthly Channel get error 3283 "Primary key already exists". So, the error details and build numbers are the essential thing to determine what problem your clients might have.
Servus
Karl
****************
Access Forever
Access News
Access DevCon
Access-Entwickler-Konferenz AEK- I can't get more details from that client until tomorrow but I had another client with the same or similar issue today. I was able to connect to a VM in their network and the error occurs on tdf.RefreshLink
Error: 3283 Primary key already exists.
Version 3212
Build 17126.20190
I won't know how many of their devices are affected until tomorrow morning. I think they all use RDP to VMs so I'm guessing all of them. It's going to need IT/Admin to do a rollback to 2311. The error occurs in the code that checks the FE Vs BE version so I can't just change the connect string using Linked Table Manager and automatically distribute new FEs. They would have to be distrubuted manually.