Click title for link...
WSVR0100W: An error occurred initializing, 2.13.2006.CWS_DEMO.GlobalMessageLoggerEAR
com.ibm.etools.archive.exception.ArchiveRuntimeException: Invalid resources path:
The filename, even though it was only 210 characters, seems to be too long. Since NTFS will support 255 characters, I would say this is a WebSphere limitation.
Reducing the path to 184 fixed the problem so the limit is somewhere between 184 & 209.
Thursday, February 23, 2006
Tuesday, February 21, 2006
Access & CVS
after checking a ms-access database out form cvs, one of the forms was broken.
within the form, I'd use the Microsoft common dialog to browse for a file. When checked out of CVS, this returned an automation error -2147467259, which was not terribly useful seeing as it only indicates an "Unknown Error"
As it turns out, for some reason the MS common dialog was stripped off of the forms at some point in the process. I simply re-created these and off it went.
within the form, I'd use the Microsoft common dialog to browse for a file. When checked out of CVS, this returned an automation error -2147467259, which was not terribly useful seeing as it only indicates an "Unknown Error"
As it turns out, for some reason the MS common dialog was stripped off of the forms at some point in the process. I simply re-created these and off it went.
Subscribe to:
Posts (Atom)
The Database is not accessible after creating Always On Availability Group
Having created a fully functional SQL Server Always On Availability Group, I connect using SSMS. Upon trying to expand the database, I get ...
