Intel's AMT SDK and Visual studio 2005

Intel's AMT SDK and Visual studio 2005

Hello,

I am getting the following error when I'm trying to compile sample discovery from Intel's AMT SDK.

------ Build started: Project: Discovery, Configuration: Debug Win32 ------
Compiling...
DiscoverySample.cpp
c:\intel_amt\samples\discovery\c++\discoverysample.h(16) : fatal error C1083: Cannot open include file: 'SoapCommonDefinitions.h': No such file or directory
Build log was saved at "file://c:\Intel_AMT\Samples\Discovery\c++\Debug\BuildLog.htm"
Discovery - 1 error(s), 0 warning(s)
---------------------

I have followed the guide step by step I have even checked the video series on how to setup Intel's AMT SDK maybe I miss something ... any clue?

44 posts / 0 new
Last post
For more complete information about compiler optimizations, see our Optimization Notice.

Quoting - ph3ar
Hello,

I am getting the following error when I'm trying to compile sample discovery from Intel's AMT SDK.

------ Build started: Project: Discovery, Configuration: Debug Win32 ------
Compiling...
DiscoverySample.cpp
c:intel_amtsamplesdiscoveryc++discoverysample.h(16) : fatal error C1083: Cannot open include file: 'SoapCommonDefinitions.h': No such file or directory
Build log was saved at "file://c:Intel_AMTSamplesDiscoveryc++DebugBuildLog.htm"
Discovery - 1 error(s), 0 warning(s)
---------------------

I have followed the guide step by step I have even checked the video series on how to setup Intel's AMT SDK maybe I miss something ... any clue?

Hello,
Could you let us know which version of the SDK you are using? Did you run the makewsdl.bat script? "makewsdl" creates soap files used in building the samples. In the 5.1 SDK, this bat file is located in the ...CommonGeneratedCodeSoapC++ folder. Also, you did not change the directory structure, did you? In order for the samples to build correctly the SDK structure must not be changed.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Hello,
Could you let us know which version of the SDK you are using? Did you run the makewsdl.bat script? "makewsdl" creates soap files used in building the samples. In the 5.1 SDK, this bat file is located in the ...CommonGeneratedCodeSoapC++ folder. Also, you did not change the directory structure, did you? In order for the samples to build correctly the SDK structure must not be changed.

Hello,

I am using SDK version 5.1, I haven't changed the directory structure.
After running makewsdl.bat script I still get the same error.

Quoting - ph3ar
Hello,

I am using SDK version 5.1, I haven't changed the directory structure.
After running makewsdl.bat script I still get the same error.

Hi ph3ar,

Please verify that you have done the following:

1. Installed the Microsoft Platform SDK - there is a link on page 13 of the User Guide.pdf (see the DOCS folder)for where to go to download it.
2.You have added the environment variable MSSDK with the path for where the Platform SDK is. See page 14 of the User Guide. Note - I think you must reboot after adding an environment variable.
3. You have added the SDK lib folder to your project settings as described on page 14 of the User's Guide.
4. You have added the SDK include folder to your project settings as described on page 13 of the User Guide.
5. You said that you ran the makewsdl.bat file - so all your soap generated files should be there
6. You might try also running the build.bat file that is in the Windows folder - I couldn't tell but perhaps it is building files that are needed by all of the samples. (I ran it and mine is compiling and building successfully)

Please let us know if all this works?

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Hi ph3ar,

Please verify that you have done the following:

1. Installed the Microsoft Platform SDK - there is a link on page 13 of the User Guide.pdf (see the DOCS folder)for where to go to download it.
2.You have added the environment variable MSSDK with the path for where the Platform SDK is. See page 14 of the User Guide. Note - I think you must reboot after adding an environment variable.
3. You have added the SDK lib folder to your project settings as described on page 14 of the User's Guide.
4. You have added the SDK include folder to your project settings as described on page 13 of the User Guide.
5. You said that you ran the makewsdl.bat file - so all your soap generated files should be there
6. You might try also running the build.bat file that is in the Windows folder - I couldn't tell but perhaps it is building files that are needed by all of the samples. (I ran it and mine is compiling and building successfully)

Please let us know if all this works?

Hi,

thank for your reply.
I have followed these steps but I'm still getting the following error:
c:iamtsdkintel amt 5.1 sdk goldwindowscommonthirdpartygsoapgsoapwinhttpx.cpp(24) : fatal error C1083: Cannot open include file: 'winhttp.h': No such file or directory

I have also chmoded the folders and files included on the SDK to be writable...

Quoting - ph3ar

Hi,

thank for your reply.
I have followed these steps but I'm still getting the following error:
c:iamtsdkintel amt 5.1 sdk goldwindowscommonthirdpartygsoapgsoapwinhttpx.cpp(24) : fatal error C1083: Cannot open include file: 'winhttp.h': No such file or directory

I have also chmoded the folders and files included on the SDK to be writable...

Hello,
winhttp.h should be in the Platform SDK. Please ensure you have followed all the instructions in section 4.4 of the User Guide. If the Platform SDK is installed and the paths are setcorrectly you should not get that error.

You are working ona Windows platform, right? Your chmod comment was a little surprising :)

Quoting - Lance Atencio (Intel)

Quoting - ph3ar

Hi,

thank for your reply.
I have followed these steps but I'm still getting the following error:
c:iamtsdkintel amt 5.1 sdk goldwindowscommonthirdpartygsoapgsoapwinhttpx.cpp(24) : fatal error C1083: Cannot open include file: 'winhttp.h': No such file or directory

I have also chmoded the folders and files included on the SDK to be writable...

Hello,
winhttp.h should be in the Platform SDK. Please ensure you have followed all the instructions in section 4.4 of the User Guide. If the Platform SDK is installed and the paths are setcorrectly you should not get that error.

You are working ona Windows platform, right? Your chmod comment was a little surprising :)

Hi,

Just downloaded the SDK again and started anything from scratch (as the windows spirit implies :) ) but I still get this error for winhttp.h .

Unfortunately, I'm working on a Windows platform, I could not find an easier word to describe chmod :)

So what can I do from now on any clue?

Quoting - ph3ar

Hi,

Just downloaded the SDK again and started anything from scratch (as the windows spirit implies :) ) but I still get this error for winhttp.h .

Unfortunately, I'm working on a Windows platform, I could not find an easier word to describe chmod :)

So what can I do from now on any clue?

It sounds to me as though you missed something in the instructions (specifically having to do with your installation and setting up of the Microsoft Platform SDK.) As Lance said, winhttp is part of the Platform SDK. Did you follow the link in the User's Guide and install it? Did you install the .Net Framework 2.0 (with service packs?)

Did you add the MSSDK environment variable set to the folder where your Platform SDK is installedand then did youreboot?

Did you add the Microsoft Platform Platform SDK lib and include folders to your Visual Studio Project directory settings? (in the order which the User's Guide tells you to do so?)

What does the log file say when your build does not work? Visual Studio produces a log file - you may want to include it so that we can take a look.

I just downloaded the 5.1 SDK yesterday and was able to compile it - so you must be missing one, or more of the installation steps. Please go through the steps and verify that you completed all the steps. And also include any log files or screen shots so that we can try to figure out what is missing.

-Thanks,
Gael

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Quoting - ph3ar

Hi,

Just downloaded the SDK again and started anything from scratch (as the windows spirit implies :) ) but I still get this error for winhttp.h .

Unfortunately, I'm working on a Windows platform, I could not find an easier word to describe chmod :)

So what can I do from now on any clue?

It sounds to me as though you missed something in the instructions (specifically having to do with your installation and setting up of the Microsoft Platform SDK.) As Lance said, winhttp is part of the Platform SDK. Did you follow the link in the User's Guide and install it? Did you install the .Net Framework 2.0 (with service packs?)

Did you add the MSSDK environment variable set to the folder where your Platform SDK is installedand then did youreboot?

Did you add the Microsoft Platform Platform SDK lib and include folders to your Visual Studio Project directory settings? (in the order which the User's Guide tells you to do so?)

What does the log file say when your build does not work? Visual Studio produces a log file - you may want to include it so that we can take a look.

I just downloaded the 5.1 SDK yesterday and was able to compile it - so you must be missing one, or more of the installation steps. Please go through the steps and verify that you completed all the steps. And also include any log files or screen shots so that we can try to figure out what is missing.

-Thanks,
Gael

Hi Gael,

Thank for your support below is the output of visual studio:
------ Build started: Project: Discovery, Configuration: Debug Win32 ------
Compiling...
gsoapWinHTTPX.cpp
c:mountiamtsdk51windowscommonthirdpartygsoapgsoapwinhttpx.cpp(24) : fatal error C1083: Cannot open include file: 'winhttp.h': No such file or directory
soapC.cpp
soapClient.cpp
Generating Code...
Compiling...
DiscoverySample.cpp
Generating Code...
Build log was saved at "file://c:mountiamtsdk51WindowsIntel_AMTSamplesDiscoveryc++DebugBuildLog.htm"
Discovery - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Quoting - ph3ar
Hi Gael,

Thank for your support below is the output of visual studio:
------ Build started: Project: Discovery, Configuration: Debug Win32 ------
Compiling...
gsoapWinHTTPX.cpp
c:mountiamtsdk51windowscommonthirdpartygsoapgsoapwinhttpx.cpp(24) : fatal error C1083: Cannot open include file: 'winhttp.h': No such file or directory
soapC.cpp
soapClient.cpp
Generating Code...
Compiling...
DiscoverySample.cpp
Generating Code...
Build log was saved at "file://c:mountiamtsdk51WindowsIntel_AMTSamplesDiscoveryc++DebugBuildLog.htm"
Discovery - 1 error(s), 0 warning(s)
========== Build: 0 succeeded, 1 failed, 0 up-to-date, 0 skipped ==========

Ok.... still pointing to your installation of the Windows Platform SDK. Can you tell me exactly what path you have set your "MSSDK" Environment variable to? And could you please attach the BuildLog.htm? And also provide the link from where you downloaded the Windows Platform SDK from.

Also, as winhttp.h is part of the Plaform SDK, please let us know which path you set inside your Visual Studio Project for the Platform SDK include files? Did you place it first, or last, in the list. As I notedin one of my previous posts, order matters - you must follow the instructions that are in the User's Guide.

Could you tell us also which instructions you followed (Document name and page number?) Are you using the Users Guide in the SDK DOCS forlder? I have also written the instructionsin this thread.

Thanks,
Gael

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - ph3ar

I have checked this video http://www.mefeedia.com/entry/how-to-compile-intel-amt-sdk-sample-code/1... in which the setup of SDK in visual studio is demonstrated.

Next I have used the pdf user guide that is included in Intel's AMT SDK pointing to pages Nr: 13 and 14.

Moreover I have attached the BuildLog.htm and 2 screenshots of the MSSDK" Environment variables.

Also, as winhttp.h is part of the Plaform SDK, please let us know which path you set inside your Visual Studio Project for the Platform SDK include files? I haven't found any information about this? You mean how to open the Intel AMT SDK path from Visual studio or the directory tree of the SDK?

Hi - You included the Visual Studio Project information where you are telling it where to find the Windows SDK Include and Library files. I do not see anything showing anew MSSDK EnvironmentVariable and what path it is set to.

I need to know two things. Did you create a new Environment Variable called MSSDK on your Window's System? And your path looks strange - did you give it a different directory name than what the installation defaulted to? Please also provide the link from where you downloaded the Platform SDK so that we can verify that you did, indeed install the correct product (again, the link is in the User's Guide).

