Quote:
Originally Posted by guesswho-.-
Thats not a proper fix tho... Idk what is more sad, the fact that there are people selling a half-assed solution like that or the ones who pay for it.
lol
|
Quote:
Originally Posted by lelay123
It's always say Critical Error SP_SIEGE_INFO_R Call fail please help me to fix this already tried all the script but didnt work! hope you guys can help me
|
IIRC on A3/A9 files the proper fix for one of the Siege related errors that I recall fixing was the wrong integer size set in one of the MSSQL stored procedures.
You can use SQL Server Profiler (not included with MSSQL Express IIRC) to view which queries are being called along with their arguments. Then use that to try calling the stored procedures with the exact arguments being passed to find out which SP is failing.
After you know which SP is failing, debug it to figure out why. If it's the date issue I recall fixing, you will just have to increase the integer size of either one of the SP's parameters or one of its variables. Can't recall which.
Really doubt this guy helps you with something, more like scam.
