Gemini Community Support Site

This Gemini community support site can be used to find solutions to product issues. You can log in using Open Id, Google Profile and even Facebook. Feel free to ask a question or browse FAQs and documentation. Product tour videos are also available along with how-to videos demonstrating key Gemini capabilities.




Consuming Web Services from Windows Server 2003 **RESOLVED**

api

Hi,

I have some code that creates issues using the REST web services API. It runs fine on my workstation (Windows XP). The same code when executed on Windows 2003 server throws the following exception:

'--' is an unexpected token. The expected token is '>'. Line 81, position 5.

Is there any reason why this would not work on a Windows 2003 server?

Code Listing Below:

const string url = "http://geminiURL.com"; const string userName = "domain\user"; const string apiKey = "xxxxxxxxxx";

        ServiceManager serviceManager = new ServiceManager(url, userName, string.Empty, apiKey, false);

        IssueEN issue = new IssueEN();

        issue.ProjectID = 30; 

        issue.IssueSummary = "IssueSummary";
        issue.IssueLongDesc = "Issue Description";
        issue.IssuePriority = 1;
        issue.IssueResolution = 1;
        issue.IssueSeverity = 1;
        issue.IssueStatus = 1;
        issue.IssueType = 1;
        issue.RiskLevel = 1;
        issue.ReportedBy = 1;

        try
        {
            issue = serviceManager.IssuesService.CreateIssue(issue);
        }
        catch (Exception ex)
        {
            Console.WriteLine(ex.Message);
        }

yu217171
· 1
yu217171
Replies (2)
helpful
0
not helpful

a couple of things to check:

  1. try navigating to one of the services: http://your server/api/admin.ashx. Do you get a welcome message?
  2. Did you configure the ASHX handler to accept all verbs?
If this still fails try using fiddler to check the response from the server:http://www.fiddler2.com/fiddler2/


Saar Cohen
· 5000
Saar Cohen
helpful
0
not helpful

Thanks for pointing me in the right direction. It was an authentication issue to the webservice which I solved by impersonation.


yu217171
· 1
yu217171