You should have installed the product called: Window Server 2003 SP1 Platform SDK Web Install - this is where the link in the User's Guide takes you. And on my system, it installed the product into the following folder: C:Program FilesMicrosoft Platform SDK for Windows XP SP2 -- so that is the path I set for my MSSDK Environment Variable and I set the Lib and Include files accordingly (.../include and ..../lib)

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Quoting - ph3ar

I have checked this video http://www.mefeedia.com/entry/how-to-compile-intel-amt-sdk-sample-code/1... in which the setup of SDK in visual studio is demonstrated.

Next I have used the pdf user guide that is included in Intel's AMT SDK pointing to pages Nr: 13 and 14.

Moreover I have attached the BuildLog.htm and 2 screenshots of the MSSDK" Environment variables.

Also, as winhttp.h is part of the Plaform SDK, please let us know which path you set inside your Visual Studio Project for the Platform SDK include files? I haven't found any information about this? You mean how to open the Intel AMT SDK path from Visual studio or the directory tree of the SDK?

Hi - You included the Visual Studio Project information where you are telling it where to find the Windows SDK Include and Library files. I do not see anything showing anew MSSDK EnvironmentVariable and what path it is set to.

I need to know two things. Did you create a new Environment Variable called MSSDK on your Window's System? And your path looks strange - did you give it a different directory name than what the installation defaulted to? Please also provide the link from where you downloaded the Platform SDK so that we can verify that you did, indeed install the correct product (again, the link is in the User's Guide).

You should have installed the product called: Window Server 2003 SP1 Platform SDK Web Install - this is where the link in the User's Guide takes you. And on my system, it installed the product into the following folder: C:Program FilesMicrosoft Platform SDK for Windows XP SP2 -- so that is the path I set for my MSSDK Environment Variable and I set the Lib and Include files accordingly (.../include and ..../lib)

Hello Gael,

The link that I have downloaded Window Server 2003 SP1 Platform SDK Web Install ishttp://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4...

I changed the environment variables to visuial studio and windows environment variables, but I still get the same error.
I have uploaded the new screenshot with my configuration.

Thanks-

Attachments: 

AttachmentSize
Download 1a.JPG53.88 KB
Download 2a.JPG55.34 KB
Download 3a.JPG37.57 KB

Quoting - ph3ar

Hello Gael,

The link that I have downloaded Window Server 2003 SP1 Platform SDK Web Install ishttp://www.microsoft.com/downloads/details.aspx?FamilyId=A55B6B43-E24F-4...

I changed the environment variables to visuial studio and windows environment variables, but I still get the same error.
I have uploaded the new screenshot with my configuration.

Thanks-

Ok - those three screenshots look OK if C:Program FilesMicrosoft SDK is actually where the product is installed. Could you verify this? Did you change the default path when you installed it? This is not the folder that the insallation created on my system. Remember: The file that it cannot find is a Window's Platform SDK include file. If you aren't using the correct path, the compiler will not be able to find the include file and you will get an error message.

