Novell Support Forums - New Posts
Active Directory Driver Error Messages - Part 5
Active Directory Driver Error Messages - Part 5
25-Nov-2009 01:54 PM
Novell Identity Manager has a lot of different connected systems available and each has its own unique set of errors.
I would love to see Novell document all the various possible errors that can come up in each different driver, but the reality is that it is almost an impossible task.
However just because it is hard, does not mean it is worth doing. Rather than just annoy documentation writers at Novell about adding more troubleshooting steps (which I still continue to do) I also want to contribute on my own. You can see the fruits of my labours below. Now to be fair, recently the driver documentation have shown more content in the Troubleshooting section. This is a very good thing, but as always, I do not feel it goes far enough.
In the first four parts of this article series,
I have done this before for other drivers, like the JDBC driver. You can read that series at:
Error Codes of the eDirectory Driver for Identity Manager - Part 1
Then there is the beginning of a series on the SAP HR driver:
Error Codes of the SAP HR driver for Identity Manager - Part 1
You can see my optimism by naming the first article as part 1.
As you can imagine with so many different drivers for Novell Identity Manager, I probably will not run out of topics for a long time, and I hope to continue writing more and more.
Back to the Active Directory driver, as I continued working through the process of deploying a new set of drivers, I found even more errors than I had covered in the first four articles, so here comes part five of a continuing series.
As always, I encourage any one else who wants too, to contribute this style of article. The more error codes we get published, with the actual text of the error code, a suggestion of what was going on, and how you resolved it, the easier it will be for others who encounter it to resolve it for themselves.
Right now, there are not enough articles about Identity manager driver error codes out there, so these are my attempts to rectify that situation.
Please help contribute any errors you may have dealt with. Lets make Google searching more useful on this topic!
Anyway, on with the errors:
LDAP_OTHER 80 error, Group create, backslash in name:
nds dtdversion="1.1" ndsversion="8.7"> AD Novell, Inc. Other 00000523: SysErr: DSID-031A0FB6, problem 22 (Invalid argument), data 0 Here we have an event for a group create, where the name of the group, had a forward slash (/) in the group name. YOu can see it is called Lan/Wan, from the operation-data node, unmatched-src-dn. It says: CN=Lan/Wan,OU=SND,OU=CIS,OU=ACME
A forward slash is not a valid character in an old style NetBIOS complaint name. The name of a group object has similar restrictions to sAMAccountName on User objects. Really the driver should validate this field for Groups as well as Users, but since it does it for Users already with a handy dandy Regular Expression, that I have no interest in parsing and trying to understand, lets just fix this problem by changing Subscriber channel create rule to add this Regex replace all to clean the CN of the Group up.
This is basically copied from the rule for Users just one or two rules away.
This is an instance where I think it would have been really worthwhile for the default driver configuration in the comments section for the rule that uses this nice long regular expression, to take the five minutes to explain what it is doing. You know, list the illegal characters, and then what each element of the regular expression is stripping out. Seems like the right place to do it is in the driver configuration, and it is just comment tagged XML so it does not waste CPU much to leave it there in every driver.
Move user in AD based on DirXML-ADContext changing:
In this example, we had a deeply structured Active Directory tree, a structured LDAP authentication tree, and linking the two in the middle, a flat Identity Vault tree. We needed to carry structural information from the LDAP tree to the Active Directory tree and vica versa. To do that, we leveraged an existing attribute, DirXML-ADContext, and made our DN structures identical in both trees.
It is worth noting that the DN of an Active Directory user has at the end of it, a virtual bit, for the Domain name of the Active Directory tree. Usually of the form dc=domain,dc=com even in it so in eDirectory, in the structured LDAP tree, we actually store the users in a dc=com object, with a child domain object of dc=domain. (Well we used real names, but you get the point). In fact we actually had three Active Directory trees, part of a single forest with an empty root domain, with a dc=americas, dc=asiapc, and a dc=emea set of containers.
In the LDAP tree, we were able to present a single view of that to LDAP applications, which in Active Directory would have to be presented as three separate directory instances. eDirectory can host multiple partitions on a single server, unlike Active Directory which is limited to a single domain (their equivalent of an eDirectory partition) on a single server. (Actually eDirectory on Unix can even run multiple eDirectory instances on a single server, listening on different IP addresses, and thus run multiple trees on a single server. We often use this feature for development labs, when there is not enough hardware (or virtual hardware) for another development box).
Here is the engine trace of the event.
[05/05/09 16:12:57.540]:ASIAPAC-AD ST: DirXML Novell, Inc. 89cc58e90b3eda4da716bc06194428ce [05/05/09 16:12:57.542]:ASIAPAC-AD ST:Remote Interface Driver: Document sent. [05/05/09 16:12:57.611]:ASIAPAC-AD :Remote Interface Driver: Received. [05/05/09 16:12:57.612]:ASIAPAC-AD : AD Novell, Inc. rename failed. Other 00002089: UpdErr: DSID-031B0CE4, problem 5012 (DIR_ERROR), data 2 This is another instance of an LDAP_OTHER with an ldap_rc of 80 like above. The previous example was a problem 22, invalid argument.
This time we have a problem 5012, DIR_ERROR.
Here is the Remote Loader Trace view of that event.
DirXML: [05/05/09 16:11:22.81]: Loader: Calling subscriptionShim->execute() DirXML: [05/05/09 16:11:22.81]: Loader: XML Document: DirXML: [05/05/09 16:11:22.81]: DirXML Novell, Inc. 89cc58e90b3eda4da716bc06194428ce DirXML: [05/05/09 16:11:22.81]: ADDriver: parse command className user destDN eventId mta-gwlab#20090505201256#1#1 association 89cc58e90b3eda4da716bc06194428ce DirXML: [05/05/09 16:11:22.81]: ADDriver: parse rename DirXML: [05/05/09 16:11:22.81]: ADDriver: Connect using ldap_bind: user=idm-asia, domain=asiapac, password=***, method=negotiate, server=localhost, sign=yes, seal=yes ssl=no DirXML: [05/05/09 16:11:22.82]: ADDriver: ldap_bind connection succeeded DirXML: [05/05/09 16:11:22.84]: ADDriver: move CN=Test3 GWUser,OU=Shanghai,OU=bogota,DC=asiapac,DC=acme,DC =corp to CN=tgwuser3,OU=Japan,dc=asiapac,dc=acme,dc=corp DirXML: [05/05/09 16:11:22.87]: Loader: subscriptionShim->execute() returned: DirXML: [05/05/09 16:11:22.87]: Loader: XML Document: DirXML: [05/05/09 16:11:22.87]: AD Novell, Inc. rename failed. Other 00002089: UpdErr: DSID-031B0CE4, problem 5012 (DIR_ERROR), data 2 In this case, the node was pointing at a full object path, with CN=tgwuser3 at the beginning. Well that won't work. Although in the case of Active Directory, we find that it often can use a CN (container) object to contain other objects. Well that sounds redundant. For example, a very common error when deploying the Active Directory driver for the first time, usually in a test lab, is to leave your users in the default Users container in Active Directory.
Well for the driver to work, you need to specify where the scope of the containers in Active Directory are. Coming from an eDirectory world you would say, thats easy. OU=Users,dc=myDomain,dc=com. Well it turns out that the qualifier for a Container object is actually CN=, which we would normally (from an eDirectory perspective) consider for end nodes, like users, not containers. Easy enough to fix once you realize it has happened. Just change the Global Configuration Variable that defines the path in Active Directory.
Interestingly enough, I asked someone once, why the default CN=Users container in Active Directory installs, and finally got an insightful answer. The Container object more closely matches the containment rules for an NT Domain, than does an Organization or an Organizational Unit. Thus to enable transitioning from NT domains to Active Directory, you could move all your objects to a Container, and know that containment would allow it to work correctly.
In my example above, I happen to know that the cn=tgwuser3 is a test user object and not a container, and thus we have violated Active Directory containment rules, trying to move a user (actually the tgwuser3) from one container to a nonexistent container, that could not contain it, even if we wanted it too.
Move events from different drivers can be subtly different, and need to be handled in slightly different ways. In order to try and capture some of that complexity in a single location, I started this open call article:
Open Call for IDM Move Event Documents
In that article you can see the difference between a move event coming from an Active Directory driver on the Publisher channel, versus one sent through an eDirectory driver on the Subscriber channel. Above we have an example of an Active Directory driver, but on the Subscriber channel, which is again, just slightly different. I included XPATH examples to select the destination DNs for each type of move event you might see, which I hope people will find helpful.
LDAP_NOT_ALLOWED_ON_RDN, ldap-rc 67 error:
[05/05/09 16:44:14.700]:ASIAPAC-AD ST:Remote Interface Driver: Sending... [05/05/09 16:44:14.700]:ASIAPAC-AD ST: DirXML Novell, Inc. 89cc58e90b3eda4da716bc06194428ce Sir tgwuser3 /home2/Test3 GWUser [05/05/09 16:44:14.703]:ASIAPAC-AD ST:Remote Interface Driver: Document sent. [05/05/09 16:44:14.729]:ASIAPAC-AD :Remote Interface Driver: Received. [05/05/09 16:44:14.730]:ASIAPAC-AD : AD Novell, Inc. Not allowed on RDN 000020B1: UpdErr: DSID-030F0AE8, problem 6004 (CANT_ON_RDN), data 0 With an Active Directory driver, you should not schema map CN in eDirectory to CN in Active Directory. It turns out that the schemata do not match, and that CN in eDirectory is multi valued, whereas in Active Directory it is a single valued attribute.
If you ever look in Console One at a user and see a value in the Other Name field on the General tab, that is a second or third instance of a CN attribute value.
This causes LDAP tools that are looking at CN as the naming attribute no end of stomach upset, and the query often names the user as cn=Jsmith+uid=smithj,ou=this,o=that which is why we usually use uniqueID for LDAP tools to query against.
I used to think that uniqueID was single valued, but recently went and actually looked at schema and much to my chagrin, found out it was actually a multi valued attribute.
I imagine a multi valued uniqueID attribute on a user would make things a bit strange for an LDAP tool querying it as well.
Now you could handle this in DirXML Policy by watching for this kind of an event, and if it is an add attribute only event, adding in a node to convert that to a set destination attribute style event, which would avoid this problem. You can use reformat operation attribute to do this for you in one step if you would like. You can read more of my thoughts on reformat operational attribute in this article:
Reformat Operation Attribute
If you wanted to handle this error completely you should also decide what to do if there is more than one add attribute value for CN. If there is more than one, you ought to make a decision. Either only use the first one, or perhaps flatten and comma separate the values (Probably makes more sense in the case of an attribute like Location, than CN) or do something with it.
You will see this problem in a bunch of different attributes, where eDirectory is multi valued but Active Directory is not. This can be painful. I think Telephone number, Location, Description, Facsimile Telephone Number are just a couple of examples. We have a really neat generic rule my boss wrote that parses the application schema that is stored on the driver object, which on the first driver startup reads the schema out of Active Directory and stores it in a large XML attribute on the driver object.
As an exercise for the reader I leave the process of using that to decide if each operational attribute in the event document is a single or multi valued attribute. This allows you to handle all of schema with one rule, instead of one flattening rule for every attribute you identify. There is a weakness in this, as the application schema stored on the driver is actually not 100% accurate and we have found errors creep in, and I am not sure of the exact cause of that.
Well that's about it for this article, stay tuned for the next in the series, I still have more error codes to work though, and I hope others will take up my charge and start writing these sort of articles as well.
More...
25-Nov-2009 01:54 PM
Novell Identity Manager has a lot of different connected systems available and each has its own unique set of errors.
I would love to see Novell document all the various possible errors that can come up in each different driver, but the reality is that it is almost an impossible task.
However just because it is hard, does not mean it is worth doing. Rather than just annoy documentation writers at Novell about adding more troubleshooting steps (which I still continue to do) I also want to contribute on my own. You can see the fruits of my labours below. Now to be fair, recently the driver documentation have shown more content in the Troubleshooting section. This is a very good thing, but as always, I do not feel it goes far enough.
In the first four parts of this article series,
- Active Directory Driver Error Messages - Part 1
- Active Directory Driver Error Messages - Part 2
- Active Directory Driver Error Messages - Part 3
- Active Directory Driver Error Messages - Part 4
I have done this before for other drivers, like the JDBC driver. You can read that series at:
- Error Codes of the Novell Identity Manager Driver for JDBC: Part 1 of 4
- Error Codes of the Novell Identity Manager Driver for JDBC: Part 2 of 4
- Error Codes of the Novell Identity Manager Driver for JDBC: Part 3 of 4
- Error Codes of the Novell Identity Manager Driver for JDBC: Part 4 of 4
Error Codes of the eDirectory Driver for Identity Manager - Part 1
Then there is the beginning of a series on the SAP HR driver:
Error Codes of the SAP HR driver for Identity Manager - Part 1
You can see my optimism by naming the first article as part 1.
As you can imagine with so many different drivers for Novell Identity Manager, I probably will not run out of topics for a long time, and I hope to continue writing more and more.
Back to the Active Directory driver, as I continued working through the process of deploying a new set of drivers, I found even more errors than I had covered in the first four articles, so here comes part five of a continuing series.
As always, I encourage any one else who wants too, to contribute this style of article. The more error codes we get published, with the actual text of the error code, a suggestion of what was going on, and how you resolved it, the easier it will be for others who encounter it to resolve it for themselves.
Right now, there are not enough articles about Identity manager driver error codes out there, so these are my attempts to rectify that situation.
Please help contribute any errors you may have dealt with. Lets make Google searching more useful on this topic!
Anyway, on with the errors:
LDAP_OTHER 80 error, Group create, backslash in name:
nds dtdversion="1.1" ndsversion="8.7"> AD Novell, Inc. Other 00000523: SysErr: DSID-031A0FB6, problem 22 (Invalid argument), data 0 Here we have an event for a group create, where the name of the group, had a forward slash (/) in the group name. YOu can see it is called Lan/Wan, from the operation-data node, unmatched-src-dn. It says: CN=Lan/Wan,OU=SND,OU=CIS,OU=ACME
A forward slash is not a valid character in an old style NetBIOS complaint name. The name of a group object has similar restrictions to sAMAccountName on User objects. Really the driver should validate this field for Groups as well as Users, but since it does it for Users already with a handy dandy Regular Expression, that I have no interest in parsing and trying to understand, lets just fix this problem by changing Subscriber channel create rule to add this Regex replace all to clean the CN of the Group up.
This is basically copied from the rule for Users just one or two rules away.
This is an instance where I think it would have been really worthwhile for the default driver configuration in the comments section for the rule that uses this nice long regular expression, to take the five minutes to explain what it is doing. You know, list the illegal characters, and then what each element of the regular expression is stripping out. Seems like the right place to do it is in the driver configuration, and it is just comment tagged XML so it does not waste CPU much to leave it there in every driver.
Move user in AD based on DirXML-ADContext changing:
In this example, we had a deeply structured Active Directory tree, a structured LDAP authentication tree, and linking the two in the middle, a flat Identity Vault tree. We needed to carry structural information from the LDAP tree to the Active Directory tree and vica versa. To do that, we leveraged an existing attribute, DirXML-ADContext, and made our DN structures identical in both trees.
It is worth noting that the DN of an Active Directory user has at the end of it, a virtual bit, for the Domain name of the Active Directory tree. Usually of the form dc=domain,dc=com even in it so in eDirectory, in the structured LDAP tree, we actually store the users in a dc=com object, with a child domain object of dc=domain. (Well we used real names, but you get the point). In fact we actually had three Active Directory trees, part of a single forest with an empty root domain, with a dc=americas, dc=asiapc, and a dc=emea set of containers.
In the LDAP tree, we were able to present a single view of that to LDAP applications, which in Active Directory would have to be presented as three separate directory instances. eDirectory can host multiple partitions on a single server, unlike Active Directory which is limited to a single domain (their equivalent of an eDirectory partition) on a single server. (Actually eDirectory on Unix can even run multiple eDirectory instances on a single server, listening on different IP addresses, and thus run multiple trees on a single server. We often use this feature for development labs, when there is not enough hardware (or virtual hardware) for another development box).
Here is the engine trace of the event.
[05/05/09 16:12:57.540]:ASIAPAC-AD ST: DirXML Novell, Inc. 89cc58e90b3eda4da716bc06194428ce [05/05/09 16:12:57.542]:ASIAPAC-AD ST:Remote Interface Driver: Document sent. [05/05/09 16:12:57.611]:ASIAPAC-AD :Remote Interface Driver: Received. [05/05/09 16:12:57.612]:ASIAPAC-AD : AD Novell, Inc. rename failed. Other 00002089: UpdErr: DSID-031B0CE4, problem 5012 (DIR_ERROR), data 2 This is another instance of an LDAP_OTHER with an ldap_rc of 80 like above. The previous example was a problem 22, invalid argument.
This time we have a problem 5012, DIR_ERROR.
Here is the Remote Loader Trace view of that event.
DirXML: [05/05/09 16:11:22.81]: Loader: Calling subscriptionShim->execute() DirXML: [05/05/09 16:11:22.81]: Loader: XML Document: DirXML: [05/05/09 16:11:22.81]: DirXML Novell, Inc. 89cc58e90b3eda4da716bc06194428ce DirXML: [05/05/09 16:11:22.81]: ADDriver: parse command className user destDN eventId mta-gwlab#20090505201256#1#1 association 89cc58e90b3eda4da716bc06194428ce DirXML: [05/05/09 16:11:22.81]: ADDriver: parse rename DirXML: [05/05/09 16:11:22.81]: ADDriver: Connect using ldap_bind: user=idm-asia, domain=asiapac, password=***, method=negotiate, server=localhost, sign=yes, seal=yes ssl=no DirXML: [05/05/09 16:11:22.82]: ADDriver: ldap_bind connection succeeded DirXML: [05/05/09 16:11:22.84]: ADDriver: move CN=Test3 GWUser,OU=Shanghai,OU=bogota,DC=asiapac,DC=acme,DC =corp to CN=tgwuser3,OU=Japan,dc=asiapac,dc=acme,dc=corp DirXML: [05/05/09 16:11:22.87]: Loader: subscriptionShim->execute() returned: DirXML: [05/05/09 16:11:22.87]: Loader: XML Document: DirXML: [05/05/09 16:11:22.87]: AD Novell, Inc. rename failed. Other 00002089: UpdErr: DSID-031B0CE4, problem 5012 (DIR_ERROR), data 2 In this case, the node was pointing at a full object path, with CN=tgwuser3 at the beginning. Well that won't work. Although in the case of Active Directory, we find that it often can use a CN (container) object to contain other objects. Well that sounds redundant. For example, a very common error when deploying the Active Directory driver for the first time, usually in a test lab, is to leave your users in the default Users container in Active Directory.
Well for the driver to work, you need to specify where the scope of the containers in Active Directory are. Coming from an eDirectory world you would say, thats easy. OU=Users,dc=myDomain,dc=com. Well it turns out that the qualifier for a Container object is actually CN=, which we would normally (from an eDirectory perspective) consider for end nodes, like users, not containers. Easy enough to fix once you realize it has happened. Just change the Global Configuration Variable that defines the path in Active Directory.
Interestingly enough, I asked someone once, why the default CN=Users container in Active Directory installs, and finally got an insightful answer. The Container object more closely matches the containment rules for an NT Domain, than does an Organization or an Organizational Unit. Thus to enable transitioning from NT domains to Active Directory, you could move all your objects to a Container, and know that containment would allow it to work correctly.
In my example above, I happen to know that the cn=tgwuser3 is a test user object and not a container, and thus we have violated Active Directory containment rules, trying to move a user (actually the tgwuser3) from one container to a nonexistent container, that could not contain it, even if we wanted it too.
Move events from different drivers can be subtly different, and need to be handled in slightly different ways. In order to try and capture some of that complexity in a single location, I started this open call article:
Open Call for IDM Move Event Documents
In that article you can see the difference between a move event coming from an Active Directory driver on the Publisher channel, versus one sent through an eDirectory driver on the Subscriber channel. Above we have an example of an Active Directory driver, but on the Subscriber channel, which is again, just slightly different. I included XPATH examples to select the destination DNs for each type of move event you might see, which I hope people will find helpful.
LDAP_NOT_ALLOWED_ON_RDN, ldap-rc 67 error:
[05/05/09 16:44:14.700]:ASIAPAC-AD ST:Remote Interface Driver: Sending... [05/05/09 16:44:14.700]:ASIAPAC-AD ST: DirXML Novell, Inc. 89cc58e90b3eda4da716bc06194428ce Sir tgwuser3 /home2/Test3 GWUser [05/05/09 16:44:14.703]:ASIAPAC-AD ST:Remote Interface Driver: Document sent. [05/05/09 16:44:14.729]:ASIAPAC-AD :Remote Interface Driver: Received. [05/05/09 16:44:14.730]:ASIAPAC-AD : AD Novell, Inc. Not allowed on RDN 000020B1: UpdErr: DSID-030F0AE8, problem 6004 (CANT_ON_RDN), data 0 With an Active Directory driver, you should not schema map CN in eDirectory to CN in Active Directory. It turns out that the schemata do not match, and that CN in eDirectory is multi valued, whereas in Active Directory it is a single valued attribute.
If you ever look in Console One at a user and see a value in the Other Name field on the General tab, that is a second or third instance of a CN attribute value.
This causes LDAP tools that are looking at CN as the naming attribute no end of stomach upset, and the query often names the user as cn=Jsmith+uid=smithj,ou=this,o=that which is why we usually use uniqueID for LDAP tools to query against.
I used to think that uniqueID was single valued, but recently went and actually looked at schema and much to my chagrin, found out it was actually a multi valued attribute.
I imagine a multi valued uniqueID attribute on a user would make things a bit strange for an LDAP tool querying it as well.
Now you could handle this in DirXML Policy by watching for this kind of an event, and if it is an add attribute only event, adding in a node to convert that to a set destination attribute style event, which would avoid this problem. You can use reformat operation attribute to do this for you in one step if you would like. You can read more of my thoughts on reformat operational attribute in this article:
Reformat Operation Attribute
If you wanted to handle this error completely you should also decide what to do if there is more than one add attribute value for CN. If there is more than one, you ought to make a decision. Either only use the first one, or perhaps flatten and comma separate the values (Probably makes more sense in the case of an attribute like Location, than CN) or do something with it.
You will see this problem in a bunch of different attributes, where eDirectory is multi valued but Active Directory is not. This can be painful. I think Telephone number, Location, Description, Facsimile Telephone Number are just a couple of examples. We have a really neat generic rule my boss wrote that parses the application schema that is stored on the driver object, which on the first driver startup reads the schema out of Active Directory and stores it in a large XML attribute on the driver object.
As an exercise for the reader I leave the process of using that to decide if each operational attribute in the event document is a single or multi valued attribute. This allows you to handle all of schema with one rule, instead of one flattening rule for every attribute you identify. There is a weakness in this, as the application schema stored on the driver is actually not 100% accurate and we have found errors creep in, and I am not sure of the exact cause of that.
Well that's about it for this article, stay tuned for the next in the series, I still have more error codes to work though, and I hope others will take up my charge and start writing these sort of articles as well.
More...
Categories: Novell Support Forums - New Posts
Making Hotel and Travel Arrangements for BrainShare
Making Hotel and Travel Arrangements for BrainShare
25-Nov-2009 10:29 AM
BrainShare has negotiated discounted rates at many downtown Salt Lake City hotels, in what is known as the BrainShare room block. You may book a room at one of these hotels once you have completed the registration process. But you'd better hurry; these rooms don't last long. The earlier you register the better your chance of getting the hotel and room of your choice. More information about making hotel and travel arrangements can be found at http://www.novell.com/brainshare/hotels
More...
25-Nov-2009 10:29 AM
BrainShare has negotiated discounted rates at many downtown Salt Lake City hotels, in what is known as the BrainShare room block. You may book a room at one of these hotels once you have completed the registration process. But you'd better hurry; these rooms don't last long. The earlier you register the better your chance of getting the hotel and room of your choice. More information about making hotel and travel arrangements can be found at http://www.novell.com/brainshare/hotels
More...
Categories: Novell Support Forums - New Posts
Error -641 iManager during configuration of SPML-SOAP
While Trying to start SPML-SOAP Driver
The following error occurred: com.novell.admin.common.exceptions.UniqueSPIExcept ion: (Error -641) The server did not understand the request because a request sent by a client workstation might be incorrect or the schema might not be synchronized.
Any Help?
The following error occurred: com.novell.admin.common.exceptions.UniqueSPIExcept ion: (Error -641) The server did not understand the request because a request sent by a client workstation might be incorrect or the schema might not be synchronized.
Any Help?
Categories: Novell Support Forums - New Posts
how to unregister device from pre-boot?
I finally got my pxe-boot kickstart enviroment to work but during the process I had a few mistakes.
At one stage I aborted a PXE-initiated Kickstart install because of an error in the preboot bundle. However this device now wont PXE-boot again - according to /var/opt/novell/log/zenworks/prebootlookup.log "Assigned preboot work is already done". This device doesnt appear in the list of devices in the webGUI so I cant assign it.
When I do '/etc/rc.d/init.d/novell-zislnx dump' on the server it shows my device
Is there a way reset this device so it will re-run the initial kickstart install again?
At one stage I aborted a PXE-initiated Kickstart install because of an error in the preboot bundle. However this device now wont PXE-boot again - according to /var/opt/novell/log/zenworks/prebootlookup.log "Assigned preboot work is already done". This device doesnt appear in the list of devices in the webGUI so I cant assign it.
When I do '/etc/rc.d/init.d/novell-zislnx dump' on the server it shows my device
Is there a way reset this device so it will re-run the initial kickstart install again?
Categories: Novell Support Forums - New Posts
NW 6.5 SP8 on HP ML350 G6
Hello,
I am trying to install Netware 6.5 sp8 onto a HP ML350 G6 with a P410i Raid controller, and 3 450gb sas drives.
I have disabled Hyperthreading and using only one core, it is setup as Raid 5.
I get the correct drivers to load on the install and get all the way to creating the volume sys and the install dies with IO errors.
Any help is appreciated, thank you.
Allen
I am trying to install Netware 6.5 sp8 onto a HP ML350 G6 with a P410i Raid controller, and 3 450gb sas drives.
I have disabled Hyperthreading and using only one core, it is setup as Raid 5.
I get the correct drivers to load on the install and get all the way to creating the volume sys and the install dies with IO errors.
Any help is appreciated, thank you.
Allen
Categories: Novell Support Forums - New Posts
JBoss as a service
Hey all,
I am trying to install JBoss as a service. I see the wrapper but don't want to pay the $90 in licensing. Is there a free version that is recommended?
Thanks.
I am trying to install JBoss as a service. I see the wrapper but don't want to pay the $90 in licensing. Is there a free version that is recommended?
Thanks.
Categories: Novell Support Forums - New Posts
Slow connection ZCM 10.1.0
We are running ZCM 10.1.0 and whenever we try to establish a remote connection to a PC on the LAN, it could take anywhere from 20 to 30 seconds.
Is anyone having this same issue? I don't see any TID's that are related to this problem. Any help would be deeply appreciated.
Stanley
Is anyone having this same issue? I don't see any TID's that are related to this problem. Any help would be deeply appreciated.
Stanley
Categories: Novell Support Forums - New Posts
Form Fill for WhatsUp Gold 14
Hello, everyone!
So far I've had success creating Form Fill policies for some of our Web applications: GW WebAccess 8 & SugarCRM. Now, I am trying to do the same for our WhatsUp Gold network monitoring server, but once the login page appears, the credentials filled in and the form submitted, the login page just loops on itself.
The form itself is fairly simple:
<form method="POST" action="DlgUserLogin.asp" name="DlgUserLogin" id="DlgUserLogin" >
And the two fields I am filling in are simply the username and password:
<input type="text" name="DlgUserLogin.sUserName" id="DlgUserLogin.sUserName" class="Aspf-Edit" onFocus="this.className+=' Aspf-Control-Focus';" onBlur="this.className='Aspf-Edit'" maxlength="100" value="" style='width:190px' />
<input type="password" name="DlgUserLogin.sPassword" id="DlgUserLogin.sPassword" class="Aspf-EditPassword" onFocus="this.className+=' Aspf-Control-Focus';" onBlur="this.className='Aspf-EditPassword'" maxlength="100" value="" style='width:190px' />
In my form fill policy, I simply fill in the two fields with the NAM credentials and select auto-submit.
If I do not select the Auto-submit option, the credentials get filled in properly and I simply have to click the Login button on my WhatsUp login screen, at which point I access the application. It seems that only the auto-submit doesn't work.
I've read some posts here on the forum, but still can't figure it out.
Any help would be greatly appreciated!
Thanks!
Jacques
So far I've had success creating Form Fill policies for some of our Web applications: GW WebAccess 8 & SugarCRM. Now, I am trying to do the same for our WhatsUp Gold network monitoring server, but once the login page appears, the credentials filled in and the form submitted, the login page just loops on itself.
The form itself is fairly simple:
<form method="POST" action="DlgUserLogin.asp" name="DlgUserLogin" id="DlgUserLogin" >
And the two fields I am filling in are simply the username and password:
<input type="text" name="DlgUserLogin.sUserName" id="DlgUserLogin.sUserName" class="Aspf-Edit" onFocus="this.className+=' Aspf-Control-Focus';" onBlur="this.className='Aspf-Edit'" maxlength="100" value="" style='width:190px' />
<input type="password" name="DlgUserLogin.sPassword" id="DlgUserLogin.sPassword" class="Aspf-EditPassword" onFocus="this.className+=' Aspf-Control-Focus';" onBlur="this.className='Aspf-EditPassword'" maxlength="100" value="" style='width:190px' />
In my form fill policy, I simply fill in the two fields with the NAM credentials and select auto-submit.
If I do not select the Auto-submit option, the credentials get filled in properly and I simply have to click the Login button on my WhatsUp login screen, at which point I access the application. It seems that only the auto-submit doesn't work.
I've read some posts here on the forum, but still can't figure it out.
Any help would be greatly appreciated!
Thanks!
Jacques
Categories: Novell Support Forums - New Posts
Teaming 2.0 and SLES10-SP3 / OES2-SP2
supported?
if not, when?
thanks
if not, when?
thanks
Categories: Novell Support Forums - New Posts
GW8 SP1 Compatible with SLES10-SP3?
and OES2 SP2?
thanks
thanks
Categories: Novell Support Forums - New Posts
Workstation associated apps with pre-install
Trying to figure out the behavior of workstation associated apps that are set to pre-install.
Testing it out with the latest zfd7 agent. I created an MSI app that is set to run in "Progress" mode, Reboot If Needed, Prompt for reboot. The Pre-Install Schedule is enabled and set to Schedule Type=None. A workstation (a test vm) is associated to the application with "App Launcher" checked only (no force run, etc).
Sometimes the agent installs at the CTRL+ALT+DEL screen and auto-reboots. Sometimes if I'm logged into the workstation sitting at the desktop, it'll just reboot as well. Its not prompting or anything. I'm not sure why.. is this just how the "Pre-Install Schedule=None" option behaves?
Thanks for tips.. I've always associated to users before
Testing it out with the latest zfd7 agent. I created an MSI app that is set to run in "Progress" mode, Reboot If Needed, Prompt for reboot. The Pre-Install Schedule is enabled and set to Schedule Type=None. A workstation (a test vm) is associated to the application with "App Launcher" checked only (no force run, etc).
Sometimes the agent installs at the CTRL+ALT+DEL screen and auto-reboots. Sometimes if I'm logged into the workstation sitting at the desktop, it'll just reboot as well. Its not prompting or anything. I'm not sure why.. is this just how the "Pre-Install Schedule=None" option behaves?
Thanks for tips.. I've always associated to users before
Categories: Novell Support Forums - New Posts
Howto start Gnome Desktop from console
Hello!
I've installed SLES 10 SP2 initially without Gnome desktop.
Now, I need a desktop and installed Gnome.
However, when booting the server, GDM is not starting automatically.
How can I start Gnome from console?
THX
I've installed SLES 10 SP2 initially without Gnome desktop.
Now, I need a desktop and installed Gnome.
However, when booting the server, GDM is not starting automatically.
How can I start Gnome from console?
THX
Categories: Novell Support Forums - New Posts
ZCM incompatible with ZLM agent?
Hi,
I just installed a brand new SLES11 64bit server (VMware guest).
Installed the ZLM agent on it, registred it to the ZLM server and ran the updates from it. So server fully patched.
Installed ZCM
-Installed mono
-Installed ZCM 10.2
After install novell-zenagent won't start.
Did some troubleshooting and found:
server:/ # /opt/novell/zenworks/bin/ZenLinuxDaemon --debug
** (/opt/novell/zenworks/bin/ZenLinuxDaemon.exe:11374): WARNING **: Symbol file /opt/novell/zenworks/lib/mono/2.0/mscorlib.dll.mdb has incorrect version (expected 50.0, got 39)
Corlib not in sync with this runtime: expected corlib version 68, found 60.
Loaded from: /opt/novell/zenworks/lib/mono/2.0/mscorlib.dll
Download a newer corlib or a newer runtime at Mono Daily Binary Packages.
And then:
server:/mnt # rpm -qf /opt/novell/zenworks/lib/mono/2.0/mscorlib.dll
novell-zenworks-mono-1.2.6-0.0.0
saturn02:/mnt # rpm -e novell-zenworks-mono-1.2.6-0.0.0
error: Failed dependencies:
novell-zenworks-mono is needed by (installed) zmd-7.3.1.0-0.0.x86_64
saturn02:/mnt # rpm -e novell-zenworks-mono-1.2.6-0.0.0 zmd-7.3.1.0-0.0.x86_64
error: Failed dependencies:
zmd is needed by (installed) novell-zenworks-zmd-tess-7.3.1-0.0.0.x86_64
zmd is needed by (installed) novell-zenworks-zmd-policymanager-7.3.1-0.0.0.x86_64
zmd is needed by (installed) novell-zenworks-zmd-settings-7.3.1-0.0.0.x86_64
zmd is needed by (installed) novell-zenworks-zmd-policyenforcers-7.3.1-0.0.0.x86_64
zmd is needed by (installed) zmd-inventory-7.3.1.0-0.0.x86_64
zmd is needed by (installed) zen-updater-7.3.1-0.0.x86_64
zmd is needed by (installed) rug-7.3.1.0-0.0.x86_64
zmd is needed by (installed) novell-zenworks-zmd-gconfpolicyenforcers-7.3.1-0.0.0.x86_64
zmd >= 7.1.1 is needed by (installed) novell-zenworks-zmd-imgagent-7.3.1-0.0.0.x86_64
zmd >= 7.1.1 is needed by (installed) novell-zenworks-zmd-rmagent-7.3.1-0.0.0.x86_64
zmd is needed by (installed) novell-zenworks-zmd-actions-7.3.1-0.0.0.x86_64
?????
So went back to the VMware snapshot I made after installing the ZLM agent, uninstalled it.
Reinstalled ZCM and now the novell-zenagent starts!
I also tried updating mono to the newest version, but then the agent complains mono is too new.
Are they really incompatible, or is there a trick to it?
Thanks,
Hein
I just installed a brand new SLES11 64bit server (VMware guest).
Installed the ZLM agent on it, registred it to the ZLM server and ran the updates from it. So server fully patched.
Installed ZCM
-Installed mono
-Installed ZCM 10.2
After install novell-zenagent won't start.
Did some troubleshooting and found:
server:/ # /opt/novell/zenworks/bin/ZenLinuxDaemon --debug
** (/opt/novell/zenworks/bin/ZenLinuxDaemon.exe:11374): WARNING **: Symbol file /opt/novell/zenworks/lib/mono/2.0/mscorlib.dll.mdb has incorrect version (expected 50.0, got 39)
Corlib not in sync with this runtime: expected corlib version 68, found 60.
Loaded from: /opt/novell/zenworks/lib/mono/2.0/mscorlib.dll
Download a newer corlib or a newer runtime at Mono Daily Binary Packages.
And then:
server:/mnt # rpm -qf /opt/novell/zenworks/lib/mono/2.0/mscorlib.dll
novell-zenworks-mono-1.2.6-0.0.0
saturn02:/mnt # rpm -e novell-zenworks-mono-1.2.6-0.0.0
error: Failed dependencies:
novell-zenworks-mono is needed by (installed) zmd-7.3.1.0-0.0.x86_64
saturn02:/mnt # rpm -e novell-zenworks-mono-1.2.6-0.0.0 zmd-7.3.1.0-0.0.x86_64
error: Failed dependencies:
zmd is needed by (installed) novell-zenworks-zmd-tess-7.3.1-0.0.0.x86_64
zmd is needed by (installed) novell-zenworks-zmd-policymanager-7.3.1-0.0.0.x86_64
zmd is needed by (installed) novell-zenworks-zmd-settings-7.3.1-0.0.0.x86_64
zmd is needed by (installed) novell-zenworks-zmd-policyenforcers-7.3.1-0.0.0.x86_64
zmd is needed by (installed) zmd-inventory-7.3.1.0-0.0.x86_64
zmd is needed by (installed) zen-updater-7.3.1-0.0.x86_64
zmd is needed by (installed) rug-7.3.1.0-0.0.x86_64
zmd is needed by (installed) novell-zenworks-zmd-gconfpolicyenforcers-7.3.1-0.0.0.x86_64
zmd >= 7.1.1 is needed by (installed) novell-zenworks-zmd-imgagent-7.3.1-0.0.0.x86_64
zmd >= 7.1.1 is needed by (installed) novell-zenworks-zmd-rmagent-7.3.1-0.0.0.x86_64
zmd is needed by (installed) novell-zenworks-zmd-actions-7.3.1-0.0.0.x86_64
?????
So went back to the VMware snapshot I made after installing the ZLM agent, uninstalled it.
Reinstalled ZCM and now the novell-zenagent starts!
I also tried updating mono to the newest version, but then the agent complains mono is too new.
Are they really incompatible, or is there a trick to it?
Thanks,
Hein
Categories: Novell Support Forums - New Posts
Moving SCSI Volume to iSCSI SAN
I'm not sure but it sounds like you can't Backup and Restore to a X_Volume and then Rename the original Volume to Old_Volume and then rename the X_Volume to the original Volume name.
Why wouldn't this way work? The new Volume will have all the trustee rights because of the SMS backup and restore.
The reason I want to do it this way is because I want to leave the GroupWise on the SCSI Drives, but moving the rest.
Steven
Why wouldn't this way work? The new Volume will have all the trustee rights because of the SMS backup and restore.
The reason I want to do it this way is because I want to leave the GroupWise on the SCSI Drives, but moving the rest.
Steven
Categories: Novell Support Forums - New Posts
Windows shares issues (nwfilter)
We are running WinXP Pro SP3 with Novell client 4.91 SP5 with all the current patches up to nwfilter 1. We have performance problems accessing a Windows share running Server 2000 SP4. The shares are authenticated via AD but the workstations are not in the domain. The issue is that after the workstations are idle a bit in regards to that windows mapping, they take several minutes to wake up when trying to browse. Overall access times are also noticeably slower. Machines without the Novell client or with older version do not have this issue. We are currently testing the age old trick of tweaking the provider order but it does not seem to be helping. We are also trying turning UNC path filtering on and off.
Is anybody else seeing this? Any suggestions? I know the current (beta) nwfilter was a complete re-write but I am wondering if it is the culprit. Logic says that if the MS provider is before the NW Client, it should not matter.
Thanks.
Is anybody else seeing this? Any suggestions? I know the current (beta) nwfilter was a complete re-write but I am wondering if it is the culprit. Logic says that if the MS provider is before the NW Client, it should not matter.
Thanks.
Categories: Novell Support Forums - New Posts
Critical update erroneously flagged as patched
I've noticed an error in Patch Management involving several managed computers (Windows XP SP 3) that have Microsoft's .NET Framework 3.5 Service Pack 1 installed. At least I believe it's an error. Patch Management says the machines are patched for the "Microsoft .NET Framework 3.5 Service Pack 1 and .NET Framework 3.5 Family Update for .NET version 2.0 through 3.5 (KB951847) x86" update, but both a Windows Update and Mcrosoft Baseline Security Analyzer (v2.1) scan shows they are not. I've also checked file versions and am confident the patch is not installed. I've looked in the ZCM Patch Management documentation and can't find a remedy for this problem, and wonder how far does this go. Have others noticed similar issues?
It bothers me that, had I not double checked with third-party scans, Patch Management would have continued to give false data.
It bothers me that, had I not double checked with third-party scans, Patch Management would have continued to give false data.
Categories: Novell Support Forums - New Posts
default login screen not showing?
This is odd
New NAM 3.1.1 IR2 setup
I get the login page, but it doesn't look like the default ones in the docs. Doesn't look like my other NAM login pages either.
I get the blue header that takes up the entire browser window width (my other NAM servers it only takes up like 1/2 the width or something).
Missing the "card" on the left-hand side next to username / password.
It also has an "authentication" tab with a "user" below it.
And the authentication cards are gone from the bottom as well.
(granted, on my other servers we got rid of the auth cards at the bottom)
but still, I haven't customized this page yet and it looks nothing like the default picture in the Novell docs
New NAM 3.1.1 IR2 setup
I get the login page, but it doesn't look like the default ones in the docs. Doesn't look like my other NAM login pages either.
I get the blue header that takes up the entire browser window width (my other NAM servers it only takes up like 1/2 the width or something).
Missing the "card" on the left-hand side next to username / password.
It also has an "authentication" tab with a "user" below it.
And the authentication cards are gone from the bottom as well.
(granted, on my other servers we got rid of the auth cards at the bottom)
but still, I haven't customized this page yet and it looks nothing like the default picture in the Novell docs
Categories: Novell Support Forums - New Posts
inventory reports multiple parallel ports
Hello everyone,
I'm having an issue with zcm's inventory, where on some workstations it would detect 1000s of parallel ports. Obviously this causes the inventory scan file to grow very large (approx. 25MB!), which I think is what is making the server and the PCs very slow.
here is a snippet of what I see in the inventory xml file:
Code: <ParallelPort>
<Component>
<ComponentOID>b7949a55df5dc6498b717a0464ff831b</ComponentOID>
<Product>
<ProductOID>d99235000000000000000000c0000cbf</ProductOID>
<Manufacturer />
<ProductName>Parallel Ports</ProductName>
<ModelVersion />
<Type>15</Type>
<Code>3511001</Code>
<IsLocal>0</IsLocal>
<ProductCategoryOID>a9e5e4000000000000000090279059b1</ProductCategoryOID>
<Category>Parallel Port</Category>
<ProductCategory>Parallel Port</ProductCategory>
</Product>
<SerialNumber />
<AssetTag />
<DeltaState>1</DeltaState>
</Component>
<LogicalName />
<IsEPP>0</IsEPP>
<IsECP>0</IsECP>
</ParallelPort>
<ParallelPort>
<Component>
<ComponentOID>77a764323a55814fae79d66ad80fee6e</ComponentOID>
<Product>
<ProductOID>d99235000000000000000000c0000cbf</ProductOID>
<Manufacturer />
<ProductName>Parallel Ports</ProductName>
<ModelVersion />
<Type>15</Type>
<Code>3511001</Code>
<IsLocal>0</IsLocal>
<ProductCategoryOID>a9e5e4000000000000000090279059b1</ProductCategoryOID>
<Category>Parallel Port</Category>
<ProductCategory>Parallel Port</ProductCategory>
</Product>
<SerialNumber />
<AssetTag />
<DeltaState>1</DeltaState>
</Component>
<LogicalName />
<IsEPP>0</IsEPP>
<IsECP>0</IsECP>
</ParallelPort>
<ParallelPort>
<Component>
<ComponentOID>385d075dc99beb4c9459aed9c3240ff3</ComponentOID>
<Product>
<ProductOID>d99235000000000000000000c0000cbf</ProductOID>
<Manufacturer />
<ProductName>Parallel Ports</ProductName>
<ModelVersion />
<Type>15</Type>
<Code>3511001</Code>
<IsLocal>0</IsLocal>
<ProductCategoryOID>a9e5e4000000000000000090279059b1</ProductCategoryOID>
<Category>Parallel Port</Category>
<ProductCategory>Parallel Port</ProductCategory>
</Product>
<SerialNumber />
<AssetTag />
<DeltaState>1</DeltaState>
</Component>
<LogicalName />
<IsEPP>0</IsEPP>
<IsECP>0</IsECP>
</ParallelPort>
<ParallelPort>
<Component>
<ComponentOID>f57b89ce1b953c47be3d584126eb54ec</ComponentOID>
<Product>
<ProductOID>d99235000000000000000000c0000cbf</ProductOID>
<Manufacturer />
<ProductName>Parallel Ports</ProductName>
<ModelVersion />
<Type>15</Type>
<Code>3511001</Code>
<IsLocal>0</IsLocal>
<ProductCategoryOID>a9e5e4000000000000000090279059b1</ProductCategoryOID>
<Category>Parallel Port</Category>
<ProductCategory>Parallel Port</ProductCategory>
</Product>
<SerialNumber />
<AssetTag />
<DeltaState>1</DeltaState>
</Component>
<LogicalName />
<IsEPP>0</IsEPP>
<IsECP>0</IsECP>
</ParallelPort> this obviously gets repeated a bunch of times, and what I have noticed is that the <ComponentOID> is always different.
I know I might have to open a SR request, but I just wanted to see if anybody had seen this before.
thanks,
Giordano
I'm having an issue with zcm's inventory, where on some workstations it would detect 1000s of parallel ports. Obviously this causes the inventory scan file to grow very large (approx. 25MB!), which I think is what is making the server and the PCs very slow.
here is a snippet of what I see in the inventory xml file:
Code: <ParallelPort>
<Component>
<ComponentOID>b7949a55df5dc6498b717a0464ff831b</ComponentOID>
<Product>
<ProductOID>d99235000000000000000000c0000cbf</ProductOID>
<Manufacturer />
<ProductName>Parallel Ports</ProductName>
<ModelVersion />
<Type>15</Type>
<Code>3511001</Code>
<IsLocal>0</IsLocal>
<ProductCategoryOID>a9e5e4000000000000000090279059b1</ProductCategoryOID>
<Category>Parallel Port</Category>
<ProductCategory>Parallel Port</ProductCategory>
</Product>
<SerialNumber />
<AssetTag />
<DeltaState>1</DeltaState>
</Component>
<LogicalName />
<IsEPP>0</IsEPP>
<IsECP>0</IsECP>
</ParallelPort>
<ParallelPort>
<Component>
<ComponentOID>77a764323a55814fae79d66ad80fee6e</ComponentOID>
<Product>
<ProductOID>d99235000000000000000000c0000cbf</ProductOID>
<Manufacturer />
<ProductName>Parallel Ports</ProductName>
<ModelVersion />
<Type>15</Type>
<Code>3511001</Code>
<IsLocal>0</IsLocal>
<ProductCategoryOID>a9e5e4000000000000000090279059b1</ProductCategoryOID>
<Category>Parallel Port</Category>
<ProductCategory>Parallel Port</ProductCategory>
</Product>
<SerialNumber />
<AssetTag />
<DeltaState>1</DeltaState>
</Component>
<LogicalName />
<IsEPP>0</IsEPP>
<IsECP>0</IsECP>
</ParallelPort>
<ParallelPort>
<Component>
<ComponentOID>385d075dc99beb4c9459aed9c3240ff3</ComponentOID>
<Product>
<ProductOID>d99235000000000000000000c0000cbf</ProductOID>
<Manufacturer />
<ProductName>Parallel Ports</ProductName>
<ModelVersion />
<Type>15</Type>
<Code>3511001</Code>
<IsLocal>0</IsLocal>
<ProductCategoryOID>a9e5e4000000000000000090279059b1</ProductCategoryOID>
<Category>Parallel Port</Category>
<ProductCategory>Parallel Port</ProductCategory>
</Product>
<SerialNumber />
<AssetTag />
<DeltaState>1</DeltaState>
</Component>
<LogicalName />
<IsEPP>0</IsEPP>
<IsECP>0</IsECP>
</ParallelPort>
<ParallelPort>
<Component>
<ComponentOID>f57b89ce1b953c47be3d584126eb54ec</ComponentOID>
<Product>
<ProductOID>d99235000000000000000000c0000cbf</ProductOID>
<Manufacturer />
<ProductName>Parallel Ports</ProductName>
<ModelVersion />
<Type>15</Type>
<Code>3511001</Code>
<IsLocal>0</IsLocal>
<ProductCategoryOID>a9e5e4000000000000000090279059b1</ProductCategoryOID>
<Category>Parallel Port</Category>
<ProductCategory>Parallel Port</ProductCategory>
</Product>
<SerialNumber />
<AssetTag />
<DeltaState>1</DeltaState>
</Component>
<LogicalName />
<IsEPP>0</IsEPP>
<IsECP>0</IsECP>
</ParallelPort> this obviously gets repeated a bunch of times, and what I have noticed is that the <ComponentOID> is always different.
I know I might have to open a SR request, but I just wanted to see if anybody had seen this before.
thanks,
Giordano
Categories: Novell Support Forums - New Posts
Spooler Error
I have two users that received a spooler error printing from word and excel. I can log in as different users on the same laptop or PC and I don't receive the error.
Categories: Novell Support Forums - New Posts
Table Errors in Sentinel Logs
Greetings!
Has anyone seen these errors in their Sentinel logs:
Table SCHEDULED_JOB_DETAIL does not exist (Execute SELECT * FROM SCHEDULED_JOB_DETAIL WHERE 1=0 Params [ ] - SQLSt
ate : 42000 - ErrorCode : 942)
This is occuring in advisor, das_binary, das_aggregation, das_itrac, das_rt log files.
It started exactly after upgrading to 2009-08-30_SENTINEL_6.1.1.2_02.
I'm running Sentinel on Solaris 10 with Oracle 10g.
I was trying to diagnose why we can't get advisor downloads anymore and I found these errors, and they repeat. System seems to run fine otherwise.
-Rob Hobson
Has anyone seen these errors in their Sentinel logs:
Table SCHEDULED_JOB_DETAIL does not exist (Execute SELECT * FROM SCHEDULED_JOB_DETAIL WHERE 1=0 Params [ ] - SQLSt
ate : 42000 - ErrorCode : 942)
This is occuring in advisor, das_binary, das_aggregation, das_itrac, das_rt log files.
It started exactly after upgrading to 2009-08-30_SENTINEL_6.1.1.2_02.
I'm running Sentinel on Solaris 10 with Oracle 10g.
I was trying to diagnose why we can't get advisor downloads anymore and I found these errors, and they repeat. System seems to run fine otherwise.
-Rob Hobson
Categories: Novell Support Forums - New Posts