Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Regarding PNPX and DPWS

30 views
Skip to first unread message

sato

unread,
Apr 7, 2010, 3:29:01 AM4/7/10
to
Hi,
i am struck in a very silly problem which i am not able to resolve
for the past 1 month. it will be of great help if this problem is resolved. i
basically want to make my device DPWS-compliant. My WS-discovery and WS-Mex
are happening properly. My device is being listed in the vista'network folder
with the information i sent in mex. But, when i try clicking install for my
device, nothing is happening.. i need some help here very urgently.. i ll
post my mex xml here.. is der nythin wrong in that??

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://www.w3.org/2003/05/soap-envelope"
xmlns:SOAP-ENC="http://www.w3.org/2003/05/soap-encoding"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing"
xmlns:wsdisco="http://schemas.xmlsoap.org/ws/2005/04/discovery"
xmlns:wsd="http://schemas.xmlsoap.org/ws/2005/04/discovery"
xmlns:mex="http://schemas.xmlsoap.org/ws/2004/09/mex"
xmlns:wsdp="http://schemas.xmlsoap.org/ws/2006/02/devprof"
xmlns:wprt="http://schemas.microsoft.com/windows/2006/08/wdp/print"
xmlns:wscn="http://schemas.microsoft.com/windows/2006/08/wdp/scan"
xmlns:PNPX="http://schemas.microsoft.com/windows/pnpx/2005/10"
xmlns:UNS1="http://schemas.microsoft.com/windows/test/testdevice/11/2005"
xmlns:trans="http://schemas.xmlsoap.org/ws/2004/09/transfer"><SOAP-ENV:Header><wsa:Action>http://schemas.xmlsoap.org/ws/2004/09/transfer/GetResponse</wsa:Action><wsa:MessageID>urn:uuid:2d8f2cde-3d5b-11df-a618-0013205b8b01</wsa:MessageID><wsa:RelatesTo>urn:uuid:130ee6bb-c091-46cf-84fa-db185b1bc395</wsa:RelatesTo><wsa:ReplyTo
xsi:type="wsa:EndpointReferenceType"><wsa:Address
xsi:type="wsa:AttributedURI">http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:Address></wsa:ReplyTo><wsa:To>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:To></SOAP-ENV:Header><SOAP-ENV:Body><mex:Metadata
xsi:type="mex:MetadataType"><mex:MetadataSection
xsi:type="mex:MetadataSectionType"
Dialect="http://schemas.xmlsoap.org/ws/2006/02/devprof/ThisDevice"><wsdp:ThisDevice
xsi:type="wsdp:ThisDeviceType"><wsdp:FriendlyName
xsi:type="wsdp:LocalizedStringType">AC Toshiba Multi-Functional
Printer</wsdp:FriendlyName><wsdp:FirmwareVersion>0.0.0.0</wsdp:FirmwareVersion><wsdp:SerialNumber>CUB800109</wsdp:SerialNumber></wsdp:ThisDevice></mex:MetadataSection><mex:MetadataSection
xsi:type="mex:MetadataSectionType"
Dialect="http://schemas.xmlsoap.org/ws/2006/02/devprof/ThisModel"><wsdp:ThisModel
xsi:type="wsdp:ThisModelType"><wsdp:Manufacturer
xsi:type="wsdp:LocalizedStringType">TOSHIBA
TEC</wsdp:Manufacturer><wsdp:ManufacturerUrl>http://www.toshibatec.co.jp</wsdp:ManufacturerUrl><wsdp:ModelName
xsi:type="wsdp:LocalizedStringType">TOSHIBA e-STUDIO
Series</wsdp:ModelName><wsdp:ModelNumber>e-STUDIO2830C</wsdp:ModelNumber><wsdp:PresentationUrl>http://192.168.100.82:80</wsdp:PresentationUrl><PNPX:DeviceCategory>MFP</PNPX:DeviceCategory></wsdp:ThisModel></mex:MetadataSection><mex:MetadataSection
xsi:type="mex:MetadataSectionType"
Dialect="http://schemas.xmlsoap.org/ws/2006/02/devprof/Relationship"><wsdp:Relationship
xsi:type="wsdp:RelationshipType"
Type="http://schemas.xmlsoap.org/ws/2006/02/devprof/host"><wsdp:Hosted
xsi:type="wsdp:HostServiceType"><wsa:EndpointReference
xsi:type="wsa:EndpointReferenceType"><wsa:Address
xsi:type="wsa:AttributedURI">http://192.168.100.82:50084</wsa:Address><wsa:ReferenceProperties
xsi:type="wsa:ReferencePropertiesType"><UNS1:ServiceIdentifier>uri:prn</UNS1:ServiceIdentifier></wsa:ReferenceProperties></wsa:EndpointReference><wsdp:Types>wprt:PrinterServiceType</wsdp:Types><wsdp:ServiceId>uri:uuid:b93318e0-8b7c-4492-acf6-47b65d19fc3f/Printer</wsdp:ServiceId><PNPX:CompatibleId><PNPX:CompatibleId>http://schemas.microsoft.com/windows/2006/08/wdp/print/PrinterServiceType</PNPX:CompatibleId></wsdp:Hosted><wsdp:Hosted
xsi:type="wsdp:HostServiceType"><wsa:EndpointReference
xsi:type="wsa:EndpointReferenceType"><wsa:Address
xsi:type="wsa:AttributedURI">http://192.168.100.82:50083</wsa:Address><wsa:ReferenceProperties
xsi:type="wsa:ReferencePropertiesType"><UNS1:ServiceIdentifier>uri:scn</UNS1:ServiceIdentifier></wsa:ReferenceProperties></wsa:EndpointReference><wsdp:Types>wscn:ScannerServiceType</wsdp:Types><wsdp:ServiceId>uri:uuid:b92218e0-8b7c-4692-acf6-47b65d19fc4f/Scanner</wsdp:ServiceId><PNPX:CompatibleId>http://schemas.microsoft.com/windows/2006/08/wdp/scan/ScannerServiceType</PNPX:CompatibleId></wsdp:Hosted></wsdp:Relationship></mex:MetadataSection></mex:Metadata></SOAP-ENV:Body></SOAP-ENV:Envelope>


