Solved Unable to access backend after Windows Update (1 Viewer)

LGDGlen

Member
Local time
Today, 16:51
Joined
Jun 29, 2021
Messages
216
Hi All

I have a shared folder with the backend of a split database and users access it via a front end local to their machines.

If no one has their front end open i can open the front end on my local machine accessing the backend via the shared folder on my local machine.

If someone else opens the front end on their local machine and accesses the backend on my machine via the shared folder (the tables are linked to the shared folder via the \\computername\sharedfolder) and then i try to open the front end on my machine i get the following:

1639650883644.png


This happens during the autoexec macro on startup when it is trying to set values in a table.

This was working correctly yesterday but not today. The only thing that has changed is that overnight my windows machine had a cumulative December update

December 14, 2021—KB5008212 (OS Builds 19041.1415, 19042.1415, 19043.1415, and 19044.1415)​


It is really frustrating me and also stopping my development process typically on my last day in the office this year. if anyone has any ideas as to what the issue might be please can you help as i'm in a bit of a predicament

kind regards

Glen
 

arnelgp

..forever waiting... waiting for jellybean!
Local time
Today, 23:51
Joined
May 7, 2009
Messages
16,133
what is the macro doing?
maybe this is a case of Lockout, not directly related to windows update
or office update.
therefore review the code first.
 

LGDGlen

Member
Local time
Today, 16:51
Joined
Jun 29, 2021
Messages
216
Code:
Public Function initVars()

    Dim strUserName As TempVars

    Dim NameSpace As Object
    Set NameSpace = CreateObject("Outlook.Application").GetNameSpace("MAPI")

    For Each Account In NameSpace.Accounts
        ' If you want to see more values, uncomment these lines
        'Debug.Print Account.DisplayName
        'Debug.Print Account.UserName
        'Debug.Print Account.SMtpAddress
        'Debug.Print Account.AccountType
        'Debug.Print Account.CurrentUser
        TempVars!strUserName = StrConv(Account.UserName, vbProperCase)
        'Debug.Print strUserName
    Next

    ' does user not exist in settings table
    If DCount("[UserName]", "Settings", "[UserName] = '" & TempVars!strUserName & "'") = 0 Then

        Set db = CurrentDb
        Set rs = db.OpenRecordset("Settings")

        rs.AddNew
        rs!UserName = TempVars!strUserName
        rs!ShowWelcome = 1
        rs!Language = 1
        rs.update

        rs.Close
        Set rs = Nothing
        Set db = Nothing

    End If

    TempVars!strReportToUse = ""

End Function

this line:

If DCount("[UserName]", "Settings", "[UserName] = '" & TempVars!strUserName & "'") = 0 Then

is the issue, works on ALL other users front ends, and works on mine if no one else is in the database

as i say this was working fine yesterday and nothing has changed here, its working fine on multiple computers accessing the back end concurrently, just not for me when i try when others are connected

if i try and open ANY of the linked tables i get the following:
1639652560093.png
 

Attachments

  • 1639652523275.png
    1639652523275.png
    2.7 KB · Views: 181

arnelgp

..forever waiting... waiting for jellybean!
Local time
Today, 23:51
Joined
May 7, 2009
Messages
16,133
is the Default Open Mode of the db (fe and be) set to Shared?
it is best practice to Declare all your variables first before using them:

Dim db As DAO.Database
Dim rs As DAO.Recordset
...
...

and you Explicitly create the Tempvar if it does not exists:

If IsNull(Tempvars("strUserName")) Then
Tempvars.Add "strUserName", ""
End If
 

arnelgp

..forever waiting... waiting for jellybean!
Local time
Today, 23:51
Joined
May 7, 2009
Messages
16,133
It sounds like you are affected by a new and serious bug caused by the latest update.
well your OS version is not among those listed?
 

isladogs

CID VIP
Local time
Today, 16:51
Joined
Jan 14, 2017
Messages
16,081
There are a small but significant number of users affected by this.
Apparently its an unwanted side effect of fixing a long standing security issue.
Unfortunately these serious bugs seem to be getting more frequent.

Apparently it only affects databases on a network share. Try testing a split dB with a local BE.
If that works, it probably confirms that you are affected by the new bug.
 

LGDGlen

