.Net API version - Have created test account and also have production account but get incomplete sign up error

[fountain...@gmail.com]

Hello,

I have been struggling with this for some time so your help is much appreciated in advance.

I am also using the C#.Net API wrapper which I have been able to understand and is now up and running. Although I am getting the error: 

Failed to get campaigns. Exception says "An API exception has occurred. See ApiException and InnerException fields for more details.""[QuotaCheckError.INCOMPLETE_SIGNUP @ ; trigger:'']" 

Here are the steps that I have followed.

1. I have created a test account te...@testdomain.com
2. I have created a MCC account for both Production (#MCC1) and Test account (#MCC2)
3. I have created a production developer token against #MCC1 (pending approval, and does not matter as mostly focusing on testing at the moment)
4. I have added the production developer token to the web.config
5. I have added the Client Customer ID, The oAuth2ClientID and oAuth2ClientSecret from the test account to the web.config

I can do the authentication just fine and I successful get the authorisation login. After that and once I get to execute I get the Incomplete_Signup error.

Also, when using the handy oAuthTokenGenerator with the clientID and secret from the test account, I get an exception:

System.Net.HttpListenerException was unhandled

  HResult=-2147467259

  Message=Access is denied

  Source=System

  ErrorCode=5

  NativeErrorCode=5

  

I am puzzled. Shouldn't this be working? I followed the documentation to the letter and I guess it should be working. Let me know if you need any IDs for investigation.

Kind regards.

[Ray Tsang (AdWords API Team)]

Hi,

Please carefully follow all steps in the Incomplete Signup error troubleshooting guide.

Thanks,

Ray

[Zweitze]

Also, when using the handy oAuthTokenGenerator with the clientID and secret from the test account, I get an exception:

System.Net.HttpListenerException was unhandled

Are you running on Windows Server 2008 or higher, or Windows Vista or higher? Then try this:
- Right-click on the EXE
- Select "Run as administrator"
- Confirm the UAC

Op dinsdag 12 augustus 2014 01:04:08 UTC+2 schreef fountain...@gmail.com: