2

I created timer job in dev environment. It is simple one that targets list items and sends communication. It works fine in dev. Before moving it to the other farm I changed all hardcoded url's to reflect other farm setup. Then created .wsp file:

  • right click the project and select Clean
  • changed the soulution configuration to Release > any CPU
  • deployed to target farm using steps from this post

When I run the timer it fails with following error:
The Web application at http://developmentEnvironmentURL/Sites/TestSite/ could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.

How to correctly prepare this timer job to be moved to different farm?

Edit: When I go to solution properties and trying to change Site URL following error pops up: Property value is not valid: Remote SharePoint site connections are not supported. (even when Server connection is set to Ofline)

Edit 2: When I search entire solution for /Sites/TestSite/ or developmentEnvironmentURL/ (part of the error url) it is not found.

  • Check the solution properties, there is a field where you can change the destination url. That url is where the solution will be deployed – Marco Aug 11 '16 at 15:12
  • I wouldn't hard code URLs at all. Use the SPContext to get the URL of the farm you're in and use that instead. – Erin L Aug 11 '16 at 15:18
  • 1
    SPContext is not defined in timer jobs – Robert Lindgren Aug 11 '16 at 15:37
  • When I go to solution properties and trying to change Site URL following error pops up: Property value is not valid: Remote SharePoint site connections are not supported. – Ulee Aug 11 '16 at 16:31
  • You may refer to this article. – Mark L Aug 12 '16 at 1:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.