Sage accpac web session manager is not installed correctly

How can I verify SM's deployment? Thanks again! Accpac's current web deployment model is a farce, and always has been. It's only use is for Sage's marketing department to say "Yeah, we're web-enabled". And since Sage is entirely rewriting their Web client, any work on the current product is a waste of time. Test and verify that a Accpac is installed and running on that server and b Accpac web deployment has been setup and is actually running.

I have always found a way to not use web deployment, so sorry no other advice than that. Thanks fellas. That verifies that I have performed my due diligence in getting these things working.

While I know I could write an app that calls the components on the server and lets my SOAP client talk to them, that's way out of budget for this project. Thanks for the good luck wishes. You may have already tried this, but here it is anyway: The Accpac Web service is not a stateless service. Opening a session requires a web IIS session to be created and persisted across web service calls. Even though you'd think the session token would be enough, that is not the case.

The web session is implemented through cookie support and the default. Net support for web service calls does not implement cookie support. Assuming you are using. Net as your client it is fairly simple to add cookie support. Just add a CookieContainer to the web service object. For example: using WebServiceSample.

WebService; webServ. CookieContainer ; If you are using another client language you'll have to add cookie support yourself. It's usually not too hard. We did a project on Windows Mobile and we have to manage the cookies ourselves. Took about 10 lines of code. Hope that helps, Chris Zinck, P. Zinck Computer Group. In your experience, would you see what I am seeing without the appropriate modifications?

I ask because I have been asked to stop spending time on this issue, and I am unable to verify myself. The second thing that may be problematic is that I will not be using any language to perform this integration. Thank you for your very insightful response. I never would have thought that was the issue. Did you learn this from anything that Sage published?

So far my searching has come up with absolutely zero documents explaining the peculiarities with the AccPac Webservice. Actually, your issue is exactly what I would have expected without cookie support. It is what we struggled with the first time we used web services. Since the Accpac Session token is tied to the web service session, the first call to the opensession works, but the second call to the web service won't.

This is because the Accpac session token was allocated in the first web session and the second call is actually starting a new web session since it wasn't persisted through the cookie. Hence Accpac says it is an invalid token since the new web session doesn't know anything about the token that was allocated in the previous web session. Since pure SOAP is a stateless protocol, you may not be able to get web session support with your tools.

If the operation you are trying to do can be expressed in a single call, you could implement a web service of your own that calls Accpac, opens a session, does the operation and closes the session. We implemented something similar to this for a client that wanted to update a customer through one web service call. If you can't implement your own web service and you are stuck with a tool that doesn't support an open web session, then you probably can't use web services. The base Accpac Web service definitely needs session support.

The only other thing you could try is changing IIS to use a different method to implement web sessions. By default it's set to use cookies and I think you can use URL support instead.

I haven't tried this before, but it might be worth a look. Chris, Thanks again. I was able to build consumers in ColdFusion and. Net, and both work as soon as I turn on session persistence. Unfortunately neither of these languages are tools the client has purchased. This pretty much borked everything. I'm going to play with a lightweight local.

Join Us! By joining you are opting in to receive e-mail. Promoting, selling, recruiting, coursework and thesis posting is forbidden. Students Click Here. When i print the accpac report am getting this error "Sage Accpac Enterprise Server is not configured correctly" importantly i uninstalled the crystal report server and crystal report as well and in register as well and i re-installed the system manager as well.

Sage Accpac 5. Neither the Crystal report server nor Crystal reports are required if you're not doing web deployment. Try rerunning workstation setup. Do you see anything there that says Accpac? You ran web deployment on that computer and that is why you get the errors. Delete those icons and it should work again. Red Flag This Post Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Close Box. Log In Come Join Us! Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.