I am trying to find out when Kohsuke created Hudson and when the first version of Hudson was released, but I can't find any information on this! Anybody knows?
The first commit on the repository imported to Github seems to be date November 5th, 2006.
But in 2006 at JavaOne Kohsuke stated, that the project started in the summer of 2004.
Related
We have an Access Database-Solution with Frontend and Backend Database running for years.
Now within the last two days problems occurred. E.g.
Set db = DBEngine.OpenDatabase(strDatabasePath, False, True, "MS Access;PWD=" & strPassword)
Does result in Error 3050 - File could not be locked. ONLY when the Backend Database is on a network share (if it's on a local drive everything works as expected).
The error occurs on any share:
a Shared Folder from a Windows PC
a Shared (Samba) Folder on a NAS
independently whether the share is accessed via a UNC-Path (\server\share) or a mapped drive-path.
The error was introduced by a faulty Office Patch (seems it was V2111 - 14701.20240)
In the first version of this post I thought that Windows-Update KB5008212 was causing the problem.
Thanks to #Gustav for identifying the problem.
How do we find out WHEN MS pleases to fix the problem?
From Microsoft:
This is due to today’s (Patch Tuesday) update to Office. The problem
was introduced by a security fix, so it impacts all active versions of
Access. We are working on a fix, and will deliver it as quickly as
possible.
The update has only been set to automatically update a very small
percentage of users, and it looks like we will be able to pause
automatic updates, so it will not propagate.
There will be a page added to the
Fixes or workarounds for recent issues in Access (microsoft.com),
which will then be the place to go
for updates.
These are the updates that introduced the problem:
KB 5002104 for Office 2013
KB 5002099 for Office 2016
Office 2019 Version 1808, build 10381.20020
Office LTSC 2021 Version 2108, build 14332.20204
Microsoft 365 Apps:
Current Channel Version 2111, build 14701.20248
Monthly Enterprise Channel Version 2110, build 14527.20340
Monthly Enterprise Channel Version 2109, build 14430.20380
Semi-Annual Enterprise Channel (Preview) Version 2108, build 14326.20692
Semi-Annual Enterprise Channel Version 2102, build 13801.21086
Semi-Annual Enterprise Channel Version 2008, build 13127.21842
If you did get updated to one of those builds, the only solution
currently is to move back to an earlier build in the channel.
Installing version 2008, in fact, resolved the issue for me. Microsoft just released new builds of versions 2108 and 2112 yesterday, 01/11/2022, that also resolved this same issue for me.
We had the same problems.
Uninstalling Office 365 (32-bits) and re-installing Office 365 (32-bits) from the OfficeWeb-Portal seems to solve the problem.
Ours is not manifesting in the same way. I seem to get a lot of orphaned lock files. Users are having some problems getting in to the databases but usually If I delete the lock file and have them wait 5 minutes, the problem goes away. Since this started it has been a game of running daily backups to a separate file just in case. Major Pain in the you know what. I'll keep an eye on what crops up here. Thanks folks (Yes this is more of a comment than an Answer, but I needed more characters)
We have an Access Database-Solution with Frontend and Backend Database running for years.
Now within the last two days problems occurred. E.g.
Set db = DBEngine.OpenDatabase(strDatabasePath, False, True, "MS Access;PWD=" & strPassword)
Does result in Error 3050 - File could not be locked. ONLY when the Backend Database is on a network share (if it's on a local drive everything works as expected).
The error occurs on any share:
a Shared Folder from a Windows PC
a Shared (Samba) Folder on a NAS
independently whether the share is accessed via a UNC-Path (\server\share) or a mapped drive-path.
The error was introduced by a faulty Office Patch (seems it was V2111 - 14701.20240)
In the first version of this post I thought that Windows-Update KB5008212 was causing the problem.
Thanks to #Gustav for identifying the problem.
How do we find out WHEN MS pleases to fix the problem?
From Microsoft:
This is due to today’s (Patch Tuesday) update to Office. The problem
was introduced by a security fix, so it impacts all active versions of
Access. We are working on a fix, and will deliver it as quickly as
possible.
The update has only been set to automatically update a very small
percentage of users, and it looks like we will be able to pause
automatic updates, so it will not propagate.
There will be a page added to the
Fixes or workarounds for recent issues in Access (microsoft.com),
which will then be the place to go
for updates.
These are the updates that introduced the problem:
KB 5002104 for Office 2013
KB 5002099 for Office 2016
Office 2019 Version 1808, build 10381.20020
Office LTSC 2021 Version 2108, build 14332.20204
Microsoft 365 Apps:
Current Channel Version 2111, build 14701.20248
Monthly Enterprise Channel Version 2110, build 14527.20340
Monthly Enterprise Channel Version 2109, build 14430.20380
Semi-Annual Enterprise Channel (Preview) Version 2108, build 14326.20692
Semi-Annual Enterprise Channel Version 2102, build 13801.21086
Semi-Annual Enterprise Channel Version 2008, build 13127.21842
If you did get updated to one of those builds, the only solution
currently is to move back to an earlier build in the channel.
Installing version 2008, in fact, resolved the issue for me. Microsoft just released new builds of versions 2108 and 2112 yesterday, 01/11/2022, that also resolved this same issue for me.
We had the same problems.
Uninstalling Office 365 (32-bits) and re-installing Office 365 (32-bits) from the OfficeWeb-Portal seems to solve the problem.
Ours is not manifesting in the same way. I seem to get a lot of orphaned lock files. Users are having some problems getting in to the databases but usually If I delete the lock file and have them wait 5 minutes, the problem goes away. Since this started it has been a game of running daily backups to a separate file just in case. Major Pain in the you know what. I'll keep an eye on what crops up here. Thanks folks (Yes this is more of a comment than an Answer, but I needed more characters)
I am relatively new to programming and have been wanting to delve into the back-end development. I have started to try and learn mySQL. The main issue I am running into is the fact that mySQL doesn't seem to be updated for VS 2020? I am using the newest version and during the mySQL install it says it requires 2015/17 or 19 to be installed. The issue I have is I cannot find a 2019 version of vs on their website. The download link just automatically downloads the newest version. Does anyone have any suggestions on what I can do? I am completely lost at this point. Any help is appreciated!
After updating to the 21st of June update for Visual studio 2017, I'm no longer able to build my project.
I'm getting a BadImageException, the signature is incorrect on Microsoft.CodeAnalysis.
I've tried to clean solution, reboot computer, repair visual studio 2017 (and resharper) (in that order).
I can build in release but I can not build in debug. Obviously, this is a problem for me.
How can I undo the latest visual studio 2017 update? In visual studio 2015 you used to be able to simply undo the updates but in visual studio 2017 this seems to be obscured.
A bit of a dead question but I resolved this by simply uninstalling the entire installation and reinstalling it (including the update) and that resolved it for me.
I have a few projects that use MySQL Connector for .NET, either directly or through NHibernate.
Very simple question: in order to avoid maintaining the Mysql.Data.dll assembly on every project and for keeping up-to-date with the upstream development, does anyone provide a maintained MySQL Connector for .NET/Mono package for openSUSE?
It would go through YaST just fine.
If "no one yet" is the answer, I'll simply do gacutil -i Mysql.Data.dll as root. But an RPM could be finer :)
As of Dec 2014 a connector RPM exists, but not yet available in official Yast distribution repository. Maybe in a separate community repository...
No one yet :-)
Al least http://software.opensuse.org/ doesn't list any packages for it, and that is usually very exhaustive.