May 27, 2009 at 7:50 pm
Started seeing this error on one of my DB's after a disk blip on our SAN over the weekend. This is an upgraded DB from 2000 to 2005. The integrity check was running fine until the outtage.
More info: Sometime last Saturday 5-23-09 we lost connectivity to our SAN from our SQL cluster for about 10-15 seconds and in that time SQL went down. It came backup fine, but with several jobs failing this being one of them. Other failing jobs are reindexing jobs.
I have tried dbcc checkdb ('MIMS', Allow_Data_Loss) with no success.
Here is the output from a DBCC CHECKDB ('MIMS')
DBCC results for 'MIMS'.
Service Broker Msg 9675, State 1: Message Types analyzed: 14.
Service Broker Msg 9676, State 1: Service Contracts analyzed: 6.
Service Broker Msg 9667, State 1: Services analyzed: 3.
Service Broker Msg 9668, State 1: Service Queues analyzed: 3.
Service Broker Msg 9669, State 1: Conversation Endpoints analyzed: 0.
Service Broker Msg 9674, State 1: Conversation Groups analyzed: 0.
Service Broker Msg 9670, State 1: Remote Service Bindings analyzed: 0.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=859202161,referenced_minor_id=42) of row (class=0,object_id=990678627,column_id=0,referenced_major_id=859202161,referenced_minor_id=42) in sys.sql_dependencies does not have a matching row (object_id=859202161,column_id=42) in sys.columns.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=859202161,referenced_minor_id=43) of row (class=0,object_id=990678627,column_id=0,referenced_major_id=859202161,referenced_minor_id=43) in sys.sql_dependencies does not have a matching row (object_id=859202161,column_id=43) in sys.columns.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=859202161,referenced_minor_id=47) of row (class=0,object_id=990678627,column_id=0,referenced_major_id=859202161,referenced_minor_id=47) in sys.sql_dependencies does not have a matching row (object_id=859202161,column_id=47) in sys.columns.
Msg 8992, Level 16, State 1, Line 1
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=859202161,referenced_minor_id=48) of row (class=0,object_id=990678627,column_id=0,referenced_major_id=859202161,referenced_minor_id=48) in sys.sql_dependencies does not have a matching row (object_id=859202161,column_id=48) in sys.columns.
CHECKDB found 0 allocation errors and 4 consistency errors not associated with any single object.
DBCC results for 'sys.sysrowsetcolumns'.
There are 1261 rows in 16 pages for object "sys.sysrowsetcolumns".
DBCC results for 'sys.sysrowsets'.
There are 172 rows in 2 pages for object "sys.sysrowsets".
DBCC results for 'sysallocunits'.
There are 190 rows in 4 pages for object "sysallocunits".
DBCC results for 'sys.sysfiles1'.
There are 2 rows in 1 pages for object "sys.sysfiles1".
DBCC results for 'sys.syshobtcolumns'.
There are 1261 rows in 17 pages for object "sys.syshobtcolumns".
DBCC results for 'sys.syshobts'.
There are 172 rows in 2 pages for object "sys.syshobts".
DBCC results for 'sys.sysftinds'.
There are 0 rows in 0 pages for object "sys.sysftinds".
DBCC results for 'sys.sysserefs'.
There are 190 rows in 1 pages for object "sys.sysserefs".
DBCC results for 'sys.sysowners'.
There are 57 rows in 1 pages for object "sys.sysowners".
DBCC results for 'sys.sysprivs'.
There are 682 rows in 6 pages for object "sys.sysprivs".
DBCC results for 'sys.sysschobjs'.
There are 382 rows in 8 pages for object "sys.sysschobjs".
DBCC results for 'sys.syscolpars'.
There are 1671 rows in 28 pages for object "sys.syscolpars".
DBCC results for 'sys.sysnsobjs'.
There are 1 rows in 1 pages for object "sys.sysnsobjs".
DBCC results for 'sys.syscerts'.
There are 0 rows in 0 pages for object "sys.syscerts".
DBCC results for 'sys.sysxprops'.
There are 0 rows in 0 pages for object "sys.sysxprops".
DBCC results for 'sys.sysscalartypes'.
There are 41 rows in 1 pages for object "sys.sysscalartypes".
DBCC results for 'sys.systypedsubobjs'.
There are 0 rows in 0 pages for object "sys.systypedsubobjs".
DBCC results for 'sys.sysidxstats'.
There are 452 rows in 10 pages for object "sys.sysidxstats".
DBCC results for 'sys.sysiscols'.
There are 687 rows in 6 pages for object "sys.sysiscols".
DBCC results for 'sys.sysbinobjs'.
There are 23 rows in 1 pages for object "sys.sysbinobjs".
DBCC results for 'sys.sysobjvalues'.
There are 673 rows in 158 pages for object "sys.sysobjvalues".
DBCC results for 'sys.sysclsobjs'.
There are 57 rows in 1 pages for object "sys.sysclsobjs".
DBCC results for 'sys.sysrowsetrefs'.
There are 0 rows in 0 pages for object "sys.sysrowsetrefs".
DBCC results for 'sys.sysremsvcbinds'.
There are 0 rows in 0 pages for object "sys.sysremsvcbinds".
DBCC results for 'sys.sysxmitqueue'.
There are 0 rows in 0 pages for object "sys.sysxmitqueue".
DBCC results for 'sys.sysrts'.
There are 1 rows in 1 pages for object "sys.sysrts".
DBCC results for 'sys.sysconvgroup'.
There are 0 rows in 0 pages for object "sys.sysconvgroup".
DBCC results for 'sys.sysdesend'.
There are 0 rows in 0 pages for object "sys.sysdesend".
DBCC results for 'sys.sysdercv'.
There are 0 rows in 0 pages for object "sys.sysdercv".
DBCC results for 'sys.syssingleobjrefs'.
There are 231 rows in 1 pages for object "sys.syssingleobjrefs".
DBCC results for 'sys.sysmultiobjrefs'.
There are 1379 rows in 11 pages for object "sys.sysmultiobjrefs".
DBCC results for 'sys.sysdbfiles'.
There are 2 rows in 1 pages for object "sys.sysdbfiles".
DBCC results for 'sys.sysguidrefs'.
There are 0 rows in 0 pages for object "sys.sysguidrefs".
DBCC results for 'sys.sysqnames'.
There are 91 rows in 1 pages for object "sys.sysqnames".
DBCC results for 'sys.sysxmlcomponent'.
There are 93 rows in 1 pages for object "sys.sysxmlcomponent".
DBCC results for 'sys.sysxmlfacet'.
There are 97 rows in 1 pages for object "sys.sysxmlfacet".
DBCC results for 'sys.sysxmlplacement'.
There are 17 rows in 1 pages for object "sys.sysxmlplacement".
DBCC results for 'sys.sysobjkeycrypts'.
There are 0 rows in 0 pages for object "sys.sysobjkeycrypts".
DBCC results for 'sys.sysasymkeys'.
There are 0 rows in 0 pages for object "sys.sysasymkeys".
DBCC results for 'sys.syssqlguides'.
There are 0 rows in 0 pages for object "sys.syssqlguides".
DBCC results for 'sys.sysbinsubobjs'.
There are 0 rows in 0 pages for object "sys.sysbinsubobjs".
DBCC results for 'tblMappedColumns'.
There are 0 rows in 0 pages for object "tblMappedColumns".
DBCC results for 'tlkpIndustryAlias'.
There are 27 rows in 1 pages for object "tlkpIndustryAlias".
DBCC results for 'tblTemp_Letter'.
There are 5066 rows in 857 pages for object "tblTemp_Letter".
DBCC results for 'tblLetter_v140'.
There are 99 rows in 3 pages for object "tblLetter_v140".
DBCC results for 'tblBackOrder'.
There are 165 rows in 5 pages for object "tblBackOrder".
DBCC results for 'X_tblLetter'.
There are 59 rows in 1 pages for object "X_tblLetter".
DBCC results for 'tlkpProdStartDate'.
There are 4 rows in 1 pages for object "tlkpProdStartDate".
DBCC results for 'tlkpstateprovalias'.
There are 581 rows in 11 pages for object "tlkpstateprovalias".
DBCC results for 'tlkpcityalias'.
There are 311 rows in 6 pages for object "tlkpcityalias".
DBCC results for 'tblCompanyShippingAddr'.
There are 19 rows in 1 pages for object "tblCompanyShippingAddr".
DBCC results for 'tblSecurity'.
There are 1 rows in 1 pages for object "tblSecurity".
DBCC results for 'X_tblLetterCorp'.
There are 15 rows in 1 pages for object "X_tblLetterCorp".
DBCC results for 'tlkpVolume'.
There are 5 rows in 1 pages for object "tlkpVolume".
DBCC results for 'x_tlkpMIMSUsers'.
There are 3 rows in 1 pages for object "x_tlkpMIMSUsers".
DBCC results for 'trelLitSource'.
There are 2 rows in 1 pages for object "trelLitSource".
DBCC results for 'tlkpProdInterest'.
There are 4 rows in 1 pages for object "tlkpProdInterest".
DBCC results for 'tblFile'.
There are 352 rows in 8 pages for object "tblFile".
DBCC results for 'tlkpHear'.
There are 9 rows in 1 pages for object "tlkpHear".
DBCC results for 'dtproperties'.
There are 21 rows in 1 pages for object "dtproperties".
DBCC results for 'tlkpProductPurchased'.
There are 5 rows in 1 pages for object "tlkpProductPurchased".
DBCC results for 'trelProdSource'.
There are 2 rows in 1 pages for object "trelProdSource".
DBCC results for 'tblLiterature'.
There are 625 rows in 53 pages for object "tblLiterature".
DBCC results for 'tblEditEmail'.
There are 3 rows in 1 pages for object "tblEditEmail".
DBCC results for 'sys.queue_messages_1076250939'.
There are 0 rows in 0 pages for object "sys.queue_messages_1076250939".
DBCC results for 'tblProduct'.
There are 194 rows in 2 pages for object "tblProduct".
DBCC results for 'sys.queue_messages_1108251053'.
There are 0 rows in 0 pages for object "sys.queue_messages_1108251053".
DBCC results for 'sys.queue_messages_1140251167'.
There are 0 rows in 0 pages for object "sys.queue_messages_1140251167".
DBCC results for 'tblcid'.
There are 0 rows in 0 pages for object "tblcid".
DBCC results for 'x_SurveyForm'.
There are 0 rows in 0 pages for object "x_SurveyForm".
DBCC results for 'tblSICimport'.
There are 0 rows in 0 pages for object "tblSICimport".
DBCC results for 'tblRequest'.
There are 356620 rows in 25486 pages for object "tblRequest".
DBCC results for 'tblgeneral'.
There are 1 rows in 1 pages for object "tblgeneral".
DBCC results for 'tbltemp'.
There are 0 rows in 0 pages for object "tbltemp".
DBCC results for 'x_HoldWebCompany'.
There are 938 rows in 188 pages for object "x_HoldWebCompany".
DBCC results for 'x_Results'.
There are 612 rows in 41 pages for object "x_Results".
DBCC results for 'x_HoldWebRequest'.
There are 1437 rows in 96 pages for object "x_HoldWebRequest".
DBCC results for 'tbltemp_xls'.
There are 2938 rows in 331 pages for object "tbltemp_xls".
DBCC results for 'ISCOM932'.
There are 0 rows in 1 pages for object "ISCOM932".
DBCC results for 'tblWebRequest'.
There are 0 rows in 0 pages for object "tblWebRequest".
DBCC results for 'x_HoldWebRequestError'.
There are 64 rows in 7 pages for object "x_HoldWebRequestError".
DBCC results for 'x_HoldWebCompanyError'.
There are 65 rows in 13 pages for object "x_HoldWebCompanyError".
DBCC results for 'tblPublisherError'.
There are 0 rows in 0 pages for object "tblPublisherError".
DBCC results for 'tccom001'.
There are 1418 rows in 89 pages for object "tccom001".
DBCC results for 'tbltemp_SA'.
There are 7 rows in 1 pages for object "tbltemp_SA".
DBCC results for 'x_tblWebRequestError'.
There are 0 rows in 0 pages for object "x_tblWebRequestError".
DBCC results for 'tblSource'.
There are 433 rows in 4 pages for object "tblSource".
DBCC results for 'x_tblWebCompanyError'.
There are 0 rows in 0 pages for object "x_tblWebCompanyError".
DBCC results for 'tblFieldErrors'.
There are 21 rows in 1 pages for object "tblFieldErrors".
DBCC results for 'tblImportErrors'.
There are 16 rows in 1 pages for object "tblImportErrors".
DBCC results for 'tblUtility'.
There are 1 rows in 1 pages for object "tblUtility".
DBCC results for 'tblMIMSColumns'.
There are 19 rows in 1 pages for object "tblMIMSColumns".
DBCC results for 'tblPublisherColumns'.
There are 896 rows in 24 pages for object "tblPublisherColumns".
DBCC results for 'tblPublisherName'.
There are 32 rows in 4 pages for object "tblPublisherName".
DBCC results for 'tblWebCompany'.
There are 0 rows in 0 pages for object "tblWebCompany".
DBCC results for 'tlkpLanguage'.
There are 10 rows in 1 pages for object "tlkpLanguage".
DBCC results for 'trelProdLit'.
There are 375 rows in 2 pages for object "trelProdLit".
DBCC results for 'tlkpCountryLanguage'.
There are 52 rows in 1 pages for object "tlkpCountryLanguage".
DBCC results for 'tlkpImportStatus'.
There are 18 rows in 1 pages for object "tlkpImportStatus".
DBCC results for 'tlkpNumbEmp'.
There are 32 rows in 1 pages for object "tlkpNumbEmp".
DBCC results for 'tlkpCountryAlias'.
There are 264 rows in 2 pages for object "tlkpCountryAlias".
DBCC results for 'tblCompany'.
There are 130035 rows in 26024 pages for object "tblCompany".
DBCC results for 'tlkpOrigin'.
There are 36 rows in 1 pages for object "tlkpOrigin".
DBCC results for 'tcmcs010'.
There are 252 rows in 3 pages for object "tcmcs010".
DBCC results for 'tlkpIndustry'.
There are 25 rows in 1 pages for object "tlkpIndustry".
CHECKDB found 0 allocation errors and 4 consistency errors in database 'MIMS'.
DBCC execution completed. If DBCC printed error messages, contact your system administrator.
This is the error from the job log.
Microsoft(R) Server Maintenance Utility (Unicode) Version 9.0.3042
Report was generated on "chn-cl-sql2005\SQL2K5".
Maintenance Plan: F-M Db's
Duration: 00:01:38
Status: Warning: One or more tasks failed..
Details:
Check Database Integrity (chn-cl-sql2005\SQL2K5)
Check Database integrity on Local server connection
Databases: FLM,INF_PC_DOM,INF_PC_REP,Insight_v50_0_84822933,ISCM,MIMS
Include indexes
Task start: 2009-05-27T01:00:07.
Task end: 2009-05-27T01:01:43.
Failed:(-1073548784) Executing the query "DBCC CHECKDB WITH NO_INFOMSGS
" failed with the following error: "Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=859202161,referenced_minor_id=42) of row (class=0,object_id=990678627,column_id=0,referenced_major_id=859202161,referenced_minor_id=42) in sys.sql_dependencies does not have a matching row (object_id=859202161,column_id=42) in sys.columns.
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=859202161,referenced_minor_id=43) of row (class=0,object_id=990678627,column_id=0,referenced_major_id=859202161,referenced_minor_id=43) in sys.sql_dependencies does not have a matching row (object_id=859202161,column_id=43) in sys.columns.
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=859202161,referenced_minor_id=47) of row (class=0,object_id=990678627,column_id=0,referenced_major_id=859202161,referenced_minor_id=47) in sys.sql_dependencies does not have a matching row (object_id=859202161,column_id=47) in sys.columns.
Check Catalog Msg 3853, State 1: Attribute (referenced_major_id=859202161,referenced_minor_id=48) of row (class=0,object_id=990678627,column_id=0,referenced_major_id=859202161,referenced_minor_id=48) in sys.sql_dependencies does not have a matching row (object_id=859202161,column_id=48) in sys.columns.
CHECKDB found 0 allocation errors and 4 consistency errors not associated with any single object.
CHECKDB found 0 allocation errors and 4 consistency errors in database 'MIMS'.". Possible failure reasons: Problems with the query, "ResultSet" property not set correctly, parameters not set correctly, or connection not established correctly.
Keith
-.- ..-. --... . -..- ---
SELECT * FROM management WHERE clue > 0;
May 27, 2009 at 11:07 pm
you cant run repair_allow_data_loss as its not suggesting you to do that .
if its not suggesting then its not going to help you .
There is only one object which is corrupt .thi scan be a constraint or something else .
-> first run the dbcc updateusage on the new database that is corrupt and upgraded
-> then run the checkdb again and see if this gives the error.
-> find out what is the object_name for object id 990678627 as this is the only object whose metadata is corrupt .
-> select * from sys.all_objects where object_id =1986106116 .Run this in the context of that database which is
corrupt.
-> if its a constraint drop it and recreate it .if its an index rebuild it .
-> I mean take the decision as per that object .
-> If the table is not very important drop it .
-> If its important then try to extract as many rows as possible and drop it .Later import it back .
-> Other option would be to try and restore an old backup of this database as a different database .
import the old table into new databse which is corrupt .if it cries on constraint then disabel the constraints first
and then import .you will have atleast some data then having nothing .
Abhay Chaudhary
Sr.DBA (MCITP/MCTS :SQL Server 2005/2008 ,OCP 9i)
May 28, 2009 at 3:41 am
Odd. Those normally aren't caused by IO problems but usually by people directly editing the system tables on SQL 2000. Disk issues usually cause more damage than a single missing row.
CheckDB cannot repair these.
Run the following
SELECT Object_Name(990678627)
SELECT Object_Name(859202161)
One of those very likely will be a procedure, view or function. If so, drop it and recreate it and then run checkDB again.
DBCC CHECKDB (< Database Name > ) WITH NO_INFOMSGS, ALL_ERRORMSGS
Also take a look at this article. http://www.sqlservercentral.com/articles/65804/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 28, 2009 at 11:03 am
Thanks for the responses. I will give the suggestions a try and report back. I'm a very green SQL admin but I have to learn somewhere.
The DB in questions was a upgrade from SQL2000, but this was done well over a year ago, and we havent had any issues until now.
Thanks again
Keith
-.- ..-. --... . -..- ---
SELECT * FROM management WHERE clue > 0;
May 28, 2009 at 11:45 am
updateusage completed with no errors, a re-run of checkdb still threw the errors. I looked up the Odject_id, and it is a SP. I contacted the DB owner and he is taking a look at the SP to see if he can see whats going on.
Appreciate the help on this!
Keith
-.- ..-. --... . -..- ---
SELECT * FROM management WHERE clue > 0;
May 28, 2009 at 11:58 am
Update usage won't do a thing here. Update usage just fixes the space-used metadata and that's not the problem. The problem is inconsistencies in the schema
No need to analyse the proc. Script it and its permissions out, drop it and then recreate it.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 28, 2009 at 3:18 pm
Sorry if I sound like an idiot here.
I noticed that the first object referenced is a SP (990678627), there is another object referenced "859202161" which is a view. I'm not sure by reading the error if the problem is with the SP, or the view, or both?
The DB owner tells me everything he see's looks fine.
Guess im not really understanding what the error is telling me.
Keith
-.- ..-. --... . -..- ---
SELECT * FROM management WHERE clue > 0;
May 28, 2009 at 3:28 pm
It's telling you that there's a dependency entry for the procedure that references a column that does not exist in the view. (It can't be the other way around because a view cannot depend on a procedure)
There will be no sign of anything wrong in the procedure or the view that anyone would be able to see. The checkDB output is the evidence of the problem.
Script the procedure out, along with all of its permissions. Drop the procedure. Run the creation script and apply all the permissions. That should have fixed the error (run checkDB again to be sure)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 28, 2009 at 4:33 pm
Gail,
Many thanks for your help. I dropped the SP, and recreated it and the DB now passes a checkdb.
Would you have any idea what might cause this type of thing? As of last Friday the jobs were completing without error, then the jobs started failing. Thought it might have been the disk issue, but that might have just been a coincidence. the DB owner says nothing has changed (of course).
Thanks to all that chimed in. Now I'm off to the index issues with other DB's. I'm sure I'll be asking for more help.
Keith
-.- ..-. --... . -..- ---
SELECT * FROM management WHERE clue > 0;
May 28, 2009 at 8:04 pm
keith ,
actually the metadata for you data got corrupt .
I have a question .you said that the there are 2 objects : a view and the SP ...does the table on which the view was created ,exists ..
secondly , i have had 2 cases where DBCC updateusage fixed the corruption when client moved from 2000 to 2005 ..
thats the sole reaon i asked you to run it ..it not only fixes the sapce and reduces the fragmentation but some issues with like this .again there is a KB for this .But its not at the top of my head ..
Regards
Abhay
[OCP 9i , MCITP/MCTS (SQL Server 2005 , 2008)]
Abhay Chaudhary
Sr.DBA (MCITP/MCTS :SQL Server 2005/2008 ,OCP 9i)
May 29, 2009 at 2:09 am
MCHPIS (5/28/2009)
Would you have any idea what might cause this type of thing?
As I mentioned earlier, normally this kind of thing is the result of someone doing direct edits on the system tables. It was not uncommon on SQL 2000 for people to hack the system tables unaware of the mess that they were causing. That doesn't explain why checkDB was clean until now. It's possible that an IO glitch cause this
One other thing. Please check the setting of Page Verify for your user databases. If it's torn page please set it to checksum. Checksum lets checkdb pick up more errors than torn page would have. Being upgraded databases, they're probably torn page.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 29, 2009 at 2:12 am
hi_abhay78 (5/28/2009)
secondly , i have had 2 cases where DBCC updateusage fixed the corruption when client moved from 2000 to 2005 ..
Update usage will fix corruption errors like this
Msg 2508, Level 16, State 3, Line 1
The In-row data RSVD page count for object "Broken1", index ID 0, partition ID 76911687695381, alloc unit ID 76911687695381 (type In-row data) is incorrect. Run DBCC UPDATEUSAGE.
thats the sole reaon i asked you to run it ..it not only fixes the sapce and reduces the fragmentation but some issues with like this .again there is a KB for this .But its not at the top of my head ..
UpdateUsage fixes incorrect space-used metadata. Nothing else. It does not reduce fragmentation, it will not fix schema errors.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 12, 2009 at 11:23 am
Gail,
Thank you! The information you provided was invaluable. I had a procedure causing the stated error. You helped me identify it, and then repair the problem.
Also, thanks for the heads up on the Page Verify setting. My db had been upgraded from SQL 2000, and was set to use TORN_PAGE_DETECTION instead of CHECKSUM.
Excellent information and succinct!
Dave Morse
Sr. Technology Analyst
Santa Barbara County
Public Health Department
June 12, 2009 at 12:10 pm
Pleasure.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 15, 2009 at 8:04 am
Gail, what's the difference between
Page Verify - None
Page Verify - Torn Page Detection
Page Verify - CheckSum
One of my DB is currently set to Page Verify - None, which makes me think it could cause corruption? Well, I read a bit on BOL, and it says Checksum creates a checksum or something, but I'm looking forward for a further explanation.
Thanks,
Cheers,
J-F
Viewing 15 posts - 1 through 15 (of 21 total)
You must be logged in to reply to this topic. Login to reply