You did reboot your computer after addeding the MSSDK Environment Variable, correct?

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Ok - those three screenshots look OK if C:Program FilesMicrosoft SDK is actually where the product is installed. Could you verify this? Did you change the default path when you installed it? This is not the folder that the insallation created on my system. Remember: The file that it cannot find is a Window's Platform SDK include file. If you aren't using the correct path, the compiler will not be able to find the include file and you will get an error message.

You did reboot your computer after addeding the MSSDK Environment Variable, correct?

There are 2 version of SDKs version 6.0A and v6.1 in this directory C:Program FilesMicrosoft SDKsWindows and of course this doesn't matches the directory referred to the SDK user guide.

I am lost!

Quoting - ph3ar

There are 2 version of SDKs version 6.0A and v6.1 in this directory C:Program FilesMicrosoft SDKsWindows and of course this doesn't matches the directory referred to the SDK user guide.

I am lost!

Interesting... What OS are you running? You might want to uninstall both and start fresh - your URL is correct, but I think it detects your OS and installs the Platform SDK that is correct for your OS. 6.0A sort of implies 'alpha" to me and maybe 6.1 would be the one to use - although my installation path is totally different so I'm a little confused at that. Where is your winhttp.h file? do both directory structures have the correct include files? You should try correctly setting your MSSDK environment variable and the Visual Studio project directories to point to the install that has the right files.

Also, the directory that the SDK refers to is a generic name - you have to use the directory name for where your installation puts the Platform SDK. It can be a little confusing, but since the product gets installed with different names depending on what OS you are on, I suppose it makes sense to use a name that is generic, for the purpose of an example.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Interesting... What OS are you running? You might want to uninstall both and start fresh - your URL is correct, but I think it detects your OS and installs the Platform SDK that is correct for your OS. 6.0A sort of implies 'alpha" to me and maybe 6.1 would be the one to use - although my installation path is totally different so I'm a little confused at that. Where is your winhttp.h file? do both directory structures have the correct include files? You should try correctly setting your MSSDK environment variable and the Visual Studio project directories to point to the install that has the right files.

Also, the directory that the SDK refers to is a generic name - you have to use the directory name for where your installation puts the Platform SDK. It can be a little confusing, but since the product gets installed with different names depending on what OS you are on, I suppose it makes sense to use a name that is generic, for the purpose of an example.

Also - what version of Microsoft Visual C/C++ are you using? You need to be running MS Visual Studio 2005 in order to build the SDK Samples.. I found this note on the Download website:

To build the C/C++ samples, you must have a C/C++ compiler. If you are using Microsoft Visual C/C++, run it at least once before installing the SDK. This will ensure that the environment variables are correctly configured. To build the Visual Basic samples, you must have Microsoft Visual Basic. This SDK does not support working with Microsoft Visual C/C++, 6.0 as support for VC 6.0 has ended. The last SDK that will work with VC 6.0 is the February 2003 Edition, you can order a CD on the fulfillment site. Side by side installations are not supported.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Interesting... What OS are you running? You might want to uninstall both and start fresh - your URL is correct, but I think it detects your OS and installs the Platform SDK that is correct for your OS. 6.0A sort of implies 'alpha" to me and maybe 6.1 would be the one to use - although my installation path is totally different so I'm a little confused at that. Where is your winhttp.h file? do both directory structures have the correct include files? You should try correctly setting your MSSDK environment variable and the Visual Studio project directories to point to the install that has the right files.

I'm windows xp with SP3 under virtualbox. So I will try to reinstall the MSSDK.

BTW is there any doc that refers to your reply http://software.intel.com/en-us/forums/showpost.php?p=56080 about many operations that won't work locally on an intel amt host?

Thanks.

Quoting - ph3ar

I'm windows xp with SP3 under virtualbox. So I will try to reinstall the MSSDK.

BTW is there any doc that refers to your reply http://software.intel.com/en-us/forums/showpost.php?p=56080 about many operations that won't work locally on an intel amt host?

Thanks.

Ok... I'm Windows XP with SP3 too. I don't know what Virtualbox is so maybe there is something strange going on there.

As far a what samples can be run locally on the AMT Client vs remotely on your management console, I have written a couple of blogs, one for remote calls and one for local calls. There is also a comprehensive table in the Overview.pdf(in the DOCs folder) that tells you which realms operate on which interface (this table will be more up to date - my blogs will not mention any of the newer AMT Features.)

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Ok... I'm Windows XP with SP3 too. I don't know what Virtualbox is so maybe there is something strange going on there.

As far a what samples can be run locally on the AMT Client vs remotely on your management console, I have written a couple of blogs, one for remote calls and one for local calls. There is also a comprehensive table in the Overview.pdf(in the DOCs folder) that tells you which realms operate on which interface (this table will be more up to date - my blogs will not mention any of the newer AMT Features.)

I think that reinstalling the mssdk did the trick, but I'm getting a different error.
---
LINK : fatal error LNK1104: cannot open file 'StatusStringsD.lib'
---
I have also attached the Buildlog.htm

