Not really. The 1.5.5000.0 (1.5.50) builds are several months old and many many bugs have already been fixed in them. Especially without an afsd.dmp file to provide a stack trace it would not be worth my time to investigate the cause of this issue.
Jeffrey Altman John Hascall wrote: > Is this kind of thing of any value? > > Problem signature: > Problem Event Name: APPCRASH > Application Name: afsd_service.exe > Application Version: 1.5.5000.0 > Application Timestamp: 487e13a8 > Fault Module Name: MSVCR80.dll > Fault Module Version: 8.0.50727.805 > Fault Module Timestamp: 45d27cd1 > Exception Code: c0000005 > Exception Offset: 000172d7 > OS Version: 6.0.6000.2.0.0.256.4 > Locale ID: 1033 > Additional Information 1: 1be8 > Additional Information 2: 48b515cc25cd7357d1da518e9bdd0b82 > Additional Information 3: a5e1 > Additional Information 4: 83754147814c8703abf135f9f75608c2 > _______________________________________________ > OpenAFS-info mailing list > OpenAFS-info@openafs.org > https://lists.openafs.org/mailman/listinfo/openafs-info
smime.p7s
Description: S/MIME Cryptographic Signature
