Object reference not set to an instance of an object.

Report · Dec 07, 2007

Hello all,
We've been struggling with this problem for a while now. My colleague posted the question here in August, but we haven't heard any suggestions since. Here's the original message:

"We are trying to set up Robosource 3 to support multiple writers. Until recently, there was no need, so the project has resided on local drives. We just upgraded to Robohelp 6."

"I have installed Robosource 3 and SQLExpress on the server (a virtual machine, actually) and set up the database, but whenever I try to connect the local (client) to it, I get the following error:"

"Object reference not set to an instance of an object."

"at SCCAPI.SCCIMPL.SccGetProjPath(Int32 context, Int32 hwnd, String& user, String& ProjName, String& LocalPath, String& AuxProjPath, Boolean bAllowChangePath, Boolean& bNew)"

"Any assistance would be greatly appreciated."

"Thanks "

One person recommended that we check that the RoboSource services are running, which they are.

Adobe's recommendation was to try installing the RoboSource client and server, plus RoboHelp on the same computer. I did this today on our virtual machine and was able to connect to version control successfully, but when I try to connect from my own desktop to the vm, I get the error above.

As my colleague said, any assistance is greatly appreciated.
Sudro[

Report · Dec 12, 2007

Hi Sudro -

How are your local clients trying to access the DB? With RH6/RSC3, the initial access is different than it was in X5. After you have the DB set up (which you have already done), the local client must make the initial access via the RSC3 Explorer. They don't have to actually *do* anything in that session, just make the connection. After they've done that, for any future accesses to the project, they can connect normally through RH.

G

Report · Dec 13, 2007

Thanks! That has resolved the error noted above. Now when we click the "Add to Version Control" selection on the File menu it creates a the folder we designate, but doesn't add the files. We can add them manually using the RoboSource Explorer, but we're not currently confident about the files checking in or out properly from RoboHelp. I'll post again when we figure out where we stand.

Report · Dec 17, 2007

If at all possible, you want to add the project to RSC via *RoboHelp*, not RSC Explorer. For the initial upload of the project into the DB, the normal steps would be:
1. Help administrator creates the RSC DB, sets up User Library, etc.
2. Help author establishes the intial connection to the DB (as you've now done).
3. Help author opens the project in RoboHelp.
4. Help author clicks Add to Version Control toolbar icon (or selects equivalent from menu).
5. In response to query, help author selects the DB for the project.
6. RoboHelp uploads all appropriate files into the DB. When it's done, it leaves all the files in a checked-out state.
7. Help author checks in the files, and voila: you have a working source-controlled project.

I have run into situations where the upload terminated for one reason or another, leaving me with a bunch of files that were still local. Given that some files had successfully been added to RSC, what worked for me in those cases was this:
1. Click on the File Status tab.
2. In the File Status pane, click on the Status column head to sort the files.
3. Select all the files in the list that are NOT source controlled, and then click the "Add to Source Control" icon in the RH toolbar.

HTH,
G