Virtualbox is a vmware like application.

I have already checked overview.pdf but still I cannot understand why I cannot enter webui of Intel's amt from the same machine (local), is this an implementation design or a "fault" ?

Attachments: 

AttachmentSize
Download BuildLog2.htm12.51 KB

Quoting - ph3ar

I think that reinstalling the mssdk did the trick, but I'm getting a different error.
---
LINK : fatal error LNK1104: cannot open file 'StatusStringsD.lib'
---
I have also attached the Buildlog.htm

Virtualbox is a vmware like application.

I have already checked overview.pdf but still I cannot understand why I cannot enter webui of Intel's amt from the same machine (local), is this an implementation design or a "fault" ?

Excellent. Because you are building a "Debug" release, it is looking for the Debug version of the StatusStrings.lib and I found that the debugversion had not been built so the lib is not there- there are two ways that you should be able to fix this.

1. Go into the ...CommonStatuStrings folder, open the StatusStrings project and select the Debug option on your top toolbar - you can choose "debug" or "release." Then build the solution. Then you will be able to see that the StatusStringsD.lib is there - then you can go back to your other sample and build - it should be able to find it.

2. Go back into your project and select the "Release" build and it will look for the StatusStrings.lib instead (and it is already there) and therefore should build just fine.

As for your WebUI question - that is by design. You can actually bring up the webui, but you will get an error.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Excellent. Because you are building a "Debug" release, it is looking for the Debug version of the StatusStrings.lib and I found that the debugversion had not been built so the lib is not there- there are two ways that you should be able to fix this.

1. Go into the ...CommonStatuStrings folder, open the StatusStrings project and select the Debug option on your top toolbar - you can choose "debug" or "release." Then build the solution. Then you will be able to see that the StatusStringsD.lib is there - then you can go back to your other sample and build - it should be able to find it.

2. Go back into your project and select the "Release" build and it will look for the StatusStrings.lib instead (and it is already there) and therefore should build just fine.

As for your WebUI question - that is by design. You can actually bring up the webui, but you will get an error.

OK, so I started with the 1st option without any error and then when I am going back to compile the discovery project I still get the same error.

When I'm trying to fix this the 2nd solution I got the following error attached as image.

WebUI question: Do you know where I can find documentation that talks about WebUI and why this is implemented like this, it's a pain in the ass if you want to configure a machine and also test this technology.

Thanks.

Attachments: 

AttachmentSize
Download xerces_error.JPG17.89 KB

Quoting - ph3ar
OK, so I started with the 1st option without any error and then when I am going back to compile the discovery project I still get the same error.

When I'm trying to fix this the 2nd solution I got the following error attached as image.

WebUI question: Do you know where I can find documentation that talks about WebUI and why this is implemented like this, it's a pain in the ass if you want to configure a machine and also test this technology.

Thanks.

Ok - when I do option 1, and then go back to the discovery sample and build, it works fine. Did you make any other changes to your project settings? (other than setting the include and lib folders for the Platform SDK?)