thanx in advance..

Sunil

unread,
Apr 9, 2010, 12:23:02 AM4/9/10
to
Hi Sato,

The Metadata response looks to be FINE.
Can i know the Operating System used?
If it is Windows server edition, please start the "IPBus Enum" service. It
will pop up an window for driver installation.

Thanks & Regards,
Sunil

sato

unread,
Apr 9, 2010, 1:41:01 AM4/9/10
to
Hi sunil,
Thanx a lot for replyin.. But, My operating system is windows vista..
i searched in the Services list. IPbus enum service is not listed in that..
Is there any other way?? :((

Sunil

unread,
Apr 9, 2010, 2:12:01 AM4/9/10
to
Hi Sato,

Run the following command as the Administrator user in command prompt,
"net start IPBusEnum"

And the service is listed as "PnP-X IP Bus Enumerator" in the Windows
Services.

sato

unread,
Apr 9, 2010, 6:08:01 AM4/9/10
to
Hi sunil,
thanx for ur quick reply again.. i tried that command as
administrator.. IPBusEnum was anyhow already started..
This is what i tried in the meanwhile.. The details of my devices just
exists in the
registry[Microsoft/FunctionDiscovery/RegistryStore/AssociationDB].. since it
had cached the details of my devices already, i wanted to do it afresh fter
the changes.. so, i removed the entries of my device in the association
database and tried it afresh.. now, the new set of logs in the
setupapi.app.log looks like dis..
[Device Install Log]
OS Version = 6.0.6000
Service Pack = 0.0
Suite = 0x0100
ProductType = 1
Architecture = x86

[BeginLog]
cci: NCI: 6to4svc.dll asking for write lock.
cci: NCI: 6to4svc.dll acquired write lock.
cci: NCI: Write lock released.

flq: {SPFILENOTIFY_CABINETINFO}
flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
flq: {SPFILENOTIFY_FILEEXTRACTED}
flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}
flq: {SPFILENOTIFY_CABINETINFO}
flq: {SPFILENOTIFY_CABINETINFO - exit(0x00000000)}
flq: {SPFILENOTIFY_FILEEXTRACTED}
flq: {SPFILENOTIFY_FILEEXTRACTED - exit(0x00000000)}

nyoder ways??
thanx,
Sato

0 new messages