I am using LR for an ISMS application which after some transaction, picks up the file from the client machine and puts it on the server.
I am using WINSOCKS protocol for recording the scripts. The scripts gets recorded successfully, however when i play it, 2 problems occur.
1) I get and error in the log saying that
vuser_init.c(25): Mismatch (expected 573 bytes, 622 bytes actually received).
I tried using the function
with different time settings but i am getting the same error again and again.
2) The file gets picked from the client machine but it vanishes somewhere [img]images/icons/smile.gif[/img] ...i tried searching for it on both the client and the server machine, but couldnt find it.
This just means that different information was received back. It's not an error per se. When you run play back you might want to capture the server return. You can then compare buf1 to what was actually received.
As previously said, the Mismatch message is not an error. it tells you that the buffer sent or reveived didn't match the number of bytes that you have in your Data.ws file.
Following the message, you'll see in the execution log the data that was received in the buffer (new data sent by the server). A couple of lines later, the ===expected buffer (which is the one in the Data.ws file)will show the data that was supposed to have.
2) how do you know the file is being picked up? Can you see the file data in the execution log? Make sure you can verify that the file is being really picked up otherwise you won't see it at all.
The file is definetly getting picked as i have the access to both the client machine as well as the server machine. Every time i run the test i see that the file i transferred is not existing anymore. That suggets that it is getting picked, moreover i can see that in the log as well as the buffer.
Did you correlate your script yet? Winsocks is a pain because it records the raw data stream, and as such upon playback the buffers will probably not match up and you will get errors. This can happen even with static data.
Here is a trick, record your script and save it. Record it again and save it. Now use the compare tool and see what data chunks in the data buffer changes and then put in your correlation points. Go to the Mercury Support site and do a Knowledgebase search on "Winsock Correlation". It will provide a nice little document on what I am talking about.