On the Web UI subject - many of the things that the Web UI would test require a remote connection (because those APIs that it is calling are only available on the Network Interface.See the explanation below from the Architecture Guide.

From the Architecture Guide: Intel AMT provides two general types of interfaces: network and local. Network interfaces consist of two types: a SOAP interface and an embedded web user interface. The SOAP interface is the enterprise model, enabling robust functionality designed to be controlled by management console applications created by third-party software makers. The full ranges of APIs associated with the SOAP interface are documented in the freely available Intel AMT SDK. The embedded web user interface has more limited functionality and is intended for use without enterprise management software, such as in small-to-medium business environments. The local host interface is used by software agents to access 3PDS and to support agent presence.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Ok - when I do option 1, and then go back to the discovery sample and build, it works fine. Did you make any other changes to your project settings? (other than setting the include and lib folders for the Platform SDK?)

On the Web UI subject - many of the things that the Web UI would test require a remote connection (because those APIs that it is calling are only available on the Network Interface.See the explanation below from the Architecture Guide.

From the Architecture Guide: Intel AMT provides two general types of interfaces: network and local. Network interfaces consist of two types: a SOAP interface and an embedded web user interface. The SOAP interface is the enterprise model, enabling robust functionality designed to be controlled by management console applications created by third-party software makers. The full ranges of APIs associated with the SOAP interface are documented in the freely available Intel AMT SDK. The embedded web user interface has more limited functionality and is intended for use without enterprise management software, such as in small-to-medium business environments. The local host interface is used by software agents to access 3PDS and to support agent presence.

Here is one more thing to try: Go into the ...Intel_AMTSamples folder and run the build.bat file. It copies the xerces-2_7.dll to the bin folder. Also, please verify that you do have a xerces folder in your ThirdParty folder?

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Quoting - Gael Holmes (Intel)
From the Architecture Guide: Intel AMT provides two general types of interfaces: network and local. Network interfaces consist of two types: a SOAP interface and an embedded web user interface. The SOAP interface is the enterprise model, enabling robust functionality designed to be controlled by management console applications created by third-party software makers. The full ranges of APIs associated with the SOAP interface are documented in the freely available Intel AMT SDK. The embedded web user interface has more limited functionality and is intended for use without enterprise management software, such as in small-to-medium business environments. The local host interface is used by software agents to access 3PDS and to support agent presence.

Here is one more thing to try: Go into the ...Intel_AMTSamples folder and run the build.bat file. It copies the xerces-2_7.dll to the bin folder. Also, please verify that you do have a xerces folder in your ThirdParty folder?

OK, I have verified that xerces folder exists in the ThirdParty folder of the SDK, and after running the build.bat on
Intel_AMTSamples folder I still get the same error for xerces.

BTW I still haven't found where the access to webUI is pointed!?Except if this is referred with Limited funcionality which can be anything else also!

Thanks.

Quoting - ph3ar

OK, I have verified that xerces folder exists in the ThirdParty folder of the SDK, and after running the build.bat on
Intel_AMTSamples folder I still get the same error for xerces.

BTW I still haven't found where the access to webUI is pointed!?Except if this is referred with Limited funcionality which can be anything else also!

Thanks.

Did you also run the build.bat that is in the ..Windows folder? (I mentioned that you should do this in one of my previous posts...) It looks like it sets up some key environment variables. I always run it in my SDK configurations and I seem to be able to compile and build.. so maybe that's it?

And I am not clear on what more you need to know about the web ui? Are you having trouble accessing it?

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Quoting - ph3ar

OK, I have verified that xerces folder exists in the ThirdParty folder of the SDK, and after running the build.bat on
Intel_AMTSamples folder I still get the same error for xerces.

BTW I still haven't found where the access to webUI is pointed!?Except if this is referred with Limited funcionality which can be anything else also!

Thanks.

Did you also run the build.bat that is in the ..Windows folder? (I mentioned that you should do this in one of my previous posts...) It looks like it sets up some key environment variables. I always run it in my SDK configurations and I seem to be able to compile and build.. so maybe that's it?

And I am not clear on what more you need to know about the web ui? Are you having trouble accessing it?

Still didn't work out... I just re-run build.bat that is in the ..Windows folder!

I thought that not being able to access the webui from the same Intel amt host is some sort of security mechanism, but I can't find this information somewhere.

Quoting - ph3ar

Still didn't work out... I just re-run build.bat that is in the ..Windows folder!

I thought that not being able to access the webui from the same Intel amt host is some sort of security mechanism, but I can't find this information somewhere.

Ok... I'm afraid I can't provide much more guidance here. I am wondering if this has something to do with your VirtualBox environment - may it's not accepting the environment variables that it needs in order to compile? Have you checked to make sure all the environment variables that needed to be set are actually in your system? Have you made sure the specific lib files that are copied over to the bin folder are actually there? The build.bat files seem to copy dlls and other files to where they need to be in order to build correctly - maybe this flow isn't happening in your VirtualBox environment? So if Microsoft Visual Studio isn't finding the dlls, libs, includes where it thinks it should be finding them, I would go through the build.bat files and see where they are being copied and make sure that they are actually there.

You can't access the WebUI locally by design.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Ok... I'm afraid I can't provide much more guidance here. I am wondering if this has something to do with your VirtualBox environment - may it's not accepting the environment variables that it needs in order to compile? Have you checked to make sure all the environment variables that needed to be set are actually in your system? Have you made sure the specific lib files that are copied over to the bin folder are actually there? The build.bat files seem to copy dlls and other files to where they need to be in order to build correctly - maybe this flow isn't happening in your VirtualBox environment? So if Microsoft Visual Studio isn't finding the dlls, libs, includes where it thinks it should be finding them, I would go through the build.bat files and see where they are being copied and make sure that they are actually there.

You can't access the WebUI locally by design.

Hi Gael,

thanks for your reply, I compiled with success AMTredirection, I have also included the BuildLog file.
Returning to the Discovery iAMT sample I guess that has to do with project Discovery properties (screenshot attached) and especially Linker in Configuration properties.

BTW when I try to debug the StatusStrings lib it asks for an executable file to be used for the debug session (screenshot attached), any clue?

Thanks.

Attachments: 

Quoting - ph3ar

Hi Gael,

thanks for your reply, I compiled with success AMTredirection, I have also included the BuildLog file.
Returning to the Discovery iAMT sample I guess that has to do with project Discovery properties (screenshot attached) and especially Linker in Configuration properties.

BTW when I try to debug the StatusStrings lib it asks for an executable file to be used for the debug session (screenshot attached), any clue?

Thanks.

The only thing that you should have had to change in the Discovery project was the adding of the Platform SDK folders (lib/include). I've never had to change anything else in the project in order to build samples. I think I would probably delete the Discovery folder and copy it over again and start fresh with it's project settings.

I'm not sure why you need to debug the StatusStings Library - in any case, I'm pretty sure that when you want to debug something in Visual Studio, you load the exe and then you can step through it - eventually you would go into libraries that were part of the program. Since StatusStringsD.dll is a library (the version built for Debug purposes)- you cannot load it into the debugger.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

The only thing that you should have had to change in the Discovery project was the adding of the Platform SDK folders (lib/include). I've never had to change anything else in the project in order to build samples. I think I would probably delete the Discovery folder and copy it over again and start fresh with it's project settings.

I'm not sure why you need to debug the StatusStings Library - in any case, I'm pretty sure that when you want to debug something in Visual Studio, you load the exe and then you can step through it - eventually you would go into libraries that were part of the program. Since StatusStringsD.dll is a library (the version built for Debug purposes)- you cannot load it into the debugger.

1. Go into the ...CommonStatuStrings folder, open the StatusStrings project and select the Debug option on your top toolbar - you can choose "debug" or "release." Then build the solution. Then you will be able to see that the StatusStringsD.lib is there - then you can go back to your other sample and build - it should be able to find it.

2. Go back into your project and select the "Release" build and it will look for the StatusStrings.lib instead (and it is already there) and therefore should build just fine.

I just followed again your instructions to help me build the Discovery project as you proposed me on your previous post reply http://software.intel.com/en-us/forums/showpost.php?p=86134

So It seems that I have misunderstood your steps!?

Thanks.

Quoting - ph3ar

I just followed again your instructions to help me build the Discovery project as you proposed me on your previous post reply http://software.intel.com/en-us/forums/showpost.php?p=86134

So It seems that I have misunderstood your steps!?

Thanks.

Does this mean that you got it to work? :-)

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Does this mean that you got it to work? :-)

