I'm afraid I'm not sure when this error started happening as it's been masked by log noise. Just started seeing it though for a number of users (always the same users).
Server Setup:
Windows 2003 Server, Progress 11.2.1 (both 32 bit)
Client Setup:
Windows 7, Progress 11.2 (32 bit).
I've tried updating the client to 11.2.1 but to no avail. Anyone seen the error? Why can it not be formatted for certain users? We use a standard build for client machines.
[2015/03/09@14:57:52.687+0000] P-7592 T-6552 I SRV 50: (742) Login usernum 1015, userid JJones client type ABL , on ENC00944 using TCP/IP IPV4 address 192.168.120.72.
[2015/03/09@14:57:52.687+0000] P-7592 T-6552 I SRV 50: (7129) Usr 1015 set name to JJones.
[2015/03/09@14:57:52.687+0000] P-7592 T-6552 I SRV 50: (7129) Usr 1015 set name to ENC00944.
[2015/03/09@14:57:52.719+0000] P-7592 T-6552 I SRV 50: (7129) Usr 1015 set name to JJones.
[2015/03/09@14:57:55.601+0000] P-7592 T-6552 I SRV 50: (-----) Message number 15247 does not exist in promsgs file
[2015/03/09@14:57:55.601+0000] P-7592 T-6552 I SRV 50: (14658) Previous message sent on behalf of user 1015, server pid 7592, broker pid 12456. (5512)
[2015/03/09@14:57:55.632+0000] P-7592 T-6552 I SRV 50: (-----) Unable to format message number 15247
[2015/03/09@14:57:55.632+0000] P-7592 T-6552 I SRV 50: (14658) Previous message sent on behalf of user 1015, server pid 7592, broker pid 12456. (5512)
Are you pointing to a PROMSGS file in your progress.ini?
This is the message (from $DLC/prohelp/msgdata/msg305) from a 10.2B installation so this is not a new 11.x message.
15247 "Cannot set : (15247)" "Update to the property or field is not allowed. This can happen if the given object only provides read-only access to the property based on its state." "" ""
Shouldn't be pointing at one but I will check the offending machines.
Difficulties reading PROMSGS are often a symptom of "virus scanner"
malware being installed on Windows.
The so-called "cure" is generally worse than the disease.
--
Tom Bascom
603 396 4886
tom@greenfieldtech.com
Thanks Tom, although in this case we only get the problem when they log on to the application and no other time. All other messages seem to work ok. It suggests that it's looking at an out of date promsgs file.