Member
Local time
Today, 16:51
Joined
Jun 29, 2021
Messages
216
so i got KB5008212 and servicing stack 10.0.19041.1371 neither of which are listed in that article, but still having a windows security update overnight and now it does this points to that as the issue i'm going to role back the security update and see what happens
 

arnelgp

..forever waiting... waiting for jellybean!
Local time
Today, 23:51
Joined
May 7, 2009
Messages
16,133
i saw my office in the list, but it has no effect on my shared folder?

  • Office LTSC 2021 Version 2108, build 14332.20204
 

The_Doc_Man

Immoderate Moderator
Staff member
Local time
Today, 10:51
Joined
Feb 28, 2001
Messages
22,563
I looked up the KB article, which as usual says nothing except "fixes security issues." However, the link provided by Colin shows that it affects file locks (based on the messages reported). That makes an certain type of sense, in that if the file lock seems to be exclusive (even if it wasn't defined that way), you WOULD see a bunch of issues where you could not share a file.

I have to second the notion of rolling back the patch, which you can do for about 10 days (before the automatic patch recovery files get purged).
 

MattBaldry

Self Taught, Learn from the Forums
Local time
Today, 16:51
Joined
Feb 5, 2019
Messages
158
I have just had this issue and managed to revert to the old version of Office with the below link.


Worked like a charm and now I can use my database again.

~Matt
 

moke123

AWF VIP
Local time
Today, 11:51
Joined
Jan 11, 2013
Messages
2,802
As of 1900 Hrs tonight


An update to the post

Officially From Microsoft​

We have an update as of 2021-12-16 at 19:00, a fix has started to roll out!

New builds with the fix have started rolling out for some channels:

Current Channel: 16.13801.21092
Current Channel (Preview): 16.0.14729.20170
Semi-Annual Channel (Preview): 16.0.14326.20272
Semi-Annual Channel: 16.0.13801.21092
Semi-Annual Channel (Extended): 16.0.13127.21846
Shane Groff - Access Dev Team
So update your systems and things should be back to normal.
 

oleronesoftwares

Passionate Learner
Local time
Today, 08:51
Joined
Sep 22, 2014
Messages
1,118

December 14, 2021—KB5008212 (OS Builds 19041.1415, 19042.1415, 19043.1415, and 19044.1415)​

Try to roll back update, just to be sure that is the cause, or google the error message with regards to the following

Using ms access split database (the ms access version) on windows os kb500........................................15
 

isladogs

CID VIP
Local time
Today, 16:51
Joined
Jan 14, 2017
Messages
16,081
Try to roll back update, just to be sure that is the cause, or google the error message with regards to the following

Using ms access split database (the ms access version) on windows os kb500........................................15
Doing that will reintroduce the security issue that the botched update was designed to fix.
Force an update to the latest version of 365 - Version 2111 Build 14701.20262.
The problem should be fixed
 

Pat Hartman

Super Moderator
Staff member
Local time
Today, 11:51
Joined
Feb 19, 2002
Messages
35,930
Thanks for the info, one of my clients just called me in a panic yesterday. Great start to Christmas week:)
 

MarkK

bit cruncher
Local time
Today, 08:51
Joined
Mar 17, 2004
Messages
7,908
At this site Microsoft describes and acknowledges the issue, and claim a fix is available.

The fix is here, and essentially entails--as Colin observes above--that you update your Office installation, which you can do as follows.

ss_Update_Access.png

I have confirmation this solves the problem.
Mark
 

LGDGlen

Member
Local time
Today, 16:51
Joined
Jun 29, 2021
Messages
216
@MarkK back from my christmas break so thought i'd update this thread, the fix of updating office resolved the issue yes thank you
 

Tina49

Registered User.
Local time
Today, 08:51
Joined
Sep 29, 2011
Messages
34
I'm having this exact issue. My problem is that I did the updates and it didn't fix the issue. Still being locked out if 1 person is using the split database.
 

Gasman

Enthusiastic Amateur
Local time
Today, 16:51
Joined
Sep 21, 2011
Messages
10,346
I'm having this exact issue. My problem is that I did the updates and it didn't fix the issue. Still being locked out if 1 person is using the split database.
Every user has to be updated?
 

Users who are viewing this thread

Top Bottom