Nope, it means that i don't understand what you really propose me with these 2 steps since I cannot debug a library. :)

Quoting - Gael Holmes (Intel)

Did you also run the build.bat that is in the ..Windows folder? (I mentioned that you should do this in one of my previous posts...) It looks like it sets up some key environment variables. I always run it in my SDK configurations and I seem to be able to compile and build.. so maybe that's it?

And I am not clear on what more you need to know about the web ui? Are you having trouble accessing it?

Ok... I was not asking you to debug the library, I was asking you to go build the debug version of the library. The reason that your Discovery sample did not build was because it was looking for StatusStringsD.dll rather than the StatusStrings.dll which is the "release" version of the library. The SDK has the release version of the library - if you want to build the debug version for the Discovery Sample, or any other sample, the compiler is going to look for the debug versionsof this library and it is not there. You have to go build it. Once you go into tht Status Strings project and select Debug (to build the debug version) and then build it, the correct dll will be where the Discovery sample expects it to be. Your version of the SDK will now have the required StatusStringsD.dll file that the Discovery sample is looking for when you have told it to build a debug version.

OR you can pick the option 2 that I proposed and tell Discovery to build the release version and it will go and look for StatusStrings.dll rather than StatusStringsD.dll.

Visual Studio and the Microsoft website probably has some good training material on building projects and what it means to build a "release" version versus a "debug" version for a project. I would suggest that you go out there and read up on this.

And, please let us know if you get Discovery to build.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Ok... I was not asking you to debug the library, I was asking you to go build the debug version of the library. The reason that your Discovery sample did not build was because it was looking for StatusStringsD.dll rather than the StatusStrings.dll which is the "release" version of the library. The SDK has the release version of the library - if you want to build the debug version for the Discovery Sample, or any other sample, the compiler is going to look for the debug versionsof this library and it is not there. You have to go build it. Once you go into tht Status Strings project and select Debug (to build the debug version) and then build it, the correct dll will be where the Discovery sample expects it to be. Your version of the SDK will now have the required StatusStringsD.dll file that the Discovery sample is looking for when you have told it to build a debug version.

OR you can pick the option 2 that I proposed and tell Discovery to build the release version and it will go and look for StatusStrings.dll rather than StatusStringsD.dll.

Visual Studio and the Microsoft website probably has some good training material on building projects and what it means to build a "release" version versus a "debug" version for a project. I would suggest that you go out there and read up on this.

And, please let us know if you get Discovery to build.

I got it! I copied the StatusStrings.dll and xerces-c_2_7.dll files to the same directory that I am running the Discovery release project.

I appreciate your support Gael, thank you again!

Quoting - ph3ar
I got it! I copied the StatusStrings.dll and xerces-c_2_7.dll files to the same directory that I am running the Discovery release project.

I appreciate your support Gael, thank you again!

Yay! I'm glad it's compiling. However, you should not have had to move them - the project should have all the directories set appropriately so I'm concerned that you continue to have problems building. You certainly don't want to have to move these files to your sample directory every time you want to build another sample.

Can you copy the SDK to another folder and start fresh? You already have your Platform SDK and you already have your MSSDK env var set. All you should have to do is run the build.bat files (I think there were two of them) and set the Platform SDK include/lib folders in your new project, and set Discovery to build a release version.

Sorry for dragging this on, but I would like to see it compile and build without having to copy libraries to your build directory (the project should be able to find them the way it is set up.)

Gael

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Yay! I'm glad it's compiling. However, you should not have had to move them - the project should have all the directories set appropriately so I'm concerned that you continue to have problems building. You certainly don't want to have to move these files to your sample directory every time you want to build another sample.

Can you copy the SDK to another folder and start fresh? You already have your Platform SDK and you already have your MSSDK env var set. All you should have to do is run the build.bat files (I think there were two of them) and set the Platform SDK include/lib folders in your new project, and set Discovery to build a release version.

Sorry for dragging this on, but I would like to see it compile and build without having to copy libraries to your build directory (the project should be able to find them the way it is set up.)

Gael

Sure, I have just started rebuiling the SDK but I haven't set the platform SDK env var set! I have only set the env for the MSSDK.

Do I miss sth here?

Quoting - ph3ar

Sure, I have just started rebuiling the SDK but I haven't set the platform SDK env var set! I have only set the env for the MSSDK.

Do I miss sth here?

Good question... I'm not sure if the order matters of when you run the build.bat files vs when you go in and set the project lib and include folders (I'm pretty sure you can run the build.bat files before you set up your project settings.) Are you in a new VM? You shouldn't have had to set the MSSDK env var again - it should have already been set. Also since you have already installed the Platform SDK, you should not have to do that again either, unless you are in a new VM.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Good question... I'm not sure if the order matters of when you run the build.bat files vs when you go in and set the project lib and include folders (I'm pretty sure you can run the build.bat files before you set up your project settings.) Are you in a new VM? You shouldn't have had to set the MSSDK env var again - it should have already been set. Also since you have already installed the Platform SDK, you should not have to do that again either, unless you are in a new VM.

I'm not using a new VM, and since I 've already setup the MSSDK env var I don't need to do it again.

The question is: Do I need to setup the lib and include folders for the iamt SDK also?

Quoting - ph3ar

I'm not using a new VM, and since I 've already setup the MSSDK env var I don't need to do it again.

The question is: Do I need to setup the lib and include folders for the iamt SDK also?

Yes, since you just copied the SDK to a new folder, you are starting new. You will need to go into your project settings and enter in the Window's Platform SDK include and library folder locations so that the compiler will be able to find those include files that it needs.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

Yes, since you just copied the SDK to a new folder, you are starting new. You will need to go into your project settings and enter in the Window's Platform SDK include and library folder locations so that the compiler will be able to find those include files that it needs.

OK, so I have missed that step! How can I set this globally for my project?
In visual studio I 'll start a new project... blah blah?

Quoting - ph3ar

OK, so I have missed that step! How can I set this globally for my project?
In visual studio I 'll start a new project... blah blah?

I'm sure you can do that - set the folders globally but Visual Studio is actually not my area of expertise. I would suggest going out to the Microsoft Website to see if you can find some good tutorials on building projects and setting them up.

Follow me on Twitter: @GaelHof Facebook: https://www.facebook.com/GaelHof

Quoting - Gael Holmes (Intel)

I'm sure you can do that - set the folders globally but Visual Studio is actually not my area of expertise. I would suggest going out to the Microsoft Website to see if you can find some good tutorials on building projects and setting them up.

Apparently visual studio is not my area of expertise either!

So If I don't setup any include/lib directories of the iamt sdk how visual studio is going to "find out" the correct path and compile the sample correctly?

Thanks.

Quoting - ph3ar
Apparently visual studio is not my area of expertise either!

So If I don't setup any include/lib directories of the iamt sdk how visual studio is going to "find out" the correct path and compile the sample correctly?

Thanks.

Hello,

If you start a new project and you want to useaheader file from the SDK you need to point it by: right click on the project > properties > C/C++ > general >Additional inclusion directories (and remember using the #include instead #include "XXX.h" in your code).
By other hand if you need access to any *.lib or *.dll file, you need to add a reference in VS by: right click on the project > properties >linker >input >Additional dependencies.

Bye.

Javier Andrs Cceres Alvis

Quoting - ph3ar
Hello,

I am getting the following error when I'm trying to compile sample discovery from Intel's AMT SDK.

------ Build started: Project: Discovery, Configuration: Debug Win32 ------
Compiling...
DiscoverySample.cpp
c:intel_amtsamplesdiscoveryc++discoverysample.h(16) : fatal error C1083: Cannot open include file: 'SoapCommonDefinitions.h': No such file or directory
Build log was saved at "file://c:Intel_AMTSamplesDiscoveryc++DebugBuildLog.htm"
Discovery - 1 error(s), 0 warning(s)
---------------------

I have followed the guide step by step I have even checked the video series on how to setup Intel's AMT SDK maybe I miss something ... any clue?

I have the same problem.

Leave a Comment

Please sign in to add a comment. Not a member? Join today