Ticket tracking...kinda

[taeratrin]

Alright, it took a bit of fiddling, but it's finally to a point where I can release it to the wild. Behold, LSServiceLog, for all your ticket-tracking needs. OK, well, not all of them. This was designed as a way to track simple configuration/hardware changes for individual computers, and is made to integrate nicely with LS via Actions.

A readme.txt is included which details the install process (you have to create your own DB and table...every attempt I made to do that through code crashed and burned). Follow it to the letter and there shouldn't be any problems.

As always, source code is included (VB.NET 2008). This is a beta. Newer versions with fixes/features will be released in the future. Please report bugs here.

Questions/comments/requests are always welcome.

[taeratrin]

Re-attaching

[AdmJLovejoy]

Can you re-attach?

[taeratrin]

When you created the database, what types did you make the fields?

[taeratrin]

Sorry for the slow response. I have re-attached the file below

[jbcsystech]

Was looking for this type of solution. But it seems the link tot he file is not valid. Do you have an other location it can be downloaded from?

[taeratrin]

I've made several improvements to this program. Most are not noticable, but the program should be more stable and better at error recovery than before. A few minor UI adjustments have been made as well. There will be more in the future.

[taeratrin]

New version : No longer uses SQLDMO (decrease in size)

[taeratrin]

Hmm, not sure on this one. You created the database and table, right? .NET 3.5 installed? Also make sure the Interop.SQLDMO.dll stays in the same directory as LSServiceLog.

It may just not be compatible with Vista (I have no Vista machines here to test with).

[HarkinsIT]

I found this in my application log:

Fault bucket 418225909, type 5
Event Name: CLR20r3
Response: None
Cab Id: 0

Problem signature:
P1: lsservicelog.exe
P2: 1.0.0.0
P3: 494ff964
P4: LSServiceLog
P5: 1.0.0.0
P6: 494ff964
P7: 13
P8: c6
P9: System.InvalidOperationException
P10:

These files may be available here:
C:\Users\username\AppData\Local\Microsoft\Windows\WER\ReportArchive\Report0c52d700

The file referenced above has this in it:

Version=1
EventType=CLR20r3
EventTime=128744564112337279
ReportType=2
Consent=1
UploadTime=128744564113577279
Response.BucketId=418225909
Response.BucketTable=5
Response.type=4
Sig[0].Name=Problem Signature 01
Sig[0].Value=lsservicelog.exe
Sig[1].Name=Problem Signature 02
Sig[1].Value=1.0.0.0
Sig[2].Name=Problem Signature 03
Sig[2].Value=494ff964
Sig[3].Name=Problem Signature 04
Sig[3].Value=LSServiceLog
Sig[4].Name=Problem Signature 05
Sig[4].Value=1.0.0.0
Sig[5].Name=Problem Signature 06
Sig[5].Value=494ff964
Sig[6].Name=Problem Signature 07
Sig[6].Value=13
Sig[7].Name=Problem Signature 08
Sig[7].Value=c6
Sig[8].Name=Problem Signature 09
Sig[8].Value=System.InvalidOperationException
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.0.6001.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=1033
UI[2]=C:\windows\System32\LSServiceLog.exe
UI[3]=LSServiceLog has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
State[0].Key=Transport.DoneStage1
State[0].Value=1
State[1].Key=DataRequest
State[1].Value=Bucket=418225909/nBucketTable=5/nResponse=1/n
FriendlyEventName=Stopped working
ConsentKey=CLR20r3
AppName=LSServiceLog
AppPath=C:\Windows\System32\LSServiceLog.exe
ReportDescription=Stopped working

Not sure if this helps or not.

-Chris