Someone put an ad on CL looking for a tutor. This guy's story ran something like this: he had been working as a landscaper, then as a grunt in an animal shelter - neither of which paid particularly well. He volunteered to maintain the animal shelter's website. This gave him enough experience with HTML and CSS to get a 'real' job with a startup. He spent most of his time working on the HTML formatting for email messages, however at various points he was expected to work on 'back end' stuff, which was written in Visual Basic and SQL Server. He had no idea what he was doing.
In this circumstance, there's no reason he should have - he had never taken any computer courses beyond perhaps an Intro to Programming. The employer's expectations were grossly unrealistic.
What I showed him with SQL Server and Visual Basic was enough for him to know he needed to take some classes, which he did. He switched jobs, explaining his circumstances to his new employer, which had more realistic expectations. Having an experienced person trying to mentor this person at Day 1 would have been a misuse of both people's time.
There were occasions where I was mentoring someone that turned out to be completely useless. I ran into someone with a rather impressive college education that couldn't program at all. Once I realized that, I pushed him out. If I was 'stuck with him' I wouldn't waste my time. I have quit in circumstances where I was expected to work with people that couldn't contribute.
In this situation you are going to have to 'go your own way'. As long as you remain in the job that you're in, you'll have to 'hack the system' - figuring out what you can. Generally, however, if you can't find something productive to do right away, they'll let you go.
If you are in a largish organization, and there are projects of varying complexity, see what you can do on simpler projects. If you don't understand 'web services' or 'stored procedures' or 'jquery' just start reading up on them and practicing. Rather than leaning on others, start nibbling away at what you don't understand, and start building up a library of sample code and demos to